On 07/11/2012 09:32 PM, Efraín Déctor wrote:
> Hello. This is what returns the 2 servers:
>
> Production Server:
> ['/usr/local/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg',
> '/usr/local/lib/python27.zip', '/usr/local/lib/python2.7',
> '/usr/local/lib/python2.7/plat-freebsd8',
> '/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old',
> '/usr/local/lib/python2.7/lib-dynload',
> '/usr/local/lib/python2.7/site-packages']
>
> Test Server:
> ['/usr/local/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg',
> '/usr/local/lib/python27.zip', '/usr/local/lib/python2.7',
> '/usr/local/lib/python2.7/plat-freebsd9',
> '/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old',
> '/usr/local/lib/python2.7/lib-dynload',
> '/usr/local/lib/python2.7/site-packages']
>
> Craig: Sorry about the details.
>
> This is what we got:
>
> Production server:
> FreeBSD 8.2
> Postgresql 9.1.2
> Python 2.7.3 (default, Jul 10 2012, 21:36:33)
Interesting that your production server has the oldest FreeBSD and the
newest Python. I'm still suspecting a library mismatch of some kind.
Is there anything vaguely informative in PostgreSQL's log files after
the error? I'm hoping for a message from Python about a dlopen() or
dlsym() error, or for a message from the dynamic linker.
If you redirect the postmaster's stderr to a file, it's possible dynamic
linker messages might appear there but not be captured by Pg for
logging. I don't see how you'd redirect that without stopping and
starting the server, which you don't want to do.
--
Craig Ringer
