David
Wed Jun 20 21:55:01 CDT 2007
On Jun 20, 10:17 am, "John Grandy" <johnagrandy-at-gmail-dot-com>
wrote:
> On IIS6 WS03 , what could causes temporary inability of iis to write to its
> log files ? Could memory or cpu load cause such an occurrence ? Is it
> possible that some other process besides the w3wp hosting iis could obtain a
> lock on the log files ( is the iis w3wp hoting other apps ) ? Something
> else ?
>
> The web app continues to function (albeit slowly) but expected log entries
> are missing
HTTP.SYS does not immediately write the log entries for IIS6. They are
buffered in memory and periodically flushed to disk.
My first question would be if you are looking for the expected log
entries too soon. Wait a minute or two after the request and they
should appear.
My second question would be to verified that the requests are actually
routed to this server. I have seen many people blame "missing log file
entry" when their DNS or IIS website was misconfigured such that the
requests actually went to another server/website in backup/test/
production, or that the LogFileDirectory was configured to go
elsewhere.
Basically, please prove that the request actually got to this
particular server, was handled by IIS, and that the log entry for the
request does not show up in the configured LogFileDirectory after
waiting 90 seconds.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//