HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- More EMS errors
Operating System - HP-UX
1833541
Members
3042
Online
110061
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-13-2003 08:34 AM
10-13-2003 08:34 AM
More EMS errors
Here are some more errors from my EMS:
/etc/opt/resmon/log/registrar.log
Standard input-----------Start Event--------------------
Event 2937 occurred at Fri May 23 08:15:20.016358 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
abort_awaiting_reply_obj: socket=19: Connection aborted
-------------------End Event----------------------
-------------------Start Event--------------------
Event 2961 occurred at Fri May 23 08:15:20.017012 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired contact object for monitor /usr/sbin/stm/uut/bin/too
ls/monitor/fc60mon
-------------------End Event----------------------
-------------------Start Event--------------------
Event 2960 occurred at Fri May 23 08:15:47.015236 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired awaiting-reply object, socket=19
-------------------End Event----------------------
/etc/opt/resmon/log/registrar.log
Standard input-----------Start Event--------------------
Event 2937 occurred at Fri May 23 08:15:20.016358 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
abort_awaiting_reply_obj: socket=19: Connection aborted
-------------------End Event----------------------
-------------------Start Event--------------------
Event 2961 occurred at Fri May 23 08:15:20.017012 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired contact object for monitor /usr/sbin/stm/uut/bin/too
ls/monitor/fc60mon
-------------------End Event----------------------
-------------------Start Event--------------------
Event 2960 occurred at Fri May 23 08:15:47.015236 2003
Process ID: 1230 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired awaiting-reply object, socket=19
-------------------End Event----------------------
I Love Computers ... Sometimes
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2003 08:37 AM
10-13-2003 08:37 AM
Re: More EMS errors
Here is my original post:
My EMS is not working. We have many admins. It's hard to tell what happened.
/opt/resmon/bin/send_test_event -v ia64_corehw
Finding resource name associated with monitor ia64_corehw.
Found resource name /system/events/ia64_corehw
associated with monitor ia64_corehw.
Creating test file /var/stm/config/tools/monitor/ia64_corehw.test
for monitor ia64_corehw.
Performing resls on resource name /system/events/ia64_corehw
for monitor ia64_corehw to cause generation of test event.
Contacting Registrar on cleuit3
resls: Cannot contact Registrar on cleuit3
/opt/resmon/bin/send_test_event: Failed to perform resls on resource name /syste
m/events/ia64_corehw for ia64_corehw to cause generation of test event.
System call failed with return value 256.
My EMS is not working. We have many admins. It's hard to tell what happened.
/opt/resmon/bin/send_test_event -v ia64_corehw
Finding resource name associated with monitor ia64_corehw.
Found resource name /system/events/ia64_corehw
associated with monitor ia64_corehw.
Creating test file /var/stm/config/tools/monitor/ia64_corehw.test
for monitor ia64_corehw.
Performing resls on resource name /system/events/ia64_corehw
for monitor ia64_corehw to cause generation of test event.
Contacting Registrar on cleuit3
resls: Cannot contact Registrar on cleuit3
/opt/resmon/bin/send_test_event: Failed to perform resls on resource name /syste
m/events/ia64_corehw for ia64_corehw to cause generation of test event.
System call failed with return value 256.
I Love Computers ... Sometimes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2003 10:36 AM
10-13-2003 10:36 AM
Re: More EMS errors
This message confuses me because 'Socket 19 = port 19 = chargen in /etc/services.' There is a security advisory out about 'chargen' but I think you've stepped into a work in progress but and need HP. Here's the 'chargen' url.
http://www.cert.org/advisories/CA-1996-01.html
Regarding ".../etc/opt/resmon/lbin/registrar...". This is what's odd. EMS use 'registar' at 1712. Check the port for 'register' in /etc/services.
registrar 1712/tcp # resource monitoring service
registrar 1712/udp # resource monitoring service
And this in /etc/inetd.conf
registrar stream tcp nowait root /etc/opt/resmon/lbin/registrar /etc/opt/resmon/
lbin/registrar
###########################################
#
###########################################
This bottom message is for a Itanium IA64 server. Events for the IA64 can be found here:
http://docs.hp.com/hpux/onlinedocs/diag/ems/ia64_corehw.htm
###########################################
#
###########################################
I think you need HP HW for this.
http://www.cert.org/advisories/CA-1996-01.html
Regarding ".../etc/opt/resmon/lbin/registrar...". This is what's odd. EMS use 'registar' at 1712. Check the port for 'register' in /etc/services.
registrar 1712/tcp # resource monitoring service
registrar 1712/udp # resource monitoring service
And this in /etc/inetd.conf
registrar stream tcp nowait root /etc/opt/resmon/lbin/registrar /etc/opt/resmon/
lbin/registrar
###########################################
#
###########################################
This bottom message is for a Itanium IA64 server. Events for the IA64 can be found here:
http://docs.hp.com/hpux/onlinedocs/diag/ems/ia64_corehw.htm
###########################################
#
###########################################
I think you need HP HW for this.
Support Fatherhood - Stop Family Law
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP