Hobbit constantly coring
An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20080612/e3887ea7/attachment.html>
I had the same issue.
$BBVAR/hist/allevents was not created.
touch it and then works fine.
Nico
Le 12 juin 08 à 10:57, Kevin Walsh a écrit :
Version Hobbit Monitor 4.2.0
We are experiencing a large number of core files all similar to the
one below which fill up the monitor server[hobbit at monitor server]$ gdb bin/hobbitd_history /home/hobbit/core. 9996 GNU gdb Red Hat Linux (6.5-25.el5_1.1rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain
conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for
details. This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/i686/nosegneg/libc.so.6...done. Loaded symbols for /lib/i686/nosegneg/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Core was generated by `hobbitd_history'. Program terminated with signal 11, Segmentation fault. #0 0x0090bc00 in setvbuf () from /lib/i686/nosegneg/libc.so.6 (gdb) bt #0 0x0090bc00 in setvbuf () from /lib/i686/nosegneg/libc.so.6 #1 0x08049fbe in main (argc=1, argv=Cannot access memory at address
0x4 ) at hobbitd_history.c:111 (gdb)If you need more info let me know.
Thanks
participants (2)
-
kevin.walsh@criticalpath.net
-
ndorfsman@gmail.com