[mod_python] Wierd pyPGSQL stuff with mod_python 3.1.2b

Keith Randall randallk at cpsc.ucalgary.ca
Mon Nov 24 16:53:31 EST 2003


Yep, new apache was running as different user, without linker path with libpq.  ;P
Thanks a lot.
Keith



On Mon, 24 Nov 2003, Julian Ciccale wrote:

> Have you checked apache's error_log? May be some "C" python module isn't loading in apache by some reason (probably LD_LIBRARY_PATH) or something.
> 
> - julcicc -
>  
> On Monday, November 24, 2003, at 05:37PM, Keith Randall <randallk at cpsc.ucalgary.ca> wrote:
> 
> >
> >
> >
> >On Mon, 24 Nov 2003, Julian Ciccale wrote:
> >
> >> Which python version are you using?
> >> 
> >> Are you sure the python interpreter that you use from the command line and the one that gets called wihthin httpd are the same?
> >> 
> >> Check it with
> >> import sys
> >> print sys.version
> >> 
> >
> >Yep, they're the same:
> >
> >apache:
> >[Mon Nov 24 09:05:06 2003] [notice] Apache/2.0.48 (Unix) mod_python/3.1.2b Python/2.3.2 configured
> >
> >vs.
> >python -v
> >
> >Python 2.3.2 (#2, Nov 12 2003, 23:39:57)
> >[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
> >
> >(and there's only one 2.3.2 installed ).
> >
> >sys.path is identical for both as well ( except for the script's own directory, which is
> >chrooted to htdocs by apache as expected.)
> >
> >Also the path to pyPgSQL is readable by all, everything was built from source, no rpms.
> >
> >python 2.3.2
> >pyPgSQL 2.4
> >mod_python 3.1.2b
> >apache 2.0.48
> >postgresql 7.4
> >



More information about the Mod_python mailing list