Hi All,
I wonder if anyone has seen errors like these before...
Scenario is as follows, two Zope instances and a zeo server all running
from the debian zope2.9 packages. All the control scripts for these
instances fail with the following error when used:
Traceback (most recent call last):
You probably have two different versions of Python installed. And
probably this is a 64-bit system at least in parts.
Check the python path cron uses and compare to the path the instance
is run with.
HTH,
__Janko
Am 18.02.2009 um 11:37 schrieb Chris Withers:
Hi All,
I wonder if anyone
Chris Withers wrote:
ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so:
undefined symbol: PyUnicodeUCS4_AsEncodedString
ImportError: /opt/Zope-2.9/lib/python/persistent/cPersistence.so:
undefined symbol: PyUnicodeUCS2_AsEncodedString
Having had a bit of a google, I found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.02.2009 12:00 Uhr, Chris Withers wrote:
Chris Withers wrote:
ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so:
undefined symbol: PyUnicodeUCS4_AsEncodedString
ImportError:
On Wed, Feb 18, 2009 at 12:00 PM, Chris Withers ch...@simplistix.co.uk wrote:
Chris Withers wrote:
ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so:
undefined symbol: PyUnicodeUCS4_AsEncodedString
ImportError: /opt/Zope-2.9/lib/python/persistent/cPersistence.so:
undefined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Bizzarri wrote:
On Wed, Feb 18, 2009 at 12:00 PM, Chris Withers ch...@simplistix.co.uk
wrote:
Chris Withers wrote:
ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so:
undefined symbol: PyUnicodeUCS4_AsEncodedString
