| | 119 | === 'Server Error' Page Displayed === |
| | 120 | |
| | 121 | Assuming you are confident that mod_python is installed and working properly (An example of a simple test setup can be found here: [http://www.dscpl.com.au/articles/modpython-001.html]), if you get the following error in your browser: |
| | 122 | |
| | 123 | '''''The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a CGI script.''''' |
| | 124 | |
| | 125 | And you get the following entries in your Apache error log: |
| | 126 | |
| | 127 | |
| | 128 | {{{ |
| | 129 | ...File "/usr/lib64/python2.3/site-packages/mod_python/apache.py", line 287, in HandlerDispatch\n log=debug) |
| | 130 | ...PythonHandler trac.web.modpython_frontend: File "/usr/lib64/python2.3/site-packages/mod_python/apache.py", line 454, in import_module\n f, p, d = imp.find_module(parts[i], path) |
| | 131 | |
| | 132 | ... PythonHandler trac.web.modpython_frontend: ImportError: No module named trac |
| | 133 | }}} |
| | 134 | |
| | 135 | Make sure the 'trac' directory that was created during installation has the appropriate permissions in order for the user your web server runs under to 'see' the files contained in it. This directory will be in the 'site-packages' directory of your platform's installation. A 'chmod -R 755 ./trac' resolved the issue for me. Modify as necessary for your security preferences |
| | 136 | |
| | 137 | |
| | 138 | |
