locked
Large log files on C:\ but TraceLogs on D:\? RRS feed

  • Question

  • A long time ago I moved the TraceLogs to the "D:\SharePointTraceLogs\" drive to avoid logs filling the "C:\ drive.

    Today I noticed "C:\Program Files\Common Files\Microsoft Shared\Web Extensions\12\Logs\" is growing fast with logs.

    eg SPServerName-20120301-xxxx.log files.

    The oldest date in this format is Feb 28, 2012 and most logs are about 2-4MB. On the 29th 2 files were 5+GB, then the next logs are about 15MB.

    This morning Mar 1, 2012 after getting a Space Warning!, I noticed these logs growing constantly. Only after rebooting and then finally stopping the services did the logging stop, with several 650+MB and 3.8GB logs.

    When the logs are going fast the enteries that seem to be repeating are"

    02/29/2012 19:19:14.43    OWSTIMER.EXE (0x0858)    0x0868    Windows SharePoint Services    Timer    5uuf    Monitorable    The previous instance of the timer job 'Config Refresh', id '{739F1A44-790B-4643-8613-EDC9B7A257D2}' for service '{315EED55-3E77-44F1-8340-FBCCD5DBD074}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.    
    02/29/2012 19:19:14.43    OWSTIMER.EXE (0x0858)    0x0868    Windows SharePoint Services    Timer    5uuf    Monitorable    The previous instance of the timer job 'Config Refresh', id '{739F1A44-790B-4643-8613-EDC9B7A257D2}' for service '{315EED55-3E77-44F1-8340-FBCCD5DBD074}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.    
    02/29/2012 19:19:14.43    OWSTIMER.EXE (0x0858)    0x0868    Windows SharePoint Services    Timer    5uuf    Monitorable    The previous instance of the timer job 'Config Refresh', id '{739F1A44-790B-4643-8613-EDC9B7A257D2}' for service '{315EED55-3E77-44F1-8340-FBCCD5DBD074}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.

    For now it seems to have settled down, but every so often the logs have a growth spurt.

    1. Can someone tell me what setting is causing logging here?
    2. I am assuming these are just reporting logs that I can manually remove, specifically the ones from previous days where they are 5GB?

    Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.


    • Edited by Stunpals Thursday, March 1, 2012 5:36 PM
    Thursday, March 1, 2012 5:35 PM

Answers

  • After following these KB article the issue seems to have Stopped.

    http://support.microsoft.com/kb/941789

    Not sure how this occured but nothing surprises me with MS products. The settings are clearly set to put logs in the defined area but they reverted back to the default location, while the settings were still pointing to the custom location.

    The second issue was the massive repeating errors that were the cause of the rapid growth, also magically fixed by following the above KB. The strange thing this article was posted in 2007, not sure how this same issue is still around.


    Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

    Thursday, March 1, 2012 6:30 PM

All replies

  • These are the diagnostic logs (WSS, MOSS), also known as the "ULS Logs" (ULS stands for Unified Logging Service). They are the logs SharePoint generates when it encounters certain conditions or errors. It sounds like you have the threshold set very low and they are filling up fast.

    You have two options: reduce the threshold, or move the logs. In the two links I have provided above are instructions and details for both. The settings are available in Central Administration -> Operations -> Diagnostic Logging.

    I also wanted to mention the free ULS Viewer tool Microsoft has made available that simplifies reading the ULS logs. It can also read them in real-time as events happen to aid with troubleshooting. 


    Jason Warren
    Infrastructure Specialist
    Habañero Consulting Group
    www.habaneros.com/blog

    Thursday, March 1, 2012 5:46 PM
  • Thanks Jason for the quick response.

    This is something strange, I"m thinking due to the recent Windows Updates? or a change they made as this wasn't not a problem until after the were ran.

    I have checked the Diag Logging and here are the settings

    Error Reports - Collect error reports (no checkboxes selected)
    Even Throttling - Not definded
    Trace Log - Path "D:\SharePointTraceLogs", 96, 30
    Unless I am wrong, all trace logs should be going to the D:\ drive.

    If I turn after rebooting the server the logs on the C:\ drive are growing at about 100MB every few seconds. It seems when I stop the Timer service the log growth slows. If I restart the service the logging remains normal. When I reboot it starts growing out of control.

    I have tried another suggestion "http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/82e3b319-05b2-46a5-ac77-6cd4ed2ce27c/", with no change.

    I'll read your links as well, but I think they are refering the the Diag Logs which are on the D:\ drive. I also have been using the ULS Viewer tool.

    Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

    Thursday, March 1, 2012 6:05 PM
  • After following these KB article the issue seems to have Stopped.

    http://support.microsoft.com/kb/941789

    Not sure how this occured but nothing surprises me with MS products. The settings are clearly set to put logs in the defined area but they reverted back to the default location, while the settings were still pointing to the custom location.

    The second issue was the massive repeating errors that were the cause of the rapid growth, also magically fixed by following the above KB. The strange thing this article was posted in 2007, not sure how this same issue is still around.


    Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

    Thursday, March 1, 2012 6:30 PM