AccessLogFile Fail Fallback
Brian Smither
14 March 2016, 06:36
Last week, I had the designated log file (for a particular VirtualHost) open in an editor for a very brief amount of time, and made some edits, while Hiawatha 9.3 (upgrading is on my TODO list) was still running.
I now find that nothing has been logged to that file since that time.
Is it conceivable that Hiawatha found a problem accessing that log file and defaulted to not writing to it anymore? (I do not know if the editor locks the file.)
Should there be an entry in the system log or VirtualHost error log?
Brian Smither
14 March 2016, 06:42
I have verified that the editor says it does not lock files while it has the file loaded for editing.
Windows 2008 R2 SP1
Hugo Leisink
14 March 2016, 08:31
Probably the ownership of access rights has changed, which caused Hiawatha to no longer have access to the logfile.
This topic has been closed.