WSS 日志文件增长失控

发布于 2024-07-17 07:24:34 字数 1872 浏览 6 评论 0原文

我正在使用 Microsoft 的 WSSv3 演示 Virtual PC demo，VHD 正在变得失控。

使用文件夹大小，我能够追踪到 WSS 日志文件。
今天我有两个日志文件变得过大。

1) 30 分钟内 2.5GB，然后

2) 2 小时内 2.1GB

我尝试使用 LTFViewer，但文件可能会太大，因为查看器会冻结周围的日志文件具有以下内容，每 5 分钟重复

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.

一次。同样，这只是今天开始的，我的主机上的硬盘空间不足。

谢谢

原文

I'm using Microsoft's WSSv3 demo Virtual PC demo and the VHD is growing out of control.

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) 2.5GB within 30 minutes and then

2) 2.1GB within 2 hours

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.

Again, this just started today and I'm running out of hard drive space on my Host.

Thanks

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

鸠书 2024-07-24 07:24:34

发现

以下行每毫秒被记录 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

谢谢 David，

为了总结博客文章，请更改您的诊断日志记录级别。
如果在本地虚拟机中进行开发，还建议将这些日志写入 VHD

中央管理之外的共享文件夹 > 操作> 记录和报告> 诊断记录

Figured it out

the following line was being logged x30 times a millisecond.

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.

This blog post describes how to fix

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

Thanks David,

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

Central Administration > Operations > Logging and Reporting > Diagnostic Logging

回复收藏 0 原文