[Orca-users] Re: How many orca installations

[Blair Zajac]

"Lightfoot.Michael" wrote:
> 
> > Other ideas included using SSH (which we do use for DMZ hosts), but we
> > didn't want a single host with access to everything.   Or simply
> > creating a web page that linked to each host's orca page
> > (which I didn't
> > think of at the time).
> >
> > How are you folks out there doing this?
> >
> I am currently testing using rsync over ssh to transfer the files to a
> central box.  The reason for this is not paranoia about the security of our
> internal network but so that I can use a similar mechanism on our DMZ boxen
> as on our internal servers.
> 
> The DMZ boxen will have to use an rsync server on the firewall management
> system (the only system with more than single protocol access to the DMZ.)
> 
> The only slight glitch so far is the following message every now and again:
> 
> "Orca: file `/work/orca/var/orca/orcallator/griffin/percol-2001-10-31' was
> current and now is not."
> 
> which I assume is due to the 4 times a day transfer updating the files
> "unexpectedly" as far as Orca is concerned.
> 
> michael

Yes, the message your getting is due to the 4 times a day transfer.  Here's
some more info from the FAQ.

  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.

Blair

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