[Orca-users] Orca is eating up both my CPUs.

[Blair Zajac]

"Camron W. Fox" wrote:
> 
> Alle,
> 
>         We've been running orca in daemon mode for around two days now and it has
> sustained this CPU usage level almost constantly.

Orca's known to take a lot of CPU power.  What people commonly do is
run them in "run once mode" with the -o option via cron.  Run it
once, twice, or more times a day as needed.

> 
> CPU0 states: 54.1% user,  3.1% system,  0.0% nice, 42.2% idle
> CPU1 states: 48.0% user,  4.3% system,  0.0% nice, 47.1% idle
> Mem:   772200K av,  729748K used,   42452K free,       0K shrd,   30772K
> buff
> Swap:  530136K av,   52640K used,  477496K free                  471440K
> cached
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
> 27307 root      25   0 63460  60M  4536 R    91.6  8.0  1328m orca
> 
> We are running on Linux 7.3 2.4.18-17.7.xsmp and are
> monitoring and are currently monitoring 81 systems.
> 
> We have been receiving the alot of the following types of errors for all
> systems from /var/log/orca:
> 
> /usr/local/bin/orca: number of columns in line 130 of
> `/usr/local/var/orca/orcallator/g21/orcallator-2002-09-24-000' does not
> match column description.

Make sure you're using the latest orcallator.se and orcallator.cfg.
It'll work around these issues.  You can get them from

http://www.orcaware.com/orca/pub/orca-0.27b3.tar.gz

> 
> Also, we are getting alot of the following email messages for all systems:
> 
> Orca: file
> `/usr/local/var/orca/orcallator/a01/orcallator-2002-08-17-000.bz2' was
> current and now is not.
> 
>         and
> 
> Orca: file `/usr/local/var/orca/orcallator/g24/orcallator-2002-11-07-000'
> did exist and is now gone.
> 
>         Both of these I'm sure are because of the rsync we have to run to get the
> data from the customer's machines on to our server (an ssh rsync job) and
> the info conflicts with the state file, but is there any way to avoid it?

Comment out the warn_email line in your orcallator.cfg file.  These
warnings are designed to warn you when your orcallator.se dies for
whatever reason.

The first happens because you're using rsync instead of keeping the
files up to date continuously if you had NFS mounts.

You may want to run orca after you run rsync on your systems.

Best,
Blair

-- 
Blair Zajac <blair at orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/