On nearly every SharePoint farm I’ve installed on Windows Server 2008, the C: drive begins filling up almost immediately with 1 and 2 GB log files. These logs are located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS
|
Timestamp Process TID Area Category EventID Level Message Correlation 01/06/2010 16:50:59.99 OWSTIMER.EXE (0×0740) 0×0750 Windows SharePoint Services Timer 5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{D8B06985-2B9C-4788-A7A5-9A9762150310}’ for service ‘{44A9C325-0E7D-41F2-B75E-5F29B48B280F}’ is still running, so the current instance will be skipped. Consider increasing the interval between jobs. |
After looking at several potential fixes such as clearing the SharePoint Configuration Cache detailed in Joe Rodger’s blog, I finally had to resort to using following KB Article 941789
Essentially, this article says to:
1. Go into SharePoint 3.0 Central Administration, Operations, Diagnostic Logging and in the “Category” drop down, select “Timer”
2. Change “Least critical event to report to the event log” to “Error”
3. Change “Least critical event to report to the trace log” to “medium”.
In my opinion, this is not a cure but a Band-Aid. Microsoft, we need fixes, not workarounds.
In addition, I change the logging location to the E; drive (where SharePoint binaries are installed anyway). Since the logging location must be available on all farm servers, I simply specify “E:\Program Files\Microsoft Office Servers\12.0\Logs”. This change is almost immediate across the farm and in the event the logs again fill up the drive, at least your not filling the system drive an crashing the system.
I’m still playing around with the how many logs to maintain, it sure would be nice to specify log rollover based on size as a 1.5GB log file can be difficult to read with native tools (Notepad, wordpad, etc. However, I’m thinking I only really need about 24 hours worth in the test environment, perhaps another day or two in production.
출처 : http://www.quantumofgeek.com/2010/01/owstimer-exe-errors-in-sharepoint-2007-logs/