Xymon Mailing List Archive search

bbproxy crashing

7 messages in this thread

list Larry Barber · Tue, 15 May 2007 08:49:30 -0500 · 
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#0  0x008aa7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x008ea7a5 in raise () from /lib/tls/libc.so.6
#2  0x008ec209 in abort () from /lib/tls/libc.so.6
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877

I really need to get this figured out, any help would be most appreciated.

Thanks,
Larry Barber
list Jason Altrincham Jones · Tue, 15 May 2007 14:58:54 +0100 · 
If you applied a patch you should run make clean; make; make install.

 
My 2 cents :-)

Jason.
▸ quoted from Larry Barber

 
From: Larry Barber [mailto:user-6ef9c2864140@xymon.invalid] 
Sent: 15 May 2007 14:50
To: hobbit
Subject: [hobbit] bbproxy crashing

 
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#0  0x008aa7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 
#1  0x008ea7a5 in raise () from /lib/tls/libc.so.6
#2  0x008ec209 in abort () from /lib/tls/libc.so.6
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877

I really need to get this figured out, any help would be most
appreciated.

Thanks,
Larry Barber
list Larry Barber · Tue, 15 May 2007 09:33:30 -0500 · 
I didn't do anything to the machine, no patches, not even any configuration
changes. Bbproxy just started crashing.

Thanks,
Larry Barber
▸ quoted from Jason Altrincham Jones

On 5/15/07, Jones, Jason (Altrincham) <user-ee957b46acd2@xymon.invalid> wrote:
 If you applied a patch you should run make clean; make; make install.



My 2 cents J
▸ quoted from Jason Altrincham Jones

Jason.


*From:* Larry Barber [mailto:user-6ef9c2864140@xymon.invalid]
*Sent:* 15 May 2007 14:50
*To:* hobbit
*Subject:* [hobbit] bbproxy crashing


Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#0  0x008aa7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x008ea7a5 in raise () from /lib/tls/libc.so.6
#2  0x008ec209 in abort () from /lib/tls/libc.so.6
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877

I really need to get this figured out, any help would be most appreciated.

Thanks,
Larry Barber
list Henrik Størner · Tue, 15 May 2007 16:44:26 +0200 ·
▸ quoted from Larry Barber
On Tue, May 15, 2007 at 08:49:30AM -0500, Larry Barber wrote:
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
Weird. Could you go back into gdb and do run the commands

   fr 5
   p cwalk
   p cwalk->ssocket
   p fdread


Regards,
Henrik
list Larry Barber · Tue, 15 May 2007 09:52:07 -0500 · 
Afraid it won't be much help:

(gdb) fr 5
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
877                                     FD_SET(cwalk->ssocket, &fdread);
(gdb) p cwalk
No symbol "cwalk" in current context.
(gdb) p cwalk->ssocket
No symbol "cwalk" in current context.
(gdb) p fdread
No symbol "fdread" in current context.


Thanks,
Larry Barber
▸ quoted from Henrik Størner

On 5/15/07, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Tue, May 15, 2007 at 08:49:30AM -0500, Larry Barber wrote:
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
Weird. Could you go back into gdb and do run the commands

   fr 5
   p cwalk
   p cwalk->ssocket
   p fdread


Regards,
Henrik
list Larry Barber · Tue, 15 May 2007 10:17:52 -0500 · 
This is getting weirder by the minute. I just restored the same
configuration I was using, so that bbproxy is back in the mix, and it's not
crashing anymore. I haven't really done anything to the machine beyond
restoring the same config I was using yesterday. Evidently whatever was
causing the problem has gone away, for now at least.

Thanks,
Larry Barber
▸ quoted from Larry Barber

On 5/15/07, Larry Barber <user-6ef9c2864140@xymon.invalid> wrote:
Afraid it won't be much help:

(gdb) fr 5
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
877                                     FD_SET(cwalk->ssocket, &fdread);
(gdb) p cwalk
No symbol "cwalk" in current context.
(gdb) p cwalk->ssocket
No symbol "cwalk" in current context.
(gdb) p fdread
No symbol "fdread" in current context.


Thanks,
Larry Barber

On 5/15/07, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Tue, May 15, 2007 at 08:49:30AM -0500, Larry Barber wrote:
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
Weird. Could you go back into gdb and do run the commands

   fr 5
   p cwalk
   p cwalk->ssocket
   p fdread


Regards,
Henrik
list Henrik Størner · Tue, 15 May 2007 17:32:35 +0200 · 
Hmm ... quite odd. But unless it re-appears, troubleshooting it will be
difficult. Let me know if it does.


Regards,
Henrik
▸ quoted from Larry Barber

On Tue, May 15, 2007 at 10:17:52AM -0500, Larry Barber wrote:
This is getting weirder by the minute. I just restored the same
configuration I was using, so that bbproxy is back in the mix, and it's not
crashing anymore. I haven't really done anything to the machine beyond
restoring the same config I was using yesterday. Evidently whatever was
causing the problem has gone away, for now at least.

Thanks,
Larry Barber

On 5/15/07, Larry Barber <user-6ef9c2864140@xymon.invalid> wrote:
Afraid it won't be much help:

(gdb) fr 5
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
877                                     FD_SET(cwalk->ssocket, &fdread);
(gdb) p cwalk
No symbol "cwalk" in current context.
(gdb) p cwalk->ssocket
No symbol "cwalk" in current context.
(gdb) p fdread
No symbol "fdread" in current context.


Thanks,
Larry Barber

On 5/15/07, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Tue, May 15, 2007 at 08:49:30AM -0500, Larry Barber wrote:
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:

(gdb) where
#3  0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
Weird. Could you go back into gdb and do run the commands

   fr 5
   p cwalk
   p cwalk->ssocket
   p fdread


Regards,
Henrik


-- 

Henrik Storner