To follow up, I have zenoss working now on Suse 10.2 64bit. Thanks for your help - installing Python 2.3.6 was the solution. The problem was a symlink existed at /usr/local/zenoss/current/bin/python that was referencing my old Python 2.5 interpreter.
I was able to turn up this snippet from some python source code (modsupport.h) that tipped me off to the problem: ---------- /* On a 64-bit system, rename the Py_InitModule4 so that 2.4 modules cannot get loaded into a 2.5 interpreter */ ---------- Once I pointed that symlink to the 2.3.6 interpreter all is well. Thanks again, ------------------------ Joe Uhl -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=5532#5532 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [EMAIL PROTECTED] http://lists.zenoss.org/mailman/listinfo/zenoss-users
