kamin at embedded
Oct 28, 2009, 3:38 AM
Post #5 of 6
(480 views)
Permalink
|
Hi again,
the test-setup using mod_python yesterday ran without problems. Today I reinstalled everything using Python 2.6 and WSGI instead of mod_python, but I don't seem to get it working.
The Browser states:
----
Internal Server Error
TracError: IOError: (22, "invalid mode ('r') or filename")
----
My guess is that my httpd.conf is bad, but I cannot locate the error (Apache doesn't log any errors [.apart from some PHP errors that are due to some other project, but didn't interfere with mod_python])
I added the following lines to the httpd.conf file:
----
LoadModule wsgi_module modules/mod_wsgi.so
WSGIScriptAlias /trac /trac/tas/cgi-bin/trac.wsgi
<Directory /trac/tas>
WSGIApplicationGroup %{GLOBAL}
Order deny,allow
Allow from all
</Directory>
----
For the directory entry I also tried "/trac" and "/trac/tas/cgi-bin"
The WSGI module is in the correct directory and seems to be loaded properly. To my understanding, http://server/trac should now display the Trac page, but only shows the error message (cf. above).
The Trac environment has been initialized and deployed. The automatically generated trac.wsgi file can be found at
C:\trac\tas\cgi-bin\trac.wsgi
I moved it there from C:\trac\temp\cgi-bin\trac.wsgi (cf. Trac deploy documentation).
The script seems to be ok, but I post it anyway because I might have overlooked something:
----
import os
def application(environ, start_request):
if not 'trac.env_path_parent_dir' in environ:
environ.setdefault('trac.env_path', 'C:\trac\tas')
if 'PYTHON_EGG_CACHE' in environ:
os.environ['PYTHON_EGG_CACHE'] = environ['PYTHON_EGG_CACHE']
elif 'trac.env_path' in environ:
os.environ['PYTHON_EGG_CACHE'] = os.path.join(environ['trac.env_path'],
'.egg-cache')
elif 'trac.env_path_parent_dir' in environ:
os.environ['PYTHON_EGG_CACHE'] = os.path.join(environ['trac.env_path_parent_dir'],
'.egg-cache')
from trac.web.main import dispatch_request
return dispatch_request(environ, start_request)
----
File access rights have been granted to C:\trac for SYSTEM, NETWORKSERVICE, and my user account
What did I do wrong?
Regards,
Volker
--
Dipl.-Inform. Volker Kamin
RWTH Aachen University
Embedded Software Laboratory
Ahornstr. 55
52074 Aachen
fon: +49 241 80 21157
fax: +49 241 80 22150
web: http://www.embedded.rwth-aachen.de/
-----Ursprüngliche Nachricht-----
Von: trac-users [at] googlegroups [mailto:trac-users [at] googlegroups] Im Auftrag von Remy Blank
Gesendet: Dienstag, 27. Oktober 2009 20:02
An: trac-users [at] googlegroups
Betreff: [Trac] Re: Which 0.12dev to use
Kamin, Volker wrote:
> Is there a revision of 0.12dev that you believe to be "more stable"
> than others?
trunk is usually "fairly stable", but there's of course no guarantee for any revision. OTOH, if you install from SVN, and a particular revision gives you trouble, it's pretty easy to update to a more recent version.
> The same question goes for genshi.
If you use trunk, you must install the advanced-i18n branch of Genshi:
http://svn.edgewall.org/repos/genshi/branches/experimental/advanced-i18n
> Also: mod_python seems to be dead and it limits us to Python 2.5. Is
> WSGI working properly by now?
WSGI is actually the recommended way to run Trac.
> mySQL 5.1 is also available: is it better to use mySQL or sqlite?
This depends on the number of users, and how often they use Trac. For small installations (~50 users), SQLite is more than adequate. If you have more users, I would suggest using PostgreSQL. While MySQL works and is officially supported, it has a few drawbacks (you can read about them on the MySQL page on trac.edgewall.org) and not that many users.
Good luck!
-- Remy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|
signature.asc
