IIS6 - Application pool recycle
Stephane
I have a webserver with several applications pools configured. Basically the
difference in the config between apps pools are the recycling timing and idle
timeout. When I look in the events, I see only one of the apppool recycling
events. Or due to the setup and the web server's activity it is not normal.
So what are the others not recycling? Where can I find log of the activity?
Maybe it is related to the "structure" of the pools : I have a "generic"
Apppool on the root folder for all asp applications. After that, I setup
virtual directories and corresponding pools on folders wich are located under
this root folder. So maybe this wrong and I need to suppress this "root" pool?
Thanks for the help you can give
David Wang
wrote:
By default, recycling caused by expected events which trigger health
monitoring metrics of the Application Pool are not logged. Thus, idle-
timeout are not logged by default.
You will have to tweak the "LogEventOnRecycle" metabase property to
change this behavior and make IIS log event log entries for any/all of
the recycles, even expected/non-interesting ones.
It sounds like someone manually set this value on one Application
Pool. The ones you created do not inherit such settings. Personally, I
would revert the changes on that one noisy Application Pool. because
IIS will already log events on the exception events that need
administrator attention. Telling IIS to log everything simply makes it
noisy (and is the reason why it is suppressed by default), but there
are paranoid administrators who want to know everything and do the
filtering themselves -- hence the feature).
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Stephane
"David Wang" wrote:
> On Oct 20, 2:04 am, Stephane <Steph...@discussions.microsoft.com>
>
> It sounds like someone manually set this value on one Application
As it is only me which act on this server, ... I dont remember I do that, it
was probably a long time ago, .. I will look into the metabase -:)
> Pool. The ones you created do not inherit such settings. Personally, I
> would revert the changes on that one noisy Application Pool. because
> IIS will already log events on the exception events that need
> administrator attention. Telling IIS to log everything simply makes it
> noisy (and is the reason why it is suppressed by default),
Just it is a good way to find crash on the server.
Thanks for the info. I will search for the list of events that iis log for
admin, because I dont find these messages and I'am quite sure there are
applications with bugs on it , and I need to find it
David Wang
wrote:
No, LogEventOnRecycle is NOT a good a way to find crash on the server.
It is an excellent way to LOSE track of crashes on the server.
By default, a crash counts as an unexpected event and is logged no
matter what, even with the default settings, so making IIS noisy about
app pool recycling really just buries those crash events because now
IIS also logs events for normal, expected recycling metrics.
Anyways, the setting depends on the type of administrator you are.
Either you want to only be told about something bad happening, or you
want to be told about everything and you do the filtering to determine
what is bad.