[Zope-DB] Zope 2.7.0 and MySQL: What Am I Missing?

Kent Hoxsey khoxsey at earthlink.net
Wed Jun 9 13:29:16 EDT 2004

> I had a DA already in there, so I didn't really get that
> far.  I've removed the two connectors I had and started it again -- and
> Zope stopped working immediately.

That's probably important, in that it indicates a setup problem rather
than a bug.

> So I tried that.  And I got 
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> ImportError: ld.so.1: python: fatal: libmysqlclient.so.14: open failed: No such file or directory

> Which hey, makes sense because my MySQL libraries were in a non-standard
> location.  So, having fixed that (thanks to the magic of crle), I could now
> do 'import _mysql' with impunity.

That was going to be my next question.  Which brings us back to the problem at hand:

> Which, unfortunately, does not fix my problem.

I'm not yet convinced that your setup is complete. Do you run zope with the Medusa
server answering on port 80?  I have had problems where the environment set up

   sudo -u zope /blah/blah/zope/bin/runzope

was not the same as the environment for:

   su - zope

In my case, appropriate setting of LD_LIBRARY_PATH made all the difference.

> Are there any success stories with 2.7.0, MySQL-python, and ZMySQLDA? Just
> knowing what versions people used will at least let me know that I'm on the
> right path.

I do have Zope 2.7.0, MySQL-python 0.9.2 (I think), and ZMySQLDA of the same
vintage. I had minor issues with DateTimes during a recent project, most likely
due to the above-mentioned library problems.

However, we use mxODBC for all our production database access, so rather than
trying to fix my setup issues, I integrated the MySQL ODBC connector into my
setup, and haven't looked back.


More information about the Zope-DB mailing list