Time stamp is 5 hours ahead in httperr.log (IIS 6.0)

[David Wang]

What timezone is the server configured to run in, and are you observing
daylight savings time?

You can't ever assume timestamps are in local timezone. For
example,suppose you copy the log file from a server on US east cost
onto a machine on US west coast - if you treat timestamp as local
timezone, you'll be three hours off in your analysis.



//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Hni,
We have been having some issues with a website we ceated nd when we look at
the httperr.log the time stamp appears to be 5 hours ahead. When I look at
another 2003 server I see the same thing happening.
Is this normal behavior for IIS 6.0??

[David Wang]

Then everything you observed with HTTPERR.LOG is normal and correct.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

We are on the east coast US and the server is configured for East cost time.
We have checked the time and date on the server. Everything appears to be
correct.
Thanks,
Angelo

Post by David Wang
What timezone is the server configured to run in, and are you observing
daylight savings time?
You can't ever assume timestamps are in local timezone. For
example,suppose you copy the log file from a server on US east cost
onto a machine on US west coast - if you treat timestamp as local
timezone, you'll be three hours off in your analysis.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Hni,
We have been having some issues with a website we ceated nd when we look at
the httperr.log the time stamp appears to be 5 hours ahead. When I look at
another 2003 server I see the same thing happening.
Is this normal behavior for IIS 6.0??

[Ken Schaefer]

All times logged are logged in GMT time, which is 5 hours ahead of US East
Coast time. That is part of the w3 spec.

Cheers
Ken

We are on the east coast US and the server is configured for East cost
time.
We have checked the time and date on the server. Everything appears to be
correct.
Thanks,
Angelo

Post by David Wang
What timezone is the server configured to run in, and are you observing
daylight savings time?
You can't ever assume timestamps are in local timezone. For
example,suppose you copy the log file from a server on US east cost
onto a machine on US west coast - if you treat timestamp as local
timezone, you'll be three hours off in your analysis.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Hni,
We have been having some issues with a website we ceated nd when we look at
the httperr.log the time stamp appears to be 5 hours ahead. When I look at
another 2003 server I see the same thing happening.
Is this normal behavior for IIS 6.0??