On Oct 31, 6:24 pm, lidiriel <[EMAIL PROTECTED]> wrote:
> Tanks for your response.
> I have do a real "restart" of myslq and apache before several test.
> I have the same problem.
> With the version Mysql5.0.51a it is the same thing.
> Perhaps that modpython has a problem ?
> I don't uderstand this and I don' t upgrade mysql on this sever
> (redhat server with no more recent package).
> Someone has any new idea ?
Are you also loading PHP into Apache. PHP preloads modules and so if
has MySQL support it may be loading a different MySQL client library,
specifically a non reentrant, non threaded one.
As described in:
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#MySQL_Shared_Library_Conflicts
what do you get when you run ldd on PHP modules, Apache modules and
Python modules that use MySQL.
An Apache restart also may not be enough, do a full 'stop' of Apache
and then a 'start'. This will ensure that shared libraries aren't
being cached across a Apache restart, as for an Apache restart, the
Apache parent process isn't actually shutdown and it it can't unload
modules/libraries properly, it may retain linkage to wrong library if
version used by something has changed.
Graham
> On 28 oct, 16:28, Christian Boos <[EMAIL PROTECTED]> wrote:
>
> > lidiriel wrote:
> > > ...
> > > I reload apache server and mysql and the "about" page of trac is :
>
> > 'restart' would be better than 'reload' in this case, as a C module for
> > Python is involved (_mysql.pyd).> ...
> > > ARRRG thread safe = 0.. ??
> > > ok i check directly in consol mode in the server :
> > > In [4]: import MySQLdb
> > > In [5]: MySQLdb.thread_safe()
> > > Out[5]: 1
>
> > > I don't understand in console mode the thread_safe() return 1 and in
> > > the about page thread_safe is Someone has already had this problem ?
>
> > Besides the possible 'restart' vs. 'reload' issue, it's also possible
> > that you're not using the same Python installation (and therefore not
> > the same version of MySQLdb) at the command line and in Apache.
>
> > Note also that this ticket mentions a possible bug in MySQL 5.0.45 which
> > happens to be the version you're using. So you may want to upgrade that
> > package as well (seehttp://trac.edgewall.org/ticket/3645#comment:44).
>
> > -- Christian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
