Power Manager stops periodically

[Mike Shilladay]

Hi Rita,

I was trying to find the download page for the latest (and last) version of Power Manager for HP-UX, which is 4.2 Build 6 (Which is what we run). However, the web page I got it from appears to have gone, only Linux and Windows versions are available.

I am not sure whether you will get any benefit from upgrade to that release. The file is too big to attach it here.(9.5MB)

Mike.

[Dennis Handly]

Again:
What does "file /opt/DevMan/core.DevManBE" show?
Once you know the path to the executable:

>usr/ccs/bin>./gdbpa executable /opt/DevMan/core.DevManBE
>..executable: No such file or directory.
>Core was generated by `DevManBE'.
>Program terminated with signal 6, Aborted.

Replace "executable" by the absolute path of the executable.
Perhaps somewhere in /opt/DevMan/*/DevManBE ??
You may need to use find(1).

>but both don't work

They work fine, if you have the correct path.

Since DevManBE aborted with signal 6, you should look for an error message saying why it is aborting.

[Rita Li]

After changing the port from default 80 to 443 by 07/24/2010 16:19, the PM keeps running & dies shortly by 07/24/2010 23:50, leaving a core file at path /opt/DevMan:-

0 -rw-rw-rw- 1 root sys 0 Jul 23 16:14 alarms.trc
16 -r-------- 1 hpsmh users 1925 Jul 23 16:19 DevManBE.ini
16 drwxrwxrwx 5 root sys 8192 Jul 23 16:27 ./
0 drwxr-x--- 2 root sys 96 Jul 23 16:27 certs/
160 -rw-rw-rw- 1 root sys 78000 Jul 23 16:29 Application.log
3088 -rw-rw-rw- 1 root sys 1579588 Jul 23 23:45 DeviceData.log
4608 -rwx--x--x 1 root root 2353116 Jul 23 23:50 core.DevManBE

Even though able to convert the core.DevManBE into some readable statements but I still get no clue to understand what goes wrong

/opt/DevMan>/usr/ccs/bin/gdbpa -c ./core.DevManBE
HP gdb 5.6.0 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.6.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.

Reading symbols from DevManBE...done.
Core was generated by `DevManBE'.
Program terminated with signal 6, Aborted.


warning: Load module /opt/DevMan/libssl.sl has been stripped


warning: Load module /opt/DevMan/libcrypto.sl has been stripped

#0 0xc7d1e508 in kill+0x10 () from /usr/lib/libc.2
(gdb) bt
#0 0xc7d1e508 in kill+0x10 () from /usr/lib/libc.2
#1 0xc7cb622c in raise+0x24 () from /usr/lib/libc.2
#2 0xc7cfbf50 in abort_C+0x160 () from /usr/lib/libc.2
#3 0xc7cfbfac in abort+0x1c () from /usr/lib/libc.2
#4 0xc72592ac in __gnu_cxx::__verbose_terminate_handler ()
at ../../../../gcc/libstdc++-v3/libsupc++/vterminate.cc:97
#5 0xc7255a10 in __cxxabiv1::__terminate (handler=0x7b03cb60)
at ../../../../gcc/libstdc++-v3/libsupc++/eh_terminate.cc:43
#6 0xc7255a9c in std::terminate ()
at ../../../../gcc/libstdc++-v3/libsupc++/eh_terminate.cc:53
#7 0xc7255c9c in __cxa_throw (obj=0xc7d1e4f8, tinfo=0x0, dest=0x7af6c1cc)
at ../../../../gcc/libstdc++-v3/libsupc++/eh_throw.cc:77
#8 0xc75ad82c in _ZN3dcl9CCommands21ReadUntilTimerExpiredEPvm+0x104 ()
from /opt/DevMan/libXComUPS.sl
#9 0xc7cb622c in raise+0x24 () from /usr/lib/libc.2
#10 0x7af0b42c in ()
#11 0xc7cb622c in raise+0x24 () from /usr/lib/libc.2
(gdb) q

Pls shed me more lights

Thanks,
Rita

[Dennis Handly]

>Even though able to convert the core.DevManBE into some readable statements but I still get no clue to understand what goes wrong

#4 0xc72592ac __gnu_cxx::__verbose_terminate_handler

There should be some message on stderr.

#7 0xc7255c9c __cxa_throw (obj=0xc7d1e4f8, tinfo=0x0, dest=0x7af6c1cc)
#8 0xc75ad82c _ZN3dcl9CCommands21ReadUntilTimerExpiredEPvm+0x104 libXComUPS.sl

This says that ReadUntilTimerExpired got an error and did a throw.
#4 says that someone made a mistake and didn't catch/handle that throw.

[Rita Li]

There should be some message on stderr. >>> where to check out such message? Can't find any corresponding message written to ths syslog.log

#4 says that someone made a mistake and didn't catch/handle that throw. >>> Do you mean someone made a mistake to the Power Manager?

[Dennis Handly]

>where to check out such message? Can't find any corresponding message written to the syslog.log

To stderr, not syslog.log.
You may have to see what "DevMan start" does so you can capture stderr.

>Do you mean someone made a mistake in Power Manager?

Yes. All throws should catches, else it will abort.

[John O'Neill_6]

Hi All,

Sorry for 'Necro'ing' this thread but this is EXACLY what i'm seeing on my RX2660, it's been driving me mad for months, trying to work out what was going on, I even had a HP tech looking into this, so far nobody has been able to tell me WHY the software crashes to a core file.

I finally came to the ITRC to look for a solution, I should have come here months ago and typed in 'DevMan HP UX' into the search bar....stupid me.

Also, is anyone able to confirm whether or not changing the port number sorts the problem out?

One query I do have, does this mean that between the UPS software crashing out and me detecting it has crashed out, we're vulnerable to a power loss failing to shut down the server gracefully? It's not exactly confidence inspiring...

How do I check for a new version of the UPS monitor software?

-John