[Orca-users] Re: orcallator.cfg.lock

[Blair Zajac]

Matthew Boeckman wrote:
> Hello list!
> 
>      I've been running orca on a sol7 box for over a year now and I love
> it. Using the se toolkit of course. I run start_orcallator to bring it
> all up, then rsync the data to a central server that generates the
> graphs. I recently installed all of AC's stuff as well as orca on a new
> 7 box and am getting some weird results.

What is the AC stuff?

> The graphs from that server
> have an awful lot of flatlining in them. Admittedly it's only been
> running for a few days, but even the daily's will show hours of
> seemingly no usage then a little "regular" looking spike. The box is
> under pretty heavy load, so I'm sure this isn't entirely accurate. The
> only difference that I can see between the two boxes is that on the
> misbehaving machine, no orcallator.cfg.lock gets created in
> /usr/local/lib, as it does on the happy box.

Orca creates the orcallator.cfg.lock, not orcallator.se.  Orca names the
lock files on the name of the configuration file, which in this case is
orcallator.cfg.

> I don't know if this has
> anything to do with anything, but it's all I've got. Both boxes are
> running orcallator as root, and (obviously) have permissions to write to
> /usr/local/lib.

Which SE and orcallator.se are you using?

You can run orcallator.se by hand and see if the data makes any sense
with other programs, such as top.

Best,
Blair

> 
> I start orca on the sad machine with start_orcallator, and ps reports
> the same process command line as the other machine. Any thoughts?
-- 
Blair Zajac <blair at orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/