DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10206>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10206 httpd stops responding when cannot write to error_log Summary: httpd stops responding when cannot write to error_log Product: Apache httpd-1.3 Version: HEAD Platform: PC OS/Version: Linux Status: NEW Severity: Blocker Priority: Other Component: core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When fopen() return "File too large" because error_log reached filesystem filesize limit, httpd does not respond to new queries. I'm not sure if it should try to rename the file and create new file, or should it die or copy /dev/null to it? This exhibits when one kills running httpd processes and start httpd via apachectl. Then I get the message about fopen: File too large. Maybe it happens also with accesslog. Server version: Apache/1.3.26 (Unix) Server built: Jun 21 2002 11:47:33 Server's Module Magic Number: 19990320:13 Server compiled with.... -D EAPI -D HAVE_MMAP -D HAVE_SHMGET -D USE_SHMGET_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FCNTL_SERIALIZED_ACCEPT -D HAVE_SYSVSEM_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D HTTPD_ROOT="/usr/local/www" -D SUEXEC_BIN="/usr/local/www/bin/suexec" -D DEFAULT_PIDLOG="logs/httpd.pid" -D DEFAULT_SCOREBOARD="logs/httpd.scoreboard" -D DEFAULT_LOCKFILE="logs/httpd.lock" -D DEFAULT_ERRORLOG="logs/error_log" -D TYPES_CONFIG_FILE="conf/mime.types" -D SERVER_CONFIG_FILE="conf/httpd.conf" -D ACCESS_CONFIG_FILE="conf/access.conf" -D RESOURCE_CONFIG_FILE="conf/srm.conf" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
