Slony-I 服务填满了我在 Windows 中的事件查看器
我以前写过类似的问题，但没有得到答案，所以我想以更简单的方式再问一次。
我有 slony-I 在 Windows 环境中复制数据库（Master 有 Windows XP，Slave 有 Windows 7，两者都带有 postgreSQL 8.2）。我在主服务器和从服务器中使用 slon -regservice 注册了一个服务，一切正常。
我遇到的问题是该服务每次运行时都会在事件查看器中写入日志，因此每秒有 5 或 6 个新日志。我希望它只会在事件查看器中写入错误，但它一直在写入日志，并且我的主服务器中的事件查看器充满了错误。由于Windows XP在事件查看器中存在空间限制，因此日志使事件查看器达到其限制，并且所有使用事件查看器的应用程序崩溃。
有没有办法配置 slony 服务以避免在事件查看器中写入日志？
任何帮助将不胜感激。我已经为这个问题苦苦挣扎了两周，我阅读了网络上的每个教程，它们都有相同的说明，但没有一个提到事件查看器中的日志。我错过了什么吗？
谢谢！
I wrote a similar question before but I got no answers so I was thinking on asking again in a simpler way.
I have slony-I replicating databases in a windows environment (Master has windows xp and slave has windows 7, both with postgreSQL 8.2). I registered a service using slon -regservice in both master and slave and everything works fine.
The problem I have is that the service is writing logs in the event viewer every time it runs so I have 5 or 6 new logs every second. I was hoping that it would write only errors in the event viewer but it writes logs all the time and the event viewer in my master server is getting filled with them. Since windows xp has a limit of space in the event viewer, the logs make the event viewer reach its limit and all the applications that use the event viewer crash.
Is there a way to configure the slony service to avoid writing logs in the event viewer?
Any help will be greatly appreciated. I've been struggling with this problem for 2 weeks now and I read every tutorial in the web and all of them have the same instructions but none of them mentions the logs in the event viewer. Am I missing something?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可能应该在 Slony-I 错误数据库中提出错误，或者向他们的邮件列表发送电子邮件。由于它是开源的，您甚至可以重新构建它并删除不需要的事件日志记录。此外，您不需要注册即可接收事件日志，但您可能需要错误。
您似乎使用的是Windows XP，它现在已经很陈旧了——它已经有10年历史了！现代版本的 Windows 具有更具弹性的事件日志。
最后，您可以重新配置事件日志设置来尝试避免该问题。您可以将日志设置得更大（默认值 512KB 相当小），并且似乎还有其他可用设置。打开事件查看器，右键单击事件日志之一并选择属性。
You probably ought to raise a bug in the Slony-I bug database or e-mail their mailing list. Since it is open source you could even re-build it and remove the unwanted event logging. Also, you don't need to register to receive event logs but you probably want errors.
You appear to be using Windows XP which is rather decrepit now – it's 10 years old! The modern versions of Windows have much more resilient event logs.
Finally, you could reconfigure the event log settings to try to avoid the problem. You could make the log much bigger (512KB default is quite small) and there appear to be other settings available. Open the event viewer, right click one of the event logs and select properties.