You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Christine Chan <Py...@yahoo.com> on 1998/11/13 16:03:53 UTC
os-solaris/3399: Log files are not written
>Number: 3399
>Category: os-solaris
>Synopsis: Log files are not written
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: support
>Submitter-Id: apache
>Arrival-Date: Fri Nov 13 07:10:00 PST 1998
>Last-Modified:
>Originator: Pye_cc@yahoo.com
>Organization:
apache
>Release: Apache 1.3.1
>Environment:
SunOS 5.5.1 Generic_103640-23 sun4u sparc SUNW, Ultra-Enterprise
>Description:
Once in a while, Apache will stop writing any log files.
Our server is configured to write a new log file for each
virtual host for each new day, while the log file for the
previous day is archived away.
Anyway, once in a while, Apache don't write any log files,
but it still runs quite happliy, until we discover the
problem and give it a reboot.
Any ideas why Apache does this and how to stop it from doing it
again?
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[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! ]