www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Conover <ccono...@mmxi.com>
Subject general/6109: Apache dies, too many open files in error log
Date Tue, 23 May 2000 13:48:16 GMT

>Number:         6109
>Category:       general
>Synopsis:       Apache dies, too many open files in error log
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue May 23 06:50:00 PDT 2000
>Originator:     cconover@mmxi.com
>Release:        1.3.12
SunOS etcs07.cold.mmxi.com 5.7 Generic_106541-10 sun4u sparc SUNW,UltraSPARC-IIi
I am running apache 1.3.12 on solaris 2.7
Once every 4 hours (cron) I move the apache logs and then send a kill -USR1 <apache pid>
command to apache to recycle them. I then archive the logs. After about a week apache stops
responding and the message in the error log says too many open files Accept: (client socket)
I tried raising the file descriptor limit but that just makes it last a bit longer. Sound
like a leak maybe or something is wrong with the kill command. This wasnt posted on the news
group, I tried but had problems with deja (sorry)
Run apache 1.3.12 and send a kill -USR1 <apache pid> every minute. Should stop responding
in about an hour
Maybe use a different signal in the kill command 
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message