[mod_python] More ugly "make_obcallback returned no obCallBack!" errors.

Gregory (Grisha) Trubetskoy grisha at modpython.org
Sat Feb 16 13:14:47 EST 2002

This looks like a bug, I'll have to take a look at it later.

As dirty work-around, try forcing the interpreter name by putting

PythonIntepreter my_interpreter

in the config at the top level (i.e. outside virtual servers)

This will, of course, make the virtual servers run in the same
interpreter, but it might solve the immediate problem, as I supsect it is
something with subinterpreters...


On Sat, 16 Feb 2002, Dustin Mitchell wrote:

> These don't seem to have anything to do with bad paths.  Here's the situation:
> I have two name-based virtualhosts, each using mod_python.  They both use a
> number of handlers.  Here are the relevant directives in the httpd.conf for
> each vhost:
>   PythonAutoReload Off
>   PythonDebug on
>   PythonTransHandler handlers.translate::transhandler
>   PythonHeaderParserHandler handlers.headers::cookies
>   PythonHeaderParserHandler handlers.headers::formdata handlers.headers::login
>   PythonAuthenHandler handlers.auth::check
>   PythonLogHandler handlers.log::log
> I'm using Apache/1.3.22 (Unix) PHP/4.1.1 mod_python/2.7.6 Python/2.1
> mod_ssl/2.8.5 OpenSSL/0.9.6.
> So here's what happens:  Each Apache "server" (i.e., operating system
> process, as differentiated by PIDs) only seems to be able to serve one of the
> two virtualhosts -- the other virtualhost will present "Internal Server
> Error" with the logs listing errors importing modules for make_obcallback,
> and the infamous "make_obcallback returned no obCallBack!" error.
> >From the perspective of a single "server" (checked by setting
> MaxSpareServers, MinSpareServers, and StartServers to 1), it can load
> virtualhost A as many times as it would like.  Once a request comes in for
> virtualhost B, however, obCallBack problems occur.  It doesn't matter which
> virtualhost is loaded first -- it will be successful, and the second
> virtualhost will not.
> I've tried some tricks to see exactly what the Python exception is when
> mod_python can't load 'apache', but I'm not an extension-writer, and my
> feeble attempts produced only segfaults.
> WITH_THREAD is not set.
> Any ideas?
> Dustin
> --
>   Dustin Mitchell
>   dustin at ywlcs.org
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python

More information about the Mod_python mailing list