On 9/10/07, Bernd Eidenschink <[EMAIL PROTECTED]> wrote:
> > > The last log entry is from yesterday 23:04 (when the last developer went
> > > home), no new access file since then.
> >
> > Did the partition fill up?
> >
> > $ df -h
> >
> > Or maybe the directory where the log files live was deleted/moved/had
> > it's permissions changed...?
>
> No, enough space; no logrotate stuff that could interfere, no cronjobs that
> change permissions, no rsync from other servers or things like that...
> The access-log is in the same directory as the server.log and the pidfile
> (logs/) on this server.
There's no error messages that match this pattern?
"nslog: logging disabled: write() failed: '%s'"
You're saying you only nslog error message you get is:
"nslog: flush failed: '%s'"
Are you sure? This doesn't make sense to me...
As far as I can see "nslog: flush failed: '%s'" is logged from
LogTrace() when LogFlush() returns NS_ERROR.
LogFlush() returns NS_ERROR when:
1) logPtr->fd == -1 anyway (log file closed)
2) write() fails within LogFlush()
In the second case, logPtr->fd is set to -1 and an error is logged.
The error is then logged again in LogTrace(), which is wrong because
firstly the error is already logged and secondly errno will be
overwritten by the call to close() so the second message will be
'Success'.
But you would expect to see a log message of type: "nslog: logging
disabled: write() failed: '%s'".
In the first case the extra log message in LogTrace( ) is also wrong,
because there's been no previous failing system call to set errno.
But for fd to equal -1 somewhere along the line there should have been
another log message to say what failed.
Even though the error logging in LogTrace() is wrong, I don't see how
it could happen without your log file actually being closed, which it
shouldn't be.
Scan the error.log for 'nslog:' messages....
Things which could have caused the log file to be closed are:
- write() failed: disk full, file too large, ...
- log roll failed: either scheduled or on signal
- someone changed the logfile with a call to ns_accesslog
LogOpen() should have caught most of those with:
"nslog: error '%s' opening '%s'"
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
