Hi Emmanuel, Thanks for your assistance. I do in fact have more than one Python installed; but the stack trace indicates that the correct one is being used.
Your email gave me an idea, though, which turned out to be correct -- I was able to correct the problem by adding "PassEnv LD_LIBRARY_PATH" to the Apache <location> directive. Evidently the CGI wasn't able to find a shared library. Trac is now working just fine! Cheers, bn On Fri, 2006-02-17 at 20:30 +0100, Emmanuel Blot wrote: > Check that you do not have two releases of Python installed. > For example, tracd would use Python libraries from /opt/trac/... > whereas the trac.cgi would use another path (such as /usr/lib/python > ...) > > > On 2/17/06, Brett Neumeier <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm trying to get trac 0.9.4 working as a CGI through Apache. > > > > I've gotten it all working fine through the standalone tracd, so I am > > quite certain that my environment really does have a working pysqlite > > (2.1.3). > > > > When I access trac.cgi as a CGI, I get "Oops... Trac detected an > > internal error:" followed by the stack trace below. Any ideas? _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
