[Setup] Forcing migrations to work around crashes of Python

Graham Perrin G.J.Perrin at bton.ac.uk
Fri Feb 19 08:57:31 UTC 2010


Following move of FileStorage and BLOBs 
from Plone 3.3.4 ZEO cluster on Mac OS X Server 10.5.8, PowerPC
to   Plone 3.3.4 ZEO cluster on Mac OS X Server 10.6.2, 64-bit kernel 
with client1 or client2 running in fg (foreground): 

 * attempting to load the home page of some sites, not all, 
   causes the client to stop unexpectedly; Python crashes. 

Crashes also occur when ZEO clients are run normally.

Attempted workarounds: 

 * force migration from 3.0 to 3.3.4 — no improvement
 * force migration from 2.5.5 to 3.3.4 — success, touch wood. 

The weird thing is, none of these sites have a Plone 2.x origin. It's
possible that some have a 3.0 alpha or beta origin, but those sites are not
the ones that are associated with crashes. 

Any ideas? 

Crash logs to follow. In the meantime, I attach ZMI views of forced
migrations of two sites that are associated with crashes.

http://n2.nabble.com/file/n4596726/migration-forced-freemancentre-3.0.txt
migration-forced-freemancentre-3.0.txt 
http://n2.nabble.com/file/n4596726/migration-forced-freemancentre-2.5.5.txt
migration-forced-freemancentre-2.5.5.txt 

http://n2.nabble.com/file/n4596726/migration-forced-globinn-3.0.txt
migration-forced-globinn-3.0.txt 
http://n2.nabble.com/file/n4596726/migration-forced-globinn-2.5.5.txt
migration-forced-globinn-2.5.5.txt 
-- 
View this message in context: http://n2.nabble.com/Forcing-migrations-to-work-around-crashes-of-Python-tp4596726p4596726.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.



More information about the Setup mailing list