A shot in the dark because I haven't really messed with FreeBSD in years..
Is it possible you have python3 on the system and the version of mod_python is compiled for python3 while you are using python2.7 for Trac? Or vice versa, is it compiled for 2.7 and you only have python3 installed? Just because you are calling mod_python doesn't mean you installed the module.. have you installed it? Im guessing apache on FreeBSD has support for mod_wsgi, that may be a reasonable alternative to mod_python. This may be why the links you are seeing reference using that instead. From: "David Gessel" <[email protected]> To: "Trac Users" <[email protected]> Sent: Friday, March 24, 2017 2:30:02 PM Subject: [Trac] Problem with new install on FreeBSD I'm pretty confident this is a path issue, but I haven't had much luck in resolving it. I am getting "500 server error" and looking at my logs I see: [ Fri Mar 24 11 : 10 : 23.282925 2017 ] [: error ] [ pid 21554 : tid 34741511168 ] [ client xxx . 127.65 . 15 : 22736 ] python_handler : Can 't get/create interpreter. ImportError : No module named mod_python . apache [ Fri Mar 24 11 : 10 : 23.282850 2017 ] [: error ] [ pid 21554 : tid 34741511168 ] make_obcallback : Python path being used "['/usr/local/lib/python27.zip', '/usr/local/lib/python2.7', '/usr/local/lib/python2.7/plat-freebsd10', '/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old', '/usr/local/lib/python2.7/lib-dynload']" . [ Fri Mar 24 11 : 10 : 23.282888 2017 ] [: error ] [ pid 21554 : tid 34741511168 ] get_interpreter : no interpreter callback found . My vhost config looks like: <VirtualHost 10.3.69.139:80 > # registrar nic.st DocumentRoot /usr/local/www/trac ServerName trac.my.domain ErrorLog /var/log/trac-error_log CustomLog /var/log/trac-access_log combined <Location /> SetHandler mod_python PythonInterpreter main_interpreter PythonOption PYTHON_EGG_CACHE /usr/local/www/trac/tmp PythonPath "sys.path + ['/usr/local/www/trac']" PythonPath /usr/local/bin/mod_python PythonHandler trac.web.modpython_frontend PythonOption TracEnv /usr/local/www/trac PythonOption TracUriRoot / </Location> </VirtualHost> I am confident it's a trivial misconfiguration issue, but most answers I find by googling are along the lines of "why aren't you using WSGIScript There's an obvious crude attempt to add the path for mod_python explicitly in my vhost declaration, which didn't help. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] . To post to this group, send email to [email protected] . Visit this group at https://groups.google.com/group/trac-users . For more options, visit https://groups.google.com/d/optout . -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
