[Orca-users] Re: Orca reports "file xxx was current and now is not"

[ashwani rathor]

No it does not help. As I mentioned, we get the error
messages for the orca files which are stop updating
becoz new files for new day has been created. The orca
still looks for old file's and complain that they are
not current which is true.
Orca complains for the old files only once or
twice.After that it doesnot complain about the files
being old and not getting updated.
Is their any way by which we could tell orca to stop
finding the files with old-day timestamp and  start
looking for newly created files for the current date.


Thanks,
Ashwani



--- Blair Zajac <blair at gps.caltech.edu> wrote:
> From the Orca FAQ at
>
> http://www.gps.caltech.edu/~blair/orca/docs/FAQ.txt
>
> Does this help?
>
> Blair
>
>   2.2) Warning: file
> `../orcallator/.../temp-percol-2001-02-22' was
>        current and now is not.
>
>        First, Orca considers a file to be current if
> the file's last
>        modified time is within `late_interval'
> seconds of the current
>        time.  In other words, Orca checks if a
> process is modifying
>        the file to keep it current.  The
> `late_interval' value is
>        determined by the configuration file or set
> to the `interval'
>        value if the configuration file does not set
> `late_interval'.
>
>        Orca stat()s the file when it first looks for
> files using the
>        `find_files' and determines that the file is
> current.  Any time
>        after that Orca reads the file, it stat()s
> the file again and
>        determines if it is current.  If there was a
> previous stat()
>        and the file was current followed by another
> stat() and the
>        file is not current, then the message is
> printed.
>
>        The appearance of this message means that the
> process that has
>        been updating the file has stopped updating
> it and this may be
>        worth looking into.
>
>        This message is also seen when the data
> gathering program,
>        e.g. orcallator.se, opens a new log file at
> the end of a day
>        and the old log file is no longer updated.
> Orca tries to
>        manage this situation when a file is no
> longer updated at the
>        end of a day.
>
>        If the actual measurement interval is not
> consistent with
>        Orca's configuration file "interval" 300
> seconds, then Orca's
>        "interval" should be modified to match the
> actual measurement
>        interval.  If you need to do this, then
> delete the RRD files
>        because they will keep the old "interval" and
> the input data
>        will need to be reloaded into new RRD files.
>
>        Increasing the "late_interval" may also
> remove this error.
>
>
>
> ashwani rathor wrote:
> >
> > It reports these error messages for the files
> which are old.
> > For e.g we see this error messages for the files
> which stops updating
> > after 12:00AM as new files are genrated for the
> new day.In theory
> > orca should look for the newly genrated files but
> it still emails us
> > reporting that the old file xxx(which is an
> privous day file) was
> > current is now is not.Is their any configuration
> or flag need to set
> > so that once a new file is created for the new
> day, then orca should
> > probe the new file for updates.
> >
> > Ashwani Rathor
> > Sr. Unix Admin
> >
> >                    Yahoo! Groups Sponsor
> > [www.debticated.com]
> >
> >
> Terms of Service.
>


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year!  http://personal.mail.yahoo.com/