On Jul 9, 2004, at 11:38 AM, Davina Treiber wrote:

Thorsten Linow wrote:

Hi,
After upgrading Legato Networker 6.1.3 towards 7.1.2 we got lots of
"service at 0.0.0.0/5833error from accept call: Too many open files"
messages in the daemon.log, during heavy load caused by obviously
too many client connection requests.
The Legato Networker Server was busy near death, nsrd occupied
one CPU by 100% but the Server was more or less idle.
We had semilar situations several times in the past but we got no
clue why.
Just since we upgraded we got this detailed messages in the
daemon.log,
so now we know where to start to investigate.

YOU can't fix this. The "too many open files" message is fatal. The
only
solution is a patch to NetWorker, since this is a bug. You need to take
this up with Legato Support.

No necessarily.  If the accept(2) system call is returning a 'too many
open files' error, you need to adjust your operating system to allow
either more open files per process or allow more open files for the
entire system.  It probably means that there are too many network
connections happening at once.  Alternatively, reduce the number of
clients being backed up at one time.

Having a system showing 100% busy but being basically idle is often
seen when the system is pushing too much data and the CPU has to wait a
lot, by the way.

Byron

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=