1830898 Members
3070 Online
110017 Solutions
New Discussion

EMS Errors

 
SOLVED
Go to solution
Phil Daws_2
Regular Advisor

EMS Errors

How can I resolve this error?

-------------------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
5 REPLIES 5
steven Burgess_2
Honored Contributor

Re: EMS Errors

Hi,

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


take your time and think things through
Steven Gillard_2
Honored Contributor

Re: EMS Errors

The real error here is the "unresolved symbol" message you see at the bottom. This is likely to be caused by some patch / product conflict that you have with your STM or EMS installation.

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
Phil Daws_2
Regular Advisor

Re: EMS Errors

# swlist -l fileset | grep EMS
# 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
Steven Gillard_2
Honored Contributor
Solution

Re: EMS Errors

Patch PHSS_23655 for STM may help, it contains the following defect fix:

3. 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
Phil Daws_2
Regular Advisor

Re: EMS Errors

Thanks :)