This could be an inetd issue, if you have a whole lot
of disklist entries pointing to the server in question.

Rate limiting is a common inetd feature.  The idea is that
more than some number of requests per unit time means the
same request is coming in repeatedly, and the server isn't
satisfying it.

As anybody who has ever tried to run even a moderatly busy SMTP 
server over inetd has discovered, this feature, while preventing
machine meltdown due to overspawning a failing server, may also
bring about server failures under slightly different circumstances.

Of course this was not unexpected, and inetd makes allowances
for this.  See "man inetd".  At least on Linux.  I'd expect
similar allowance on Solaris, too.

>From "man 5 inetd.conf", an entry like

amanda     dgram udp wait.100   amanda /usr/libexec/amandad amandad

specifies that 100 server processes may be spawned in one minute.

On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote:
> I have Solaris 8 box using Amanda 2.4.2 (client).  And when I run
> amcheck from the tape server I get the following errors on the console:
> 
> Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning]
> /var/adm/amanda/libexec/amandad: Killed
> Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp
> server failing (looping), service terminated
> 
> I thought it was an issue pertaining to the OS version only.  But I
> have been able to use amanda on other 5.8 boxes.  The only differance
> is that I used different GCC to compile the software.  The failing box
> uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the
> compiler).
> 
> Has anybody seen issues of this variety by chance.  I'm not sure if
> this is even related to the gcc rev.
> 
> Thanks for any advice.
> 
> Don Potter
> 
> 

-- 
-----------------------------------------------------------------
 Dan Wilder <[EMAIL PROTECTED]>   Technical Manager & Editor
 SSC, Inc. P.O. Box 55549   Phone:  206-782-8808
 Seattle, WA  98155-0549    URL http://embedded.linuxjournal.com/
-----------------------------------------------------------------

Reply via email to