/etc/init.d/apache2 restart produces error

Bug #153863 reported by Tomas Cassidy
6
Affects Status Importance Assigned to Milestone
Apache2 Web Server
Fix Released
Critical
apache2 (Debian)
Fix Released
Unknown
apache2 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: apache2

/etc/init.d/apache2 restart produces the following error in /var/log/apache2/error.log:

[error] (9)Bad file descriptor: apr_socket_accept: (client socket)

full contents of error.log:

[Thu Oct 18 20:46:00 2007] [notice] caught SIGWINCH, shutting down gracefully
[Thu Oct 18 20:46:00 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Oct 18 20:46:00 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Oct 18 20:46:00 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Oct 18 20:46:00 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Oct 18 20:46:00 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Oct 18 20:46:11 2007] [notice] Digest: generating secret for digest authentication ...
[Thu Oct 18 20:47:18 2007] [notice] Digest: done
[Thu Oct 18 20:47:19 2007] [notice] Apache/2.2.4 (Ubuntu) DAV/2 PHP/5.2.3-1ubuntu6 mod_ssl/2.2.4 OpenSSL/0.9.8e configured -- resuming normal operations

Sorry if this bug report is a duplicate/incomplete (first bug post :-) ).

description: updated
Revision history for this message
Soren Hansen (soren) wrote : Re: [Bug 153863] /etc/init.d/apache2 restart produces error

On Thu, Oct 18, 2007 at 10:51:58AM -0000, TomasCassidy wrote:
> /etc/init.d/apache2 restart produces the following error in
> /var/log/apache2/error.log:
>
> [error] (9)Bad file descriptor: apr_socket_accept: (client socket)

Did you just stumble upon in the log files or is it actually causing you
any trouble?

--
Soren Hansen
Ubuntu Server Team
http://www.ubuntu.com/

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

I just noticed it after doing a routine check of my log files. I found the same bug reported with debian (#400918), so I thought I might as well submit a bug here. I haven't really noticed it being a problem with anything (yet).

Revision history for this message
Soren Hansen (soren) wrote :

Thanks for your quick response. It smells like it might be this upstream bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=42829

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

It seems like it, after reading that bug report. I remember having some issues after restarting apache, it would complain with some errors about pid files. I can't seem to find these errors in any log files, but I haven't looked too hard though.

Mathias Gug (mathiaz)
Changed in apache2:
status: New → Incomplete
Changed in apache2:
status: Unknown → Confirmed
Changed in apache2:
status: Unknown → Fix Released
Changed in apache2:
status: Confirmed → Unknown
Changed in apache2:
status: Unknown → Confirmed
Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Hardy Heron. It won't be fixed in previous versions of Ubuntu because the bug doesn't fit requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Changed in apache2:
status: Incomplete → Fix Released
Revision history for this message
Paul Neaveill (boycotthell2005) wrote :

How do we get the apache update or whatever the thing is, as it grocked my webserver and I cannot wait until HH comes out in the spring?

06 21:29:37 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [notice] caught SIGWINCH, shutting down gracefully
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:09 2007] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu Dec 06 21:54:19 2007] [notice] Apache/2.2.4 (Ubuntu) PHP/5.2.3-1ubuntu6.2 configured -- resuming normal operations

Changed in apache2:
status: Confirmed → Incomplete
Changed in apache2:
status: Incomplete → In Progress
Revision history for this message
seanscullion (sean-choonz) wrote :

I've just been googling this error message and was brought here - I'm getting this message in Ubuntu

Kubuntu 7.10 GUTSY
Linux: 2.6.22-16-generic

I get this when attempting to stop apache2 (or restart)
> sudo /etc/init.d/apache2 stop

==> error.log <==
[Tue Jan 06 15:48:48 2009] [notice] caught SIGWINCH, shutting down gracefully
[Tue Jan 06 15:48:48 2009] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Tue Jan 06 15:48:48 2009] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Tue Jan 06 15:48:48 2009] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Tue Jan 06 15:48:48 2009] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Tue Jan 06 15:48:48 2009] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)

I found this coz I'm having other errors to do with configuring multiple SSL hosts (with multiple IPs) under a single apache installation. I do not know if this error message is related to my SSL problem - yet - but is there a simple way to fix this problem without taking the full risk involved with going over to Hardy Heron?

Thanks,

Sean

Changed in apache2:
status: In Progress → Fix Released
Changed in apache2:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.