Latest clients look to have broken archive file movement

Peter Van Epp vanepp at sfu.ca
Thu Jun 21 11:07:40 EDT 2007


On Wed, Jun 20, 2007 at 10:05:39PM -0400, Carter Bullard wrote:
> Hey Peter,
> Did you get any since of what was going on?
> Carter
> 

	No not yet (time is very lacking right now as you have probably noticed
by the lack of output :-)). I'm about to move back to an earlier client release
since it didn't used to do this (it is dead again this morning in the same
way). Then I'll try a different machine in case its the Mac doing something. 

ps auxwwww | grep ra3
vanepp     638   0.1 -0.1    30360   1480  p3- S     4:54PM   1:58.54 /usr/local/bin/ra3 -S 192.75.244.191:561 -n -w /var/log/argus/c4_argus
vanepp     637   0.0 -0.1    30360   1676  p3- S     4:54PM   5:11.09 /usr/local/bin/ra3 -S 192.75.244.191:560 -n -w /var/log/argus/com_argus

and it died again around 1 AM:

test4:/var/log/argus vanepp$ ls /archive/argus3/com_argus.archive/2007/06/21
com_argus.2007.06.21.00.00.00.0.gz      com_argus.2007.06.21.02.00.00.0.gz
com_argus.2007.06.21.01.00.00.0.gz

	There is currently no com_argus or c4_argus output file and the ra's
will likely need to be killed with -9 because -HUP won't stop them. Luckily
my tar store is on a netap and I should be able to extract an earlier version
of rc.44 from the snapshots to try that.

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada



More information about the argus mailing list