[Orca-users] Re: Nightly "did exist and is now gone" email messages

[Blair Zajac]

We'll have to fix this.  I noted a bug report for it, but I don't have the
time to look at it now, so if anybody wants to take a crack at it, I'd
apprecaite it.

Best,
Blair

Leewa wrote:
> 
> Douglas, Blair,
> 
>     I have just installed orca 0.27b2 with
> orcallator.se version 1.32 and orcallator.cfg version
> 1.32.  I have it running on an Ultra 60 just to test
> out orca.  I'm pretty much running orca with
> essentially the default configuration.  The only
> exceptions would be the locations of the RRD files and
> HTML files.  Seems to work nicely, but I am getting
> same e-mails as Douglas describes.  The last few
> nights I've had e-mails sent to me around 12:00am,
> 12:06am, and 12:11am.  The e-mails aren't really a
> problem, but like Douglas says, I would rather be
> getting "real" e-mail failure messages.  I'm not sure
> why I'm getting these messages.  I'll continue to let
> my test system run and see if it is consistent.
> 
>     Oh, I should say that I am running both the
> orcallator.se and orca programs on the same system.  I
> store all of the RRD data locally and write out the
> HTML files to a separate remote NFS mount which is the
> local disks for our web server which hosts those
> resulting pages.
> 
> Wayne Lee
> Systems Administrator
> Amerada Hess Corp.
> **************************************************************************
> "UNIX_IS_ user friendly, its just picky about who its
> friends are."
> **************************************************************************
> 
> --- Douglas Valkenaar <workmail at valkenaar.net> wrote:
> > At 07:48 PM 11/8/01, Blair Zajac wrote:
> > >Douglas Valkenaar wrote:
> > > >
> > > > At 10:51 AM 11/8/01, you wrote:
> > > > >Douglas Valkenaar wrote:
> > > > > >
> > > > > > Every night after setting up Orca and the
> > orcallator I'm receiving
> > > > > messages
> > > > > > such as:
> > > > > >
> > > > > > Orca: file
> > >
> >
> `/proj/atria/etc/orcallator/trout/orcallator-2001-11-06-000'
> > > > > did
> > > > > > exist and is now gone.
> > > > > >
> > > > > > I get two of them and then they stop until
> > the next night.  Does
> > > anyone
> > > > > > know the cause of this?
> > > > > >
> > > > > > Thanks in advance.
> > > > >
> > > > >Douglas,
> > > > >
> > > > >I just added this question to the FAQ at
> > > > >
> > > > >
> > http://www.orcaware.com/orca/docs/FAQ.txt
> > > > >
> > > > >   2.4) Warning: file
> > `.../orcallator/host1/orcallator-2001-11-06-000'
> > > > >        did exist and is now gone.
> > > > >
> > > > >        Orca prints this message when it found
> > an input data file to
> > > > >        read and when it goes to read it, which
> > may be a while later,
> > > > >        the file no longer exists.
> > > > >
> > > > >        When Orca is being used with
> > orcallator.se, this message may
> > > > >        occur when orcallator.se compresses the
> > previous day's
> > > percol-*
> > > > >        or orcallator-* file that Orca found.
> > > > >
> > > > >Are you compressing or removing the percol-* or
> > orcallator-* data
> > > files at
> > > > >some point in the day?
> > > >
> > > > They are being compressed by 'orcallator.se' -
> > probably about that
> > > > time.  Do you think there's some way to tweak
> > the timing of events to
> > > avoid
> > > > this happening?  While it's simply an annoyance,
> > I'd really rather only
> > > get
> > > > real failure messages.
> > > >
> > > > Thanks for the response!
> > >
> > >I don't know why you're seeing them.  Orca has code
> > to check if the file
> > >was
> > >up to date and then is not up to date to warn the
> > administrator but not if
> > >the day of the month has changed, for example when
> > orcallator.se is not
> > >using compression is, used and then it starts
> > writing to a new file at the
> > >end of the day.
> > >
> > >However, this isn't true for the warning you're
> > seeing.
> > >
> > >Can you look exactly when you're getting the
> > messages and when
> > >orcallator.se
> > >is compressing the files?  This would help.
> >
> > The files appear to be getting compressed at
> > 11:57pm, and since *all* the
> > files have the same date/time stamp, I assuming this
> > isn't taking too long
> > (under a minute for the six machines we're
> > monitoring).
> >
> > I receive two messages per machine, at 12:02 and
> > 12:08am, every day.  I'm
> > using the (essentially) default configuration as
> > delivered by both packages
> > so I assume there must be other users experiencing
> > the same thing.
> >
> > Thanks.
> >
> > --
> > Douglas Valkenaar, Tools and SCM Architect
> > LSI Logic - Milpitas, CA
> > 408.954.3296/408.234.5296 (cell)

-- 
Blair Zajac <blair at orcaware.com> - Perl & sysadmin services for hire
Web and OS performance plots - http://www.orcaware.com/orca/