- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: EMS error message.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 05:56 AM
07-11-2002 05:56 AM
EMS error message.
Jul 11 19:32:49 admsvr EMS [1165]: ----- EMS Monitor Restart due to system reboot ----- Title: lpmc_em Command: /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em Vendor: Hewlett-Packard Company Version: B.01.00 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 3292848383
if I excecute the above mentioned command I get this output.
/system/events/cpu/lpmc/cache_errors
But If I run cstm I am not getting any error.
And one more thing telnet messages is not being logged in syslog. (I have tried inetd -c,reboot etc.)
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 06:04 AM
07-11-2002 06:04 AM
Re: EMS error message.
I just found some messages in this patch of STM for hpux11.11
PHSS_26268
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 06:09 AM
07-11-2002 06:09 AM
Re: EMS error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 06:10 AM
07-11-2002 06:10 AM
Re: EMS error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 07:12 AM
07-11-2002 07:12 AM
Re: EMS error message.
The message told you, that the monitor has been restarted and not, that the monitor has detected an error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 07:27 AM
07-11-2002 07:27 AM
Re: EMS error message.
And after executing that command I am getting some output.
The syslog.conf is as follows-
# @(#) $Revision: 74.1 $
#
# syslogd configuration file.
#
# See syslogd(1M) for information about the format of this file.
#
mail.debug /var/adm/syslog/mail.log
*.info;mail.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.alert root
*.emerg *
It is the same on one other server also, but there I do not get these messages. Why?
Can someone throw some light on this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2002 09:07 AM
07-11-2002 09:07 AM
Re: EMS error message.
It appears there is a problem internal to your EMS software. EMS by default issues restart messages that are "informational" and are logged in /var/opt/resmon/log/event.log. They should not be logged into your syslog unless you have changed the defaults.
1. By running the following command you see where all of the events are sent:
/etc/opt/resmon/lbin/moncheck |more
For /adapters/events/TL_adapter/0_12_0_0.8.0.255.0:
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
Events >= 3 (MAJOR WARNING) Goto SYSLOG
Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root
Events >= 4 (SERIOUS) Goto TCP; host=nitro.atl.hp.com port=49406...truncated text....
Check and make sure you are not sending information messages to syslog.
2. Check the /var/opt/resmon/log/api.log and search for lpmc errors.
3. Check the README file for the version of Diagnostics you have installed to make sure you have all of the required patches for the appropriate version:
http://www.docs.hp.com/hpux/onlinedocs/diag/st/st_read.htm
You can determine the release date by using the table of versions and the version of Support Tools Manager installed:
swlist -l product |grep -i sup-tool-mgr
Sup-Tool-Mgr B.11.00.20.09 Support Tools Manager for HPUX systems
Take this number to:
http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table
In this example B.11.00.20.09 = March 2002.
4. Versions of STM and EMS are bundled together in the OnlineDiag software. As such they are rev locked and should not be other than shown in the table of versions. Make sure you do not have different software versions other than those that are shown together.
Thanks for participating in the forums,
Martin
Chaos reigns within. Reflect, repent, and reboot. Order shall return.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2004 08:57 AM
10-12-2004 08:57 AM