“由sys.excepthook中的Error启动的线程中未处理的异常"在存储zodb pack期间 [英] "Unhandled exception in thread started by Error in sys.excepthook" during relstorage zodb pack

查看:133
本文介绍了“由sys.excepthook中的Error启动的线程中未处理的异常"在存储zodb pack期间的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个相当大的Plone实例在其自己的挂载点上运行. ZMI界面列出的数据库大小为7101.4M.我们使用Relstorage zodbpack.py脚本每周运行一次数据库包,删除7天以上的对象.最近两周,运行该程序包的cron作业已输出以下内容:

We have a reasonably large Plone instance running on its own mount point. The ZMI interface lists the size of the database as 7101.4M. We run a weekly pack of the database using the Relstorage zodbpack.py script, removing objects older than 7 days. The last two weeks the cron job that runs the pack has output the following:

Sun Jun 26 07:00:38 BST 2011 packing cms mount
/home/zope/home/parts/zope2/lib/python/zope/configuration/xmlconfig.py:323: DeprecationWarning: zope.app.annotation has moved to zope.annotation. Import of zope.app.annotation will become unsupported in Zope 3.5
__import__(arguments[0])
/home/zope/home/eggs/p4a.common-1.0.7-py2.4.egg/p4a/common/configure.zcml:19: DeprecationWarning: The five:localsite directive is deprecated and will be removed in Zope 2.12.
See Five/doc/localsite.txt .
 <five:localsite class=".Portal.PloneSite" />
/home/zope/home/parts/zope2/lib/python/zope/configuration/fields.py:417: UserWarning: You did not specify an i18n translation domain for the 'description' field in /home/zope/home/eggs/Products.CMFSquidTool-1.5.1-py2.4.egg/Products/CMFSquidTool/configure.zcml
 warnings.warn(
/home/zope/home/parts/zope2/lib/python/zope/configuration/fields.py:417: UserWarning: You did not specify an i18n translation domain for the 'title' field in /home/zope/home/eggs/Products.CMFSquidTool-1.5.1-py2.4.egg/Products/CMFSquidTool/configure.zcml
 warnings.warn(
Unhandled exception in thread started by
Error in sys.excepthook:

Original exception was:
Sun Jun 26 09:56:31 BST 2011 finished pack

第一行和最后一行是由cron作业运行的shell脚本输出的.

The first and last lines are output by the shell script the cron job runs.

打包后,数据库大小减小,因此它似乎正在做某事.对于如何进一步调试此错误,我有些茫然.

The database size decreases after the pack so it appears it is doing something. I'm at a bit of a loss as to how to debug this error further.

长期以来,程序包运行正常.然后,我们更改了数据库的连接参数,但忘记了在cron作业上更新它们,因此该包没有运行11周.在此错误出现之前,它成功运行了两次-长时间不运行包装是否与该错误有关?

For a long period the pack was running OK. We then changed the connection parameters for the database but forgot to update them on the cron job and so the pack wasn't run for 11 weeks. It ran successfully twice before this error appeared - could the long period of no packs being run have something to do with the error?

任何帮助将不胜感激.

我们正在运行:

  • 克隆3.3.5
  • Zope 2.10.11
  • Relstorage 1.4.1
  • ZODB 3.8.4轮询

推荐答案

该错误与Python有关,而不与RelStorage有关.请参阅 http://bugs.python.org/issue1722344 以获取我认为与此处有关的bug报告.该错误适用于Python 2.5和2.6,但也可能适用于Python 2.4.如果尚未升级,请尝试将Python 2.4升级到最新版本.

The error is related to Python, not RelStorage. See http://bugs.python.org/issue1722344 for the bugreport I think is relevant here. That bug applies to Python 2.5 and 2.6, but may also be applicable to Python 2.4. Try upgrading Python 2.4 to the latest if it is not already.

在任何情况下,此消息均无害.打包仅使用一个线程,您会在最后得到成功消息(Sun Jun 26 09:56:31 BST 2011 finished pack仅在打包成功时才会显示).

In any case, the message is harmless in this case. Packing only uses one thread, and you do get the success message at the end (Sun Jun 26 09:56:31 BST 2011 finished pack will only be displayed if the pack was successful).

您还可以尝试升级到RelStorage 1.5.0(上周发布);包装得到了显着改善,可以处理较大规模的数据库和繁忙的站点.

You could also try upgrading to RelStorage 1.5.0 (it came out last week); packing was significantly improved to handle larger scale databases and busy sites.

这篇关于“由sys.excepthook中的Error启动的线程中未处理的异常"在存储zodb pack期间的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆