Are you saying that you get 40/50GB of log files PER DAY.
If not, then log file/number/size is not the issue. You can always tell IIS
to start a new log on a daily basis and have a background script that
archives the log files and also cleans up in 6 month intervals (nothing says
the log file must stay on the web server for 6 months).
Also, until you run something like IISState to diagnose the IIS crashes, it
is not possible to correlate "IIS crashing due to logging". It may be custom
code you run on the server, hooked into logging, that has issues, etc. Or
maybe disk space runs out on the system partition and it causes the OS to
throw out-of-memory errors and cause issues for running programs. Etc.
Personally, I would first try to debug the actual issue on IIS5 (i.e. catch
the crash with IISState, post it here for analysis) and then decide what to
do. Until you do that, you do not know if logging is the problem -- you only
know that turning off logging, which disables a lot of other code including
logging -- but you do not know what causes the problem nor if your solution
is even relevant/correct. Only by diagnosing the crash can you validate
whether your guess is correct.
Besides, IIS6 is a complete rewrite of the web server, so even if you have
issues with logging on IIS5 now, it may not matter on IIS6 -- normal logging
may not have any problems, and remote logging may cause problems.
<a style='text-decoration: underline;' href="http://www.iisfaq.com/default.aspx?view=P197" target="_blank">http://www.iisfaq.com/default.aspx?view=P197</a>
--
//David
IIS
<a style='text-decoration: underline;' href="http://blogs.msdn.com/David.Wang" target="_blank">http://blogs.msdn.com/David.Wang</a>
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Oliver" <Oliver.TakeThisOut@noemail.com> wrote in message
news:%23QJwYvlKFHA.3064@TK2MSFTNGP12.phx.gbl...
Well our IIS is hosting about 150 sites, we have thousands and thousands log
files, we need to keep it for 6 months, the IIS log files at this point are
almost as large as the IIS data, about 40/50GB of just log files, we had IIS
crashing 4 times a day, since I stopped logging, used diskkeeper (about 20
runs) its has improved and stabilized 98%, the system is currently running
IIS 5.0 w2k SP4, so i want to get a new w2k3 box move over all sites and
start logging to a remote server so I don't run into the same problem, I've
heard people saying that remote logging might be a bad idea, it might put an
extra load on the server, so I wanted to do a reality check.
Thanks
"Jeff Cochran" <jeff.nospam.TakeThisOut@zina.com> wrote in message
news:423d50bc.181552568@msnews.microsoft.com...
> On Tue, 15 Mar 2005 15:00:48 -0500, "Oliver" <Oliver.TakeThisOut@noemail.com>
> wrote:
>
>>With IIS 6.0, is there any advantage or disadvantage on logging to a
>>remote
>>server, I've basically found that my log files are causing defrag issues
>>causing IIS to crash, so I want to dedicate a box just for logging, is it
>>against any recommendations, I would appreciate any
>>suggestion/input/advice,
>>or any write up.
>
> Advantages: Consolidation of multiple log files, logs available if
> web server is compromised, space available.
>
> Cons: If the link is down, no logs. Latency in log transfers.
> Bandwidth use for transfers.
>
> And likewise, I can't imagine any situation where logs would cause
> defrag issues resulting in a crash of IIS. Maybe if you explain the
> issues we can suggest an alternate solution.
>
> Jeff<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Remote logging 
FAQ
Search
Profile
Private Messages
Log in/Register/Password
