Trouble with radium (rc.44-070608)

[Carter Bullard]

Oh and one other question.  Is this a 64-bit machine?

Check to see if any of the software in your clients ./common
uses "sleep" or "usleep".  If so, then we need to replace
your radium() as some of these sleep calls are not thread
safe (discovered this on solaris on a 64-bit machine).

Carter


On Jun 18, 2007, at 2:40 PM, Carter Bullard wrote:

> Not good, and you're right, a changed state in argus should not have
> any effect on radium().  So is this a newer version, older version?
> In the system log (/var/log/messages?) radium will print status  
> messages
> as it goes through its problems.  Did you get any messages?
>
> Carter
>
>
> On Jun 18, 2007, at 2:14 PM, Wolfgang Barth wrote:
>
>> Hi,
>>
>> today radium stops working after rebooting a router running argus.  
>> radium
>> on the central machine (elix01) collects data from 6 argus  
>> sensors. 3 on elibridge,
>> and 1 on three other hosts (i.e. eligate2).
>>
>> All hosts are running and argus and radium are working. Now  
>> eligate2 was
>> rebooted. The log entries:
>>
>> Jun 18 08:49:08 eligate2 argus[1224]: 18 Jun 07 08:49:13.330699  
>> started
>> Jun 18 08:49:08 eligate2 argus[1224]: 18 Jun 07 08:49:13.331156  
>> ArgusGetInterfaceStatus: interface eth0 is up
>> Jun 18 08:49:21 elix01 radium[2515]: 2007-06-18 08:49:21  
>> ArgusReadStream eligate2: idle stream: closing
>>
>> radium is running after this, but doesn't write data to the log  
>> file. I
>> can't kill radium with kill -TERM or kill -15, I had to kill  
>> radium with
>> kill -15.
>>
>> The argus daemon is 3.0.0 from 070615.
>>
>> Rebooting one of the argus sensor should not hang up radium.
>>
>> Wolfgang
>> -- 
>> <wob (at) swobspace de> * http://www.swobspace.de
>>
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20070618/8f7e2c4a/attachment.html>