FWD: RE: Argus, and moving 'live files'

[Carter Bullard]

Hey Guys,
   Chris, more than likely your problem doesn't have anything
to do with the file moving itself.  If Argus breaks, you will
see that your file moving strategy will suddenly stop, as
there won't be a file to move any more.  So the file moving
makes the problem much more apparent.

   Unless you are moving the file faster than once every 0.01
seconds, you shouldn't have any problems with moving the file.
I'm hoping that beta.10 will do well for you.

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134
http://qosient.com

> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu
> [mailto:owner-argus-info at lists.andrew.cmu.edu]On Behalf Of 
> Chris Newton
> Sent: Thursday, March 08, 2001 1:22 PM
> To: argus; Peter Van Epp
> Subject: RE: FWD: RE: Argus, and moving 'live files'
> 
> 
> I'll give lsof a try, next time it occurs (if it does).  It 
> seems to happen 
> randomly... and I'm wondering if the higher move rate I am 
> using, would make 
> me more likely to see the bug.  I was running fine for 3 
> days... buy my move 
> rate is 10 times higher than yours.  And, prior to that I was 
> running for many 
> days before it happened (about 2 weeks), with a prior 
> version.  I'll keep an 
> eye on it... and report anything I see.
> 
> Chris
> 
> >===== Original Message From Peter Van Epp <vanepp at sfu.ca> =====
> >	Hmmm, I've had beta.8 running on my test box on our 
> inbound link and
> >cycling every 10 minutes from cron since Mar 2 without 
> seeing such a problem
> >(FreeBDS 4.2-RELEASE). I'm just about to change that to 
> beta.10 for test
> >purposes. If you have lsof on the system you might run it 
> and see where argus
> >thinks it is writing the file (it may be writing somewhere 
> unexpected or to a
> >detached inode for some reason).
> >
> >Peter Van Epp / Operations and Technical Support
> >Simon Fraser University, Burnaby, B.C. Canada
> >
> >
> >>
> >> Bouncing this over, so everyone knows about this possible bug...
> >>
> >> Carter gave me some suggestions already, and I'll likely 
> implement them
> >> tonight.  It may take a couple of days before the problem 
> resurfaces 
> though.
> >>
> >> --------------------------
> >>
> >>    OK, first thing is to see if it happens in beta.10, as there
> >> are some fixes in beta.9 that address output files, and beta.10
> >> fixes a specific problem that caused argus to not generate
> >> output.  Hard to say that any of this addresses your problem,
> >> but gotta start with the latest.
> >>
> >> Carter
> >>
> >> Carter Bullard
> >> QoSient, LLC
> >> 300 E. 56th Street, Suite 18K
> >> New York, New York  10022
> >>
> >> carter at qosient.com
> >> Phone +1 212 588-9133
> >> Fax   +1 212 588-9134
> >> http://qosient.com
> >>
> >> > -----Original Message-----
> >> > From: Chris Newton [mailto:newton at unb.ca]
> >> > Sent: Wednesday, March 07, 2001 9:05 PM
> >> > To: Carter Bullard
> >> > Subject: Argus, and moving 'live files'
> >> >
> >> >
> >> > Hi Carter, me again :)
> >> >
> >> >   I'm having a problem with 2.0.0 beta 8.  I have it running,
> >> > daemon mode,
> >> > dumping to a file.  I also have a program (script) called
> >> > argproc, that every
> >> > minute, moves the argus log file to a filename generated from
> >> > the current
> >> > date/time.  This works well for a couple of days... then,
> >> > argus stops writing
> >> > to the file.  Ie... there is no file there for my script to
> >> > move any more.
> >> >
> >> >   Killing and restarting the argus server, fixes the problem.
> >> >  Per chance, is
> >> > there a bug that bungs up the file writing code, if the file
> >> > gets move at
> >> > 'just the right time'?  This has happened a couple of times now.
> >> >
> >> >   Hmm, also... argus seems to be still working.. using the
> >> > same amount of cpu
> >> > as normal... just not writing to the argus output file anymore.
> >> >
> >> > Chris
> >> >
> >> > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> >> >
> >> > Chris Newton, Systems Analyst
> >> > Computing Services, University of New Brunswick
> >> > newton at unb.ca 506-447-3212(voice) 506-453-3590(fax)
> >> >
> >> >
> >>
> >> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> >>
> >> Chris Newton, Systems Analyst
> >> Computing Services, University of New Brunswick
> >> newton at unb.ca 506-447-3212(voice) 506-453-3590(fax)
> >>
> >>
> 
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
> Chris Newton, Systems Analyst
> Computing Services, University of New Brunswick
> newton at unb.ca 506-447-3212(voice) 506-453-3590(fax)
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20010308/77aef845/attachment.html>