Question

我正在使用微软的WSSv3演示虚拟PC演示，VHD正在失控。

Using Folder Size I was able to trace it down to the WSS log files.
Today I have two log files that grew to excessive size.

1） 30分钟内达到2.5GB，然后

2） 2小时内2.1GB

I m trying to review the content with LTFViewer, but the files may be to large as the viewer freezes up The surrounding log files have the following content that repeats every 5 minutes

OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch.  
OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch.  
OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch. 
w3wp.exe (0x0C44)        General   Entering MRU trim routine.    
w3wp.exe (0x0C44)        General   Initial table size: 41125202 in 222 entries   
w3wp.exe (0x0C44)        General   Final table size: 41125202 in 222 entries     
w3wp.exe (0x0C44)        General   Exiting MRU trim routine.     
w3wp.exe (0x071C)        General   Entering MRU trim routine.    
w3wp.exe (0x071C)        General   Initial table size: 19857672 in 90 entries    
w3wp.exe (0x071C)        General   Final table size: 19857672 in 90 entries  
w3wp.exe (0x071C)        General   Exiting MRU trim routine.     
OWSTIMER.EXE (0x06C0)    General   Entering MRU trim routine.    
OWSTIMER.EXE (0x06C0)    General   Initial table size: 0 in 0 entries    
OWSTIMER.EXE (0x06C0)    General   Final table size: 0 in 0 entries  
OWSTIMER.EXE (0x06C0)    General   Exiting MRU trim routine.     
OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch.  
OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch.  
OWSTIMER.EXE (0x06C0)    E-Mail    The Incoming E-Mail service has completed a batch.

同样，这是今天刚开始的，我的主机上的硬盘空间快用完了。

谢谢

Answer 1

想通了

下面的行每毫秒被记录x30次。

Timestamp
04/03/2009 09:48:47.86 

Process
OWSTIMER.EXE (0x0DE8)

TID
0x06D0

Area
Windows SharePoint Services

Category
Timer

EventID
5uuf

Level
Monitorable

Message
The previous instance of the timer job  Config Refresh , id
 {975F79C9-1B0D-4D14-BD60-C531FF142500}  for service
 {6C881CF7-F11F-457B-A757-68862E0059E6}  is still running, so the
current instance will be skipped. Consider increasing the interval
between jobs.

这篇博客文章描述了如何修复

http://blogs.vertigo.com/personal/steventap/Blog/archive/2007/01/19/managing-sharepoint-2007-moss-application-log-size.aspx

谢谢大卫，

To summarize blog post, change your diagnostic logging levels. If developing in a local Virtual Machine, also suggest to write those logs to a shared folder outside of the VHD

中央管理局>；操作>；日志记录和报告>；诊断日志记录

Answer 2

可以通过对象模型（SPDiagnosticsService）对日志文件设置限制，但不能通过STSADM命令行工具设置限制-直到现在：

http://stsadm.blogspot.com/2008/06/trace-log-settings.html

这是STSADM的一个外接程序，可以将日志移动到不同的驱动器，限制日志文件数和日志时间。

-奥辛

Answer 3

我在日志中看到了同样的事情，但Steve建议的修复方法没有奏效。

所做的工作是确保时钟设置在正确的时间。时钟在过去设定为20分钟。一旦我更新了服务器上的时间以使其正确，错误就停止了。

友情链接