radium: information in argus.log lost after restart

[Carter Bullard]

Hey Wolfgang,
Sounds like radium() is having problems restarting?
Do you have an messages in /var/log/messages from the radium
process?  If its being rejected by the remote servers, messages
will be there.   Radium, if its shutdown properly, will do the right
thing with its sockets, at least that is the design.

Radium doesn't have any sense of the data that is in its output file,
so it can't "throw away old information", but it could possibly corrupt
the output file, somehow.   If radium is corrupting the file, if you can
send me a copy of it, or anything like it, I'll be glad to figure out  
how
to read it.

Carter

On Feb 12, 2007, at 2:23 PM, Wolfgang Barth wrote:

> Hi,
>
> I have a problem with radium (3.0.0.rc.39 and older):
> radium reads input data from severe distributed argus daemons.  
> After reboot
> the hosts running argus, radium didn't collect no more data. This  
> may be a
> side effect from firewalling with iptables and connection tracking  
> (it can
> only works, if radium would close the connection and reopen it).
>
> As a work around I'm restarting radium (without saving argus.log to my
> archive). argus.log has after restarting radium the same size, but  
> I cannot
> access information in argus.log before restart.
>
> It seems to be a bug for me. If radium should throw away old  
> information,
> why the size of argus.log is unchanged? But if the size is  
> unchanged and
> argus.log contains information before restarting radium, why I  
> cannot acces
> this information (ra, rasplit, all the same behavior)?
>
> wob
> -- 
> <wob (at) swobspace de> * http://www.swobspace.de
>