#1771 OpenHPI Daemon Core generated

Future
open
OpenHPI Daemon
5
2015-10-06
2012-10-24
No

We have started multiple openHPI daemons to get the HW details and randomly we are getting the following cores from openHPI damon,

Can you please let me know, the reason for getting these,

Thread 1 (LWP 15962):
#0 0x00000055591f8f80 in raise () from /lib64/libc.so.6
#1 0x00000055591fd88c in abort () from /lib64/libc.so.6
#2 0x0000005558f5e4f8 in g_logv () from /lib64/libglib-2.0.so.0
#3 0x0000005558f5e538 in g_log () from /lib64/libglib-2.0.so.0
#4 0x0000005558ee45cc in _ftext () from /lib64/libgthread-2.0.so.0
#5 0x0000005559039218 in __pthread_mutex_lock_full () from /lib64/libpthread.so.0
#6 0x000000012005ba30 in ?? ()
(gdb) quit

Thread 1 (LWP 15733):
#0 0x0000000000000000 in ?? ()
#1 0x0000005562bf57a4 in oh_get_event () from /lib/openhpi/libipmidirect.so
#2 0x0000000120012258 in harvest_events_for_handler ()
#3 0x00000001200123dc in oh_harvest_events ()
#4 0x0000000120033594 in evtget_func ()
#5 0x0000005562674ee8 in ?? () from /lib64/libglib-2.0.so.0
warning: GDB can't find the start of the function at 0x5562674ee7.
(gdb) info args

#0 0x000000555d2e2f80 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x000000555d2e2f80 in raise () from /lib64/libc.so.6
#1 0x000000555d2e788c in abort () from /lib64/libc.so.6
Cannot access memory at address 0xffff768de8

Discussion

  • Santhosh kanchanapally

    • labels: 622325 --> IPMI Direct plugin
    • assigned_to: avpak --> arcress
     
  • Anton Pak

    Anton Pak - 2012-10-29

    Did you use different UID-MAP files for those OpenHPI daemon instances?

     
  • Santhosh kanchanapally

    Same UID-MAP files are used for these different instances of openHPI daemon.

     
  • dr_mohan

    dr_mohan - 2015-10-06
    • Subsystem: --> OpenHPI Daemon
    • 3.7.0: 3.0.0 --> Future
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks