[Orca-users] RE: Adding Removing graphs and plots

[Andrew Broad]

Hi

Setting the file decriptor limit to 1024 fixed the problem regarding "Too
many open files" however I still get the errors regarding "expecting RRD
name  no data loaded from etc" All I am doing is commenting out the plots on
the orcallator.cfg file which seems to work for everybody but me :o( any
ideas would be greatly appreciated.

Regards

Andy

> RSS  VSZ %MEM        TIME     USER   PID COMMAND
> 7144 7960  0.3        0:05     root 11194 /usr/local/bin/perl
> Current running time is 0:09 minutes.
> Loading new data from group orcallator for hostname1.
> Loading new data from group orcallator for hostname2.
> Odd number of elements in hash assignment at
> /usr/local/lib/Orca/SourceFile.pm
> line 876, <FD> line 2.
> /usr/local/bin/orca: internal error: expecting RRD name
> `orcallator_hostname2_g
> auge_1024_*_8_*_hme0InKB/s' but no data loaded from
> `/usr/local/var/orca/orcall
> ator/hostname2/percol-2001-11-16-000' at time Fri Nov 16 14:00:01 2001
> (1005919
> 201).
-----Original Message-----
From: Blair Zajac [mailto:blair at orcaware.com]
Sent: Tuesday, April 23, 2002 6:57 PM
To: orca-users at yahoogroups.com
Subject: Re: [orca-users] Adding Removing graphs and plots


Andrew Broad wrote:
>
> I have Orca running successfully on my test systems and want to get rid of
> the plots and html graphs for NFS stuff as we dont use it as well as all
the
> graphs and plots that are web related. I tried to comment out the plots in
> the orcallator.cfg file and it works as far as not showing the NFS/Web
> graphs etc when it rebuilds the index.html file but produces a lot of
errors
> into the orca.log file such as below. Is it a just a matter of commenting
> out the plots in the orcallator.cfg or do I need to do something else.
>
> /usr/local/bin/perl -w /usr/local/bin/orca -v
/usr/local/bin/orcallator.cfg
> > /tmp/orca.log 2>&1 &
>
> Below is a short extract from the orca.log file.
>
> <Orca.log>
>
> Orca version 0.264 using RRDs version 1.000331 at Tue Apr 23 11:24:46
2002.
> Loading state from `/usr/local/var/orca/rrd/orcallator/orca.state'.
> Creating orca.gif.
> Creating rrdtool.gif.
> Finding files and setting up data structures at Tue Apr 23 11:24:46 2002.
> /usr/local/bin/orca: warning: cannot open `gunzip -c
> /usr/local/var/orca/orcall
> ator/hostname2/percol-2002-01-12-000.gz |' for reading: Too many open
files
> /usr/local/bin/orca: warning: shrinking maximum number open files to 56.

This is the first problem I would start off handling.  You need to increase
the number of open file descriptors available to Orca.

>From the FAQ, follow these steps:

  2.3) Warning: cannot create Orca::HTMLFile object: cannot open
       `/home/orca_html/o_host1-monthly.html.htm' for writing: Too
       many open files.

       This obviously happens with Orca runs out of open file
       descriptors.  Orca opens many file descriptors to do its work
       and it doesn't like to close them unless it needs to.

       The first thing to check is the maximum number of file
       descriptors each process can have.  On some systems, the login
       shell scripts lower the maximum number of open file descriptors
       a process may have.

       To check this in a Csh shell variant (csh, tcsh), then type

         limit descriptors

       or for Bourne shell variant (sh, bash), then type

         ulimit -n

       On all operating systems Orca should be able to use 256 file
       descriptors.  On some, such as Linux, Orca can open 1024 files
       at once.  If the number you are getting is less than 256, then
       raise this limit.  Some operating systems let you raise the
       limit. such as Solaris, while others do not, such as Linux.  To
       try to raise the limit, do

         limit descriptors 1024

       or

         ulimit -n 1024

       If these commands do not work, ask your system administrator
       how to do this.

       There is a bug in Orca's older than 0.27b2 where Orca would not
       close a pipe file descriptor that is uncompressing a compressed
       percol-* file to Orca.  If your percol-* files are compressed,
       then try either upgrading to 0.27b2 or later or apply the patch


http://www.orcaware.com/orca/pub/patches/orca-0.26-defunct-processes-patch.t
xt

       to Orca 0.26.  This should have Orca reduce its file descriptor
       count.


> RSS  VSZ %MEM        TIME     USER   PID COMMAND
> 7144 7960  0.3        0:05     root 11194 /usr/local/bin/perl
> Current running time is 0:09 minutes.
> Loading new data from group orcallator for hostname1.
> Loading new data from group orcallator for hostname2.
> Odd number of elements in hash assignment at
> /usr/local/lib/Orca/SourceFile.pm
> line 876, <FD> line 2.
> /usr/local/bin/orca: internal error: expecting RRD name
> `orcallator_hostname2_g
> auge_1024_*_8_*_hme0InKB/s' but no data loaded from
> `/usr/local/var/orca/orcall
> ator/hostname2/percol-2001-11-16-000' at time Fri Nov 16 14:00:01 2001
> (1005919
> 201).

Let me know if these continue after the first problem is handled.

Best,
Blair

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







*************************************************************************   
This message is intended only for the stated addressee(s)
and may be confidential.  Access to this email by anyone
else is unauthorised. Any opinions expressed in this email
do not necessarily reflect the opinions of royalblue.
Any unauthorised disclosure, use or dissemination,
either whole or in part is prohibited,.   If you are not the
intended recipient of this message, please notify
the sender immediately.
*************************************************************************