- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- EMS Errors
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
12-10-2001 02:37 AM
12-10-2001 02:37 AM
-------------------Start Event--------------------
User event occurred at Sun Dec 9 08:18:04.748504 2001
Process ID: 1320 (/usr/sbin/stm/uut/bin/.../dm_core_hw) Log Level: Error
Tool is exiting due to receipt of an unexpected signal (6).
SIGABRT (6) signal indicates tool called abort() system call or tool attempted to access a shared library routine that does not exis
t or cannot be accessed due to permission problems.
Possible Causes/Recommended Action:
Internal Application error. Tool should never call abort system call.
Ensure the STM libraries have read and execute permissions for all users.
-------------------End Event----------------------
-------------------Start Event--------------------
User event occurred at Sun Dec 9 08:19:06.090905 2001
Process ID: 1678 (/usr/sbin/stm/uut/bin/.../dm_core_hw) Log Level: Error
dm_core_hw monitor has successfully registered with diaglogd for hardware event monitoring.
-------------------End Event----------------------
/usr/lib/dld.sl: Unresolved symbol: pre_super_kludge (code) from /usr/sbin/stm/uut/lib/tlmisc.sl
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 04:33 AM
12-10-2001 04:33 AM
Re: EMS Errors
As per message , I would check your permissions within stm (Support Tools Manager)
I have checked mine, directories and files within are all rx-rx-rx-
I have 2 monitoring processes
-r-xr-xr-x 1 bin bin 61440 Jan 28 1998 diaglogd
-r-xr-xr-x 1 bin bin 147456 Jan 28 1998 diagmond
They are both started from
ll diagnostic
-r-xr-xr-x 1 bin bin 3435 Apr 8 1998 diagnostic
You can use the stm tool by simply typing stm from your prompt
Checkout the hp site for errors also
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 05:26 AM
12-10-2001 05:26 AM
Re: EMS Errors
Can you post output to the following commands:
- swlist -l fileset | grep EMS
- swlist -l fileset | grep -i stm
Or it might be best to log a call with HP and find out if this is a known problem.
Regards,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 05:35 AM
12-10-2001 05:35 AM
Re: EMS Errors
# EMS-Config A.03.20 EMS Config
EMS-Config.EMS-GUI A.03.20 EMS GUI
# EMS-Core A.03.20 EMS Core Product
EMS-Core.EMS-CORE A.03.20 Event Monitoring Services Core Files
# EMS-KRMonitor A.11.00.02 EMS Kernel Resource Monitor
EMS-KRMonitor.KRMON-DRV-CMN A.11.00.02 EMS Kernel Resource Monitor Common Files for Driver
EMS-KRMonitor.KRMON-DRV-DRV A.11.00.02 EMS Kernel Resource Monitor 64-bit Driver
EMS-KRMonitor.KRMON-MAN A.11.00.02 EMS Kernel Resource Monitor Manual
EMS-KRMonitor.KRMON-RUN A.11.00.02 EMS Kernel Resource Monitor Runtime
# swlist -l fileset | grep -i stm
Sup-Tool-Mgr.STM-CATALOGS B.11.00.15.08 HPUX Support Tools Manager Catalogs
Sup-Tool-Mgr.STM-MAN B.11.00.15.08 HPUX Support Tools Manager Manual Pages
Sup-Tool-Mgr.STM-SHLIBS B.11.00.15.08 HPUX Support Tools Manager Share Libraries
Sup-Tool-Mgr.STM-UI-RUN B.11.00.15.08 HPUX Support Tools Manager User Interface
Sup-Tool-Mgr.STM-UUT-RUN B.11.00.15.08 HPUX Support Tools Manager Unit Under Test Runtime
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 05:56 AM
12-10-2001 05:56 AM
Solution3. dm_core_hw monitor
EMS monitor dm_core_hw will exit at each polling cycle,
which is once every 15 minutes. It will then be restarted,
and a "restart" event message will be logged in the event
log /var/opt/resmon/log/event.log and send the same message
to all targets associated with this monitor.
Give that a try.
Regards,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 06:04 AM
12-10-2001 06:04 AM