www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Wedekind <...@wedekind.de>
Subject config/1756: accept: (client socket): Operation not supported on t
Date Mon, 02 Feb 1998 15:07:22 GMT

>Number:         1756
>Category:       config
>Synopsis:       accept: (client socket): Operation not supported on t
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Feb  2 07:10:00 PST 1998
>Originator:     jan@wedekind.de
>Release:        1.2.4
OS: Solaris
	SunOS star5 5.5.1 Generic_103640-09 sun4u sparc SUNW,Ultra-1
	SunOS star4 5.5.1 Generic_103640-12 sun4u sparc SUNW,Ultra-1

Compiler: GCC
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2/specs
gcc version 2.7.2

	Server version Apache/1.2.4 (FrontPage/3.0.3)
Since mid of december 97 we caught the following error for about 
 7-10 times with three different servers (all Version 1.2.4):

After restarting the server (via -HUP) the server fails to initialize
some clients, reporting the following message into the error log:

accept: (client socket): Operation not supported on transport endpoint

The server repeats to write this message into the logfile, 
until restarted (stop & start, not HUP).
So (of course) the first times of occuring, it killed our free disk space, 
writing of about 100000 lines of error_log / minute.

This problem may be related to Problem # 872 (already closed),
but under Solaris compiling with '#define USE_FCNTL_SERIALIZED_ACCEPT'
is the default since Version 1.2.0 (see CHANGES and conf.h)
I'm sorry, but the error really rather seldom occured for now.
We aren't either available to repeat it.
Just a workaround (a small sh-skript to detect the error, restart the server
and complain about per e-mail). Called by cron very often after
midnight (log rotating) and automatically after reconfiguration of the 

if tail -1 $err | grep "(client socket): Operation not supported" >/dev/null; th
        $start 2>&1 >/tmp/checkclient.$$
        mailx -s "Warning: client socket error (restarted)" \
                root jw@de.uu.net </tmp/checkclient.$$
        rm /tmp/checkclient.$$
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]

ransport endpoint

View raw message