Radium Exiting After Connected ratop() Exits Normally

[David Edelman]

The server isn’t running flat out, but it is running hotter than I would usually allow. I’d be happy to experiment with the deadman timer.
 
--Dave
 
From: Carter Bullard [mailto:carter at qosient.com] 
Sent: Monday, October 07, 2013 8:58 PM
To: David Edelman
Cc: Argus
Subject: Re: Radium Exiting After Connected ratop() Exits Normally
 
When we hit certain errors, we exit the program.  We fork a complete process to compile the filter.  We have to write the filter to the  new process, and wait to read the resulting compiled filter from the socket, and we put a deadman timer on waiting.   So looks like either you are reconnecting and passing the filter, but the deadman pops.  Is this server really busy ????
 
 The idea on the filter is that it maybe important, so we exit if we can get it.  We should increase the deadman timer...

Carter

On Oct 7, 2013, at 7:15 PM, "David Edelman" <dedelman at iname.com <mailto:dedelman at iname.com> > wrote:
I have an instance of radium collecting flow records from a radium instance on a remote system. I was looking at some odd behavior with rasqlinsert reading from the local radium instance so I had radium running under gdb (not optimal but life rarely is) I know that I had hooked up ratop more than once using –S localhost:561 with no problem, but this time I gave ratop a bpf filter of – udp and not \( dst port 53 or dst port 137 or dst port 161 or dst port 162\) ratop worked fine. However, when I stopped ratop with the :q command, radium exited with this in gdb:
Detaching after fork from child process 2196.
radium[9083]: Mon 2013-10-07 18:44:00.529 ArgusWriteOutSocket(0x89f54a18) max queue exceeded 500001
radium[9083]: Mon 2013-10-07 18:44:00.529 ArgusWriteOutSocket(0x89f54a18) max queue exceeded 500001
radium[9083]: Mon 2013-10-07 18:54:17.043 connect from localhost.localdomain
radium[9083]: Mon 2013-10-07 18:54:33.433 ArgusWriteOutSocket(0x973cd358) max queue exceeded 500001
radium[9083]: Mon 2013-10-07 18:54:33.433 ArgusWriteOutSocket(0x973cd358) max queue exceeded 500001
radium[9083]: Mon 2013-10-07 18:58:36.256 ArgusCheckClientMessage: client localhost.localdomain sent DONE
radium[9083]: Mon 2013-10-07 18:59:25.558 connect from localhost.localdomain
Detaching after fork from child process 2371.
radium[9083]: Mon 2013-10-07 19:00:38.889 ArgusCheckClientMessage: client localhost.localdomain sent DONE
radium[9083]: Mon 2013-10-07 19:02:03.745 connect from localhost.localdomain
Detaching after fork from child process 2440.
radium[9083]: Mon 2013-10-07 19:02:08.825 ERROR: compiler timed out
[Thread 0xb66adb90 (LWP 9093) exited]
[Thread 0xb70aeb90 (LWP 9092) exited]
Program exited normally.
Missing separate debuginfos, use: debuginfo-install glibc-2.9-3.i686 libgcc-4.3.2-7.i386 tcp_wrappers-libs-7.6-53.fc10.i386 zlib-1.2.3-18.fc9.i386
(gdb)
(gdb)
(gdb)
At this point gdb has nothing to say;  no data for  where no data for info threads the program has exited. Any suggestions?
--Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20131008/161ca583/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6283 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20131008/161ca583/attachment.bin>