The RRD logfiles were very big and thus caused the crash.
They get very big due to RRD update errors complaining about updating the RRD with the same timestamp.
Anybody else have this behaviour ?
Regards, Thomas
Thomas wrote:
Running 4.0.5 on RedHat 3.0 Update 3.
Did not see it but had many core files.
Upgraded to todays snapshot Aug 29 (4.1.2) but with the same errors
-bash-2.05b$ file core.5735 core.5735: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'hobbitd_larrd' -bash-2.05b$ gdb bin/hobbitd_larrd core.5735 GNU gdb Red Hat Linux (6.1post-1.20040607.17rh) Copyright 2004 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/tls/libthread_db.so.1".
Core was generated by `hobbitd_larrd --rrddir=/usr/local/hobbit/data/rrd'. Program terminated with signal 25, File size limit exceeded. Reading symbols from /usr/lib/libpng12.so.0...done. Loaded symbols for /usr/lib/libpng12.so.0 Reading symbols from /lib/libpcre.so.0...done. Loaded symbols for /lib/libpcre.so.0 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/tls/libm.so.6...done. Loaded symbols for /lib/tls/libm.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 0x009c19fe in __write_nocancel () from /lib/tls/libc.so.6 (gdb) quit
the following error is given several times pr day as yellow alerts
BOARDBUSY locked at 1, GETNCNT is 0, GETPID is 0, 0 clients
Anybody seen this before ?
Regards, Thomas
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk