On Tue, Jan 06, 2004 at 11:02:07AM +0100, Bruno Mattarollo wrote:
Hello,
We are running a Zope 2.5.1 (yes, I know, old) version on one of our servers and yesterday we started getting these errors (quite a lot of them) on the error log:
2004-01-05T11:06:05 ERROR(200) ZODB Couldn't load state for '\x00\x00\x00\x00\x00y0s' Traceback (innermost last): File /var/Zope/Zope-2.5.1-src/lib/python/ZODB/Connection.py, line 447, in setstate File /var/Zope/Zope-2.5.1-src/lib/python/ZODB/FileStorage.py, line 582, in load (Object: /var/Zope/instances/cc251/var/Data.fs) File /var/Zope/Zope-2.5.1-src/lib/python/ZODB/FileStorage.py, line 557, in _load (Object: /var/Zope/instances/cc251/var/Data.fs) POSKeyError: 0000000000793073
And then this:
2004-01-06T06:05:06 PROBLEM(100) ZODB FS FS21 warn: /var/Zope/instances/cc251/var/Data.fs truncated, possib ly due to damaged records at 2137747449
------ 2004-01-06T06:05:06 PROBLEM(100) ZODB FS FS21 warn: Writing truncated data from /var/Zope/instances/cc251/v ar/Data.fs to /var/Zope/instances/cc251/var/Data.fs.tr0
You have some damage in your ZODB. You should run fsrecover.py on a *copy* of this database and see if you can fix these errors. Alternatively, restore a backup of the database. Note that some versions of fsrecover.py were broken. Check the archives, I don't remember if 2.5.1 was OK. I remember that 2.6.2 is OK, 2.6.0 was not. After recovery, try checking the output with utilities/ZODBTools/fstest.py. I don't know what causes "Writing truncated data", you might ask on the zodb-dev list.
So this morning we tried a "restart" and it didn't work, some python process was refusing to die, even with "kill -9" :( So we restarted the server and this is what we get now in the error log:
2004-01-06T09:40:51 PROBLEM(100) Init Ambiguous name for method of Products.PlugIns.PlugIns.PlugInGroup: "ma nage_workspace" != "manage_main" ------ 2004-01-06T09:40:51 PROBLEM(100) Init Ambiguous name for method of Products.LoginManager.LoginMethods.BasicC ookieLogin: "manage_propertiesForm" != "manage_main" ------ 2004-01-06T09:40:52 PROBLEM(100) Init Ambiguous name for method of Products.PythonMethod.PythonMethod.Python Method: "manage" != "manage_main" ------ 2004-01-06T09:40:52 PROBLEM(100) Init Ambiguous name for method of Products.SiteAccess.SiteRoot.SiteRoot: "m anage" != "manage_main" ------ 2004-01-06T09:40:52 PROBLEM(100) OFS.Application Duplicate Product name After loading Product 'SiteAccess' from '/var/Zope/instances/cc251/Products', I skipped the one in '/var/Zope/Zope-2.5.1-src/lib/python/Products'. ------ 2004-01-06T09:42:21 INFO(0) ZODB Opening database for mounting: '158998424_1044618368.927185' ------ 2004-01-06T09:42:21 INFO(0) ZODB Mounted database '158998424_1044618368.927185' at /temp_folder ------ 2004-01-06T09:42:22 PROBLEM(100) Zope No such file or directory: /var/Zope/instances/cc251/Products/PlugIns/ help ------ 2004-01-06T09:42:23 INFO(0) Zope New disk product detected, determining if we need to fix up any ZClasses. ------ 2004-01-06T09:42:23 INFO(0) ZServer HTTP server started at Tue Jan 6 10:42:23 2004 Hostname: activism.greenpeace.org Port: 8085
The last message looks like you're up... none of the above issues should prevent startup.
------ 2004-01-06T09:46:11 PROBLEM(100) ZODB Could not import class 'Connection' from module 'Products.ZPoPyDA.DA'
That's a 3rd-party product... looks like it's broken? Did it work before? Anyway, this should not prevent zope from starting. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's SEMI LUGGAGE CAPTAIN! (random hero from isometric.spaceninja.com)