[Orca-users] Re: I know I've seen this error before on this list

[John Mastin]

Hmm, this does seem to explain things better.  I am updating graphs
every hour.  Just before the 'updater' cronjob gets fired off, I go out
and collect the data from my Orca clients (via rsync).  It is then
normal for Orca find them to be not current because I am only updating
them once an hour.


Thanks for the help!
Johnny


Blair Zajac wrote:
> 
> Here's an answer to this question from a work in progress FAQ:
> 
>   1.4) What does the message "file `/orca/olympis/percol-2000-07-12'
>        was current and now is not" mean?
> 
>        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.
>