radium - ArgusWriteOutSocket max queue exceeded messages

[David Edelman]

I have a radium process that collects argus flow records from several
collectors and makes the labeled and processed flow records available to
several local processes [rastream and rasqlinsert]

I've noticed instance of rasqlinsert disappearing with no obvious trace.
This is not a frequent occurrence but it is a problem when it happens.
Figuring that I need to catch the rabbit before I can cook the rabbit, I
left radium running in gdb (not optimal but it did work) I see these
messages from the radium instance:

radium[9083]: Fri 2013-10-04 00:38:01.283 ArgusCheckClientMessage: client
localhost.localdomain sent DONE
radium[9083]: Fri 2013-10-04 00:39:01.050 ArgusWriteOutSocket(0x9d61b050)
max queue exceeded 500001
radium[9083]: Fri 2013-10-04 00:39:01.050 ArgusWriteOutSocket(0x9d61b050)
max queue exceeded 500001
radium[9083]: Fri 2013-10-04 00:39:12.122 connect from localhost.localdomain


Is there some value that I can play with to accommodate the size of the data
or is there some way that I can get the ArgusWriteOutSocket() process to
work with smaller amounts of data?

--Dave


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20131003/8a79a6e7/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/20131003/8a79a6e7/attachment.bin>