In <user-01cf0bccef0a@xymon.invalid> Adam Scheblein <user-de8d51f0c651@xymon.invalid> writes:
For the past couple of nights i have been getting the following errors
in some of my hobbit logs:
Clientdata.log:
2005-09-28 03:09:36 Worker process died with exit code 134, terminating
"code 134" usually means it it crashed with a segfault (signal 6 = 134-128).
Check for core files in the ~hobbit/server/tmp/ directory - I'm
sure you'll find some - and run them through gdb as described
in http://www.hswn.dk/hobbit/help/known-issues.html#bugreport
Hobbitlaunch.log
2005-09-29 02:04:20 Task clientdata terminated, status 1
2005-09-29 05:41:37 Task clientdata terminated, status 1
and then all graphing and updates stop...
hobbitlaunch normally restarts a task, but if it continues to
crash it will stop doing that (to avoid a run-away program taking
up all system ressources by starting all the time). So when we
figure out why hobbitd_client is crashing, this should go
away also.
Henrik