[Orca-users] Re: startup errors

[Blair Zajac]

That's odd.  Orca has some code in it to limit the number of open
file descriptors.  I'm assuming that you followed the directions
in step 10) of the INSTALL file in the orca-0.25 distribution
regarding ulimit and the number of open file descriptors for a
single process?

If the problem continues, you can always do this

truss -i -t open,close -o orca.truss orca -o -v orcallator.cfg |& orca.log

Compress both outputs and leave them somewhere for me to look
at.

Thanks,
Blair


bsirinek at cme.com wrote:

> From: bsirinek at cme.com
>
> Hi. I am running Orca 0.25 on an E4500 with Solaris 2.6 and get problems on
> restarting orca.
>
> I first installed Orca 0.23 maybe 2-3 weeks ago and set up two servers to be
> watched. While the orca process was running on my main server, I added
> several more servers to the mix without problems. I never stopped orca for
> this.
>
> I upgraded orca today and when I went to start it up again I got hundreds
> (seemingly) of lines giving me a "too many open files" error.
>
> They looked like this:
>
> bin/orca: warning: cannot open
> `/usr/local/var/orca/orcallator/groovy/percol-1999-10-14' for reading: Too
> many open files
>
> Because of this, I can only use orca with the first 5 or so servers in the
> bunch (I think I was watching 14 when I stopped orca to upgrade it). Its my
> hope to be able to run this tool on over 200 Sun servers. Is there some
> workaround I can do here aside from raising the number of open files on the
> system.. im sure that will help a little but I think theres a bigger issue
> here... such as do all the orcallator files need to be open simultaneously
> upon startup of orca?
>
> Please note though that eventually orca catches up with itself and generates
> graphs for all the servers. (the clients never stopped writing to their
> nfs-mounted orca directory)
>
> Thanks for any help you can give
>
> Bill Sirinek
>
>