The hobbitlaunch.log seems to be logging every task that starts. Is it possible to turn that behavior off? Or at least only log errors? I'm concerned about the level of growth of the log.
alan
On Wed, Jul 06, 2005 at 10:17:14AM -0400, Killenbeck, Alan wrote:
The hobbitlaunch.log seems to be logging every task that starts. Is it possible to turn that behavior off? Or at least only log errors? I'm concerned about the level of growth of the log.
Presently you cannot. I'll turn it off for the next release, and let you turn it on via a command line option for those rare cases where it's needed.
Regards, Henrik
Greetings,
I keep seeing these errors in my hobbitlaunch logfiles:
2005-07-01 22:06:47 Task hobbitd terminated by signal 6 2005-07-01 22:06:47 Task bbdisplay terminated by signal 15 2005-07-01 22:11:53 Task hobbitd terminated by signal 6 2005-07-01 22:11:53 Task bbdisplay terminated by signal 15 2005-07-01 22:16:58 Task hobbitd terminated by signal 6 2005-07-01 22:16:58 Task bbdisplay terminated by signal 15 2005-07-02 21:57:24 Task hobbitd terminated by signal 6 2005-07-02 21:57:24 Task bbdisplay terminated by signal 15 2005-07-02 22:16:59 Task hobbitd terminated by signal 6 2005-07-02 22:16:59 Task bbdisplay terminated by signal 15 2005-07-02 22:22:08 Task hobbitd terminated by signal 6 2005-07-02 22:22:08 Task bbdisplay terminated by signal 15 2005-07-02 22:32:16 Task hobbitd terminated by signal 6 2005-07-02 22:32:16 Task bbnet terminated by signal 15 2005-07-02 22:32:16 Task bbdisplay terminated by signal 15 2005-07-03 22:12:00 Task hobbitd terminated by signal 6 2005-07-03 22:12:00 Task bbretest terminated by signal 15 2005-07-03 22:12:00 Task bbdisplay terminated by signal 15 2005-07-03 22:17:07 Task hobbitd terminated by signal 6 2005-07-03 22:17:07 Task bbdisplay terminated by signal 15 2005-07-03 22:27:19 Task hobbitd terminated by signal 6 2005-07-03 22:27:19 Task bbdisplay terminated by signal 15 2005-07-03 22:27:19 Task bbnet terminated by signal 15 2005-07-04 22:12:27 Task hobbitd terminated by signal 6 2005-07-04 22:12:27 Task bbdisplay terminated by signal 15 2005-07-04 22:16:35 Task hobbitd terminated by signal 6 2005-07-04 22:16:35 Task bbdisplay terminated by signal 15 2005-07-04 22:26:47 Task hobbitd terminated by signal 6 2005-07-04 22:26:47 Task bbdisplay terminated by signal 15 2005-07-05 22:26:56 Task hobbitd terminated by signal 6 2005-07-05 22:26:56 Task bbdisplay terminated by signal 15 2005-07-05 22:31:51 Task hobbitd terminated by signal 6 2005-07-05 22:31:51 Task bbdisplay terminated by signal 15 2005-07-05 22:37:02 Task hobbitd terminated by signal 6 2005-07-05 22:37:02 Task bbdisplay terminated by signal 15
I've been also seeing the following errors in bb-display:
2005-06-26 22:11:38 2005-06-26 22:16:47 hobbitd status-board not available 2005-06-26 22:21:57 hobbitd status-board not available 2005-06-26 22:27:09 hobbitd status-board not available 2005-06-27 22:16:32 hobbitd status-board not available 2005-06-27 22:21:28 hobbitd status-board not available 2005-06-28 21:46:38 hobbitd status-board not available 2005-06-28 22:02:01 hobbitd status-board not available 2005-06-28 22:07:17 hobbitd status-board not available 2005-06-29 22:16:32 hobbitd status-board not available 2005-06-29 22:21:40 hobbitd status-board not available 2005-06-30 21:46:57 hobbitd status-board not available 2005-06-30 22:06:35 hobbitd status-board not available 2005-07-01 22:11:53 2005-07-01 22:16:58 hobbitd status-board not available 2005-07-02 22:16:59 2005-07-02 22:22:08 hobbitd status-board not available 2005-07-02 22:32:16 2005-07-03 22:12:00 hobbitd status-board not available 2005-07-03 22:17:07 hobbitd status-board not available 2005-07-03 22:27:19 hobbitd status-board not available 2005-07-04 22:12:27 hobbitd status-board not available 2005-07-04 22:16:35 hobbitd status-board not available 2005-07-04 22:26:47 hobbitd status-board not available 2005-07-05 22:26:56 2005-07-05 22:37:02 hobbitd status-board not available
I have removed the HEARTBEAT command from hobbitlaunch and am running the latest snapshot.
Any suggestions would be greatly appreciated.
Thanks,
Mike
On Wed, Jul 06, 2005 at 10:47:19AM -0400, Michael Dunne wrote:
Greetings,
I keep seeing these errors in my hobbitlaunch logfiles:
2005-07-01 22:06:47 Task hobbitd terminated by signal 6 2005-07-01 22:06:47 Task bbdisplay terminated by signal 15
Signal 6 is a segfault, which should not happen. There ought to be a core file in your ~hobbit/server/tmp/ directory - it would be nice if you could run it through gdb as described in http://www.hswn.dk/hobbit/help/known-issues.html
The other problem is probably related to hobbitd crashing.
Regards, Henrik
Henrik,
Here are the results:
(gdb) bt #0 0x9004310c in kill () #1 0x9009fb9c in abort () #2 0x0001018c in sigsegv_handler (signum=0) at sig.c:57 #3 <signal handler called> #4 0xffff8aac in __memcpy () #5 0x00000001 in ?? () #6 0x90006cc8 in __vfprintf () #7 0x90007390 in sprintf () #8 0x00006a88 in do_message (msg=0xffffdda5, origin=0x225b "p|??p|?8\226|??\024|?^p|?8P\034?\016\020|??P=") at hobbitd.c:1956 #9 0x00009704 in main (argc=0, argv=0xbfffe100) at hobbitd.c:3038
Thanks,
MIke
On 7/6/05 3:51 PM, "Henrik Stoerner" <henrik at hswn.dk> wrote:
On Wed, Jul 06, 2005 at 10:47:19AM -0400, Michael Dunne wrote:
Greetings,
I keep seeing these errors in my hobbitlaunch logfiles:
2005-07-01 22:06:47 Task hobbitd terminated by signal 6 2005-07-01 22:06:47 Task bbdisplay terminated by signal 15
Signal 6 is a segfault, which should not happen. There ought to be a core file in your ~hobbit/server/tmp/ directory - it would be nice if you could run it through gdb as described in http://www.hswn.dk/hobbit/help/known-issues.html
The other problem is probably related to hobbitd crashing.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Michael Dunne Systems Support Specialist AccuWeather, Inc. 814-237-0309 Ext. 7661
Hi Michael,
this *could* be the same bug that I've been chasing with a couple of other users over the past week. We believe it's been nailed down now, so if you could pick up the latest snapshot from http://www.hswn.dk/beta/ and let me know if that runs without these crashes, I would appreciate it.
Thanks, Henrik
On Wed, Jul 06, 2005 at 04:44:38PM -0400, Michael Dunne wrote:
Henrik,
Here are the results:
(gdb) bt #0 0x9004310c in kill () #1 0x9009fb9c in abort () #2 0x0001018c in sigsegv_handler (signum=0) at sig.c:57 #3 <signal handler called> #4 0xffff8aac in __memcpy () #5 0x00000001 in ?? () #6 0x90006cc8 in __vfprintf () #7 0x90007390 in sprintf () #8 0x00006a88 in do_message (msg=0xffffdda5, origin=0x225b "p|??p|?8\226|??\024|?^p|?8P\034?\016\020|??P=") at hobbitd.c:1956 #9 0x00009704 in main (argc=0, argv=0xbfffe100) at hobbitd.c:3038
Thanks,
MIke
On 7/6/05 3:51 PM, "Henrik Stoerner" <henrik at hswn.dk> wrote:
On Wed, Jul 06, 2005 at 10:47:19AM -0400, Michael Dunne wrote:
Greetings,
I keep seeing these errors in my hobbitlaunch logfiles:
2005-07-01 22:06:47 Task hobbitd terminated by signal 6 2005-07-01 22:06:47 Task bbdisplay terminated by signal 15
Signal 6 is a segfault, which should not happen. There ought to be a core file in your ~hobbit/server/tmp/ directory - it would be nice if you could run it through gdb as described in http://www.hswn.dk/hobbit/help/known-issues.html
The other problem is probably related to hobbitd crashing.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Michael Dunne Systems Support Specialist AccuWeather, Inc. 814-237-0309 Ext. 7661
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Henrik Storner
Greetings Henrik,
I built and installed the latest snapshot and it seems to correct the problem I wrote about previously. However, soon after installing Hobbit showed an alarm for hobbitd_rrd. The alarm is "Program Crashed Fata Signal Caught"
My core file shows the following:
/cores hobbit$ gdb ~/server/bin/hobbitd /cores/core.2764 GNU gdb 5.3-20030128 (Apple version gdb-330.1) (Fri Jul 16 21:42:28 GMT 2004) Copyright 2003 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 "powerpc-apple-darwin". Reading symbols for shared libraries .. done #0 0x9004310c in kill () (gdb) bt #0 0x9004310c in kill () #1 0x9009fb9c in abort () #2 0x0000b724 in run_command (cmd=0x19 "", errortext=0xbfff4d84 "", banner=0x14, bannerbytes=0xfffffff5, showcmd=-1073791308, timeout=31) at misc.c:313 #3 <signal handler called> #4 0x90007250 in strlen () #5 0x90006cc8 in __vfprintf () #6 0x9000c8ac in vfprintf () #7 0x0000a44c in main (argc=-1073787516, argv=0xa00016b4) at hobbitd.c:3379
Any ideas?
Thanks,
Mike
On 7/13/05 2:32 AM, "Henrik Stoerner" <henrik at hswn.dk> wrote:
Hi Michael,
this *could* be the same bug that I've been chasing with a couple of other users over the past week. We believe it's been nailed down now, so if you could pick up the latest snapshot from http://www.hswn.dk/beta/ and let me know if that runs without these crashes, I would appreciate it.
Thanks, Henrik
Hi Michael,
In <BEFA935A.59DE%dunne at accuweather.com> Michael Dunne <dunne at accuweather.com> writes:
I built and installed the latest snapshot and it seems to correct the problem I wrote about previously. However, soon after installing Hobbit showed an alarm for hobbitd_rrd. The alarm is "Program Crashed Fata Signal Caught"
My core file shows the following:
/cores hobbit$ gdb ~/server/bin/hobbitd /cores/core.2764
Your command here is wrong - you're loading the "hobbitd" program into gdb, but the crash happened with the hobbitd_rrd program. So the traceback doesn't make sense.
"gdb ~/server/bin/hobbitd_rrd /cores/core.2764" should give a more meaningful result.
I have one other report of a crash in hobbitd_rrd (or hobbitd_larrd, as it has been called before), so there is some bug hiding in there.
Regards, Henrik
Blast...Apologies...Here is the corrected output.
/cores hobbit$ gdb ~/server/bin/hobbitd_rrd /cores/core.2764 GNU gdb 5.3-20030128 (Apple version gdb-330.1) (Fri Jul 16 21:42:28 GMT 2004) Copyright 2003 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 "powerpc-apple-darwin". Reading symbols for shared libraries ... done #0 0x9004310c in kill () (gdb) bt #0 0x9004310c in kill () #1 0x9009fb9c in abort () #2 0x0000b724 in sigsegv_handler () at pcre.c:8090 #3 <signal handler called> #4 0x90007250 in strlen () #5 0x90006cc8 in __vfprintf () #6 0x9000c8ac in vfprintf () #7 0x0000a44c in dprintf () at pcre.c:7445 #8 0x000086d0 in do_external_rrd () at pcre.c:6313 #9 0x00008f28 in update_rrd () at pcre.c:6809 #10 0x00002dac in find_fixedlength (code=0x0, options=-1610591728) at pcre.c:1396
On 7/13/05 10:32 AM, "Henrik Storner" <henrik at hswn.dk> wrote:
Hi Michael,
In <BEFA935A.59DE%dunne at accuweather.com> Michael Dunne <dunne at accuweather.com> writes:
I built and installed the latest snapshot and it seems to correct the problem I wrote about previously. However, soon after installing Hobbit showed an alarm for hobbitd_rrd. The alarm is "Program Crashed Fata Signal Caught"
My core file shows the following:
/cores hobbit$ gdb ~/server/bin/hobbitd /cores/core.2764
Your command here is wrong - you're loading the "hobbitd" program into gdb, but the crash happened with the hobbitd_rrd program. So the traceback doesn't make sense.
"gdb ~/server/bin/hobbitd_rrd /cores/core.2764" should give a more meaningful result.
I have one other report of a crash in hobbitd_rrd (or hobbitd_larrd, as it has been called before), so there is some bug hiding in there.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (3)
-
Alan.Killenbeck＠xerox.com
-
dunne＠accuweather.com
-
henrik＠hswn.dk