In <4974AE8B.80706 at gmail.com> Olivier Beau <obeau79 at gmail.com> writes:
It happened again today at 17:00:22. Nothing new when doing a bt on the coredump. An extract of rrd-status.log from 16h55 to 17h05 is available at http://www.qalpit.com/~olivier/tmp/rrd-status.log.gz
OK, the interesting part is here when it crashes: 2009-01-19 17:00:22 hobbitd_rrd: Got message 181436 @@status#181436/cedratnet-bdd1|1232380822.602633|127. 0.0.1||cedratnet-bdd1|mysql|1232398822|green||green|1231215890|0||0||1232380812|0|linuxmysql|unix/mysql 2009-01-19 17:00:22 startpos 342639, fillpos 378880, endpos 342991 2009-01-19 17:00:22 hobbitd_rrd: Got message 181437 @@status#181437/moniteur-ora2|1232380822.618847|10.12 .0.67||moniteur-ora2|cpu|1255363113|blue||blue|1228751913|0||1255363113|Disabled by 2009-01-19 17:00:22 startpos 342995, fillpos 378880, endpos -1 2009-01-19 17:00:22 Peer at 0.0.0.0:0 failed: Broken pipe 2009-01-19 17:00:22 Peer not up, flushing message queue 2009-01-19 17:00:22 Opening file /data/hobbit/server/etc/hobbit-rrddefinitions.cfg 2009-01-19 17:00:22 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=528383 2009-01-19 17:00:22 hobbitd_rrd: Got message 181450 @@status#181450/nurun-etam-bdd1|1232380822.807004|127 .0.0.1||nurun-etam-bdd1|mysql|1232398822|green||green|1231768476|0||0||1232380582|0|linuxmysql|unix/mysql 2009-01-19 17:00:22 startpos 17100, fillpos 19357, endpos 17846 2009-01-19 17:00:22 Opening file /data/hobbit/server/etc/bb-hosts It appears to be a "mysql" status from either cedratnet-bdd1 or nurun-etam-bdd1 that causes the crash (I cannot tell exactly, because output buffering comes into play when there's a crash). It *could* also be the cpu-report from moniteur-ora2, but I doubt that - the cpu-status is tested a lot more than the mysql-status. In fact, "mysql" isn't part of hobbitd_rrd by default. So is this something you've added ? Is it something that you generate graphs for ? Or is it just a status that hobbitd_rrd should ignore ? Regards, Henrik