Prev: IIS 7 Catastrophic Failure :: COMException :: Microsoft.JScript
Next: Problem solved!!!
From: Bill Glidden on 15 Nov 2009 21:32
I have been wondering why my system volume of my SBS 2008 keeps running
out of disk space. I now see that c:\inetpub\LogFiles\W3SVC1372222313\
contains a bajillion u_ex*.log files, totalling 67.1GB. Is this
something I�m supposed to be managing or is something wrong? They range
in date from mid-August to today. The files are frequently over 1GB in
size. The server has been commissioned since August.
From: Steve Schofield on 16 Nov 2009 01:08
You can write a script to remove log files or compress them. I wrote a
utility called IISLogs to help resolve this exact thing. With IISLogs or
some zip program, you'd regain about 90% of your disk space. If you
schedule with something like task scheduler, it would run daily.

Shameless plug
http://www.iislogs.com

You could use a powershell script, vbscript or something else.

Steve Schofield
Microsoft MVP - IIS


"Bill Glidden" <bill(a)glidden.net.au> wrote in message
news:O4iqNUmZKHA.1592(a)TK2MSFTNGP06.phx.gbl...
>I have been wondering why my system volume of my SBS 2008 keeps running out
>of disk space. I now see that c:\inetpub\LogFiles\W3SVC1372222313\ contains
>a bajillion u_ex*.log files, totalling 67.1GB. Is this something I�m
>supposed to be managing or is something wrong? They range in date from
>mid-August to today. The files are frequently over 1GB in size. The server
>has been commissioned since August.


From: .._.. on 16 Nov 2009 14:11
Yes, you should be managing them. Depending on what information you are
getting (probably not much, if you didn't know they were that large) you can
zip them up and delete the originals, make reports and then delete the
originals, or just delete them.

I would STRONGLY ADVISE moving them to a separate partition so they do not
fill up the space available to the Windows install.

If you are not using the data, you can also just turn off logging by
unchecking the box in the site properties.

"Bill Glidden" <bill(a)glidden.net.au> wrote in message
news:O4iqNUmZKHA.1592(a)TK2MSFTNGP06.phx.gbl...
>I have been wondering why my system volume of my SBS 2008 keeps running out
>of disk space. I now see that c:\inetpub\LogFiles\W3SVC1372222313\ contains
>a bajillion u_ex*.log files, totalling 67.1GB. Is this something I�m
>supposed to be managing or is something wrong? They range in date from
>mid-August to today. The files are frequently over 1GB in size. The server
>has been commissioned since August.


From: Bill Glidden on 16 Nov 2009 18:44
..._.. wrote:
> Yes, you should be managing them. Depending on what information you are
> getting (probably not much, if you didn't know they were that large) you can
> zip them up and delete the originals, make reports and then delete the
> originals, or just delete them.
>
> I would STRONGLY ADVISE moving them to a separate partition so they do not
> fill up the space available to the Windows install.
>
> If you are not using the data, you can also just turn off logging by
> unchecking the box in the site properties.
>
> "Bill Glidden" <bill(a)glidden.net.au> wrote in message
> news:O4iqNUmZKHA.1592(a)TK2MSFTNGP06.phx.gbl...
>> I have been wondering why my system volume of my SBS 2008 keeps running out
>> of disk space. I now see that c:\inetpub\LogFiles\W3SVC1372222313\ contains
>> a bajillion u_ex*.log files, totalling 67.1GB. Is this something I�m
>> supposed to be managing or is something wrong? They range in date from
>> mid-August to today. The files are frequently over 1GB in size. The server
>> has been commissioned since August.
>
>
Thanks "-" and Steve.
Should I not be worried about the size of these files? Do they not
indicate a possible problem? I am happy to turn off logging, since I do
not use these files. Are they ever useful for diagnostic purposes? If
so, I can always re-enable logging for a period.
Cheers, Bill
From: .._.. on 17 Nov 2009 13:51
The size will change depending on the traffic and how the web site is built.
A clean simple site without a lot of images will make a smaller log file
than one with 300 image objects and 4 JavaScript files per page. So it
really depends on how the site was built, and the traffic level you get.

If you want to look, turn off logging, rename the current log file, turn on
logging, then view the new log file before it gets too big to manage and see
what's in it. Only then can you tell if there is a problem or not.

"Bill Glidden" <bill(a)glidden.net.au> wrote in message
news:4B01E3FB.5040303(a)glidden.net.au...
> .._.. wrote:
>> Yes, you should be managing them. Depending on what information you are
>> getting (probably not much, if you didn't know they were that large) you
>> can zip them up and delete the originals, make reports and then delete
>> the originals, or just delete them.
>>
>> I would STRONGLY ADVISE moving them to a separate partition so they do
>> not fill up the space available to the Windows install.
>>
>> If you are not using the data, you can also just turn off logging by
>> unchecking the box in the site properties.
>>
>> "Bill Glidden" <bill(a)glidden.net.au> wrote in message
>> news:O4iqNUmZKHA.1592(a)TK2MSFTNGP06.phx.gbl...
>>> I have been wondering why my system volume of my SBS 2008 keeps running
>>> out of disk space. I now see that c:\inetpub\LogFiles\W3SVC1372222313\
>>> contains a bajillion u_ex*.log files, totalling 67.1GB. Is this
>>> something I�m supposed to be managing or is something wrong? They range
>>> in date from mid-August to today. The files are frequently over 1GB in
>>> size. The server has been commissioned since August.
>>
>>
> Thanks "-" and Steve.
> Should I not be worried about the size of these files? Do they not
> indicate a possible problem? I am happy to turn off logging, since I do
> not use these files. Are they ever useful for diagnostic purposes? If so,
> I can always re-enable logging for a period.
> Cheers, Bill


 |  Next  |  Last
Pages: 1 2 3
Prev: IIS 7 Catastrophic Failure :: COMException :: Microsoft.JScript
Next: Problem solved!!!