[mod_python] Can't get it to interpret

Hi all!

well, since I'm at full speed at trying to get this running, I'm on several lists besides this one...  I just got this from the NAV list (both interesting...I'm going to try two approaches and let you all know.  First, I'm adding a few more search paths and second I'll try the VirtualHost approach.)
.
.
.

The missing session attribute would occur if NAV's headerparserhandler
was not properly run by mod_python.  The .htaccess file in the webroot
directory configures the nav.web module to act as the
headerparserhandler hook for that directory and all subdirectories.

Question is, is the .htaccess file present in webroot, and are .htaccess
files enabled in your httpd.conf?

--
mvh
Morten Brekkevold
UNINETT


Unfortunately, NAV assumes it will be at the document root of the
server.  If you are unable to set up NAV on a VirtualHost of its own,
then you won't get the web interface up and running as it stands today.

--
mvh
Morten Brekkevold
UNINETT


-----Original Message-----
From: Jim Gallacher [mailto:jpg at jgassociates.ca]
Sent: Mon 10/2/2006 5:07 PM
To: Paul J. Pathiakis
Cc: Graham Dumpleton; mod_python at modpython.org
Subject: Re: [mod_python] Can't get it to interpret
 
Paul J. Pathiakis wrote:
> ** Graham,
> 
> 
> If the PythonHeaderParserHandler wasn't there, I would say that the
> PythonPath directive isn't required as mod_python.publisher doesn't
> require it to be set as described.
> 
> The question is, what is 'nav.web' and what does the handler in it
> do? Most people wouldn't have a need to be defining a handler for
> the PythonHeaderParserHandler phase. What it does will dictate
> whether or not PythonPath needs to be set as indicated or whether
> the comment about what to do derives from a misunderstanding as to
> how mod_python works.

FYI Graham, the authentication is performed in by the 
PythonHeaderParserHandler handler.

> Graham
> 
> ** Well, nav.web is a directory /usr/local/nav/lib/python/.  NAV is a directory in the director.  Web is the directory underneath it.  I believe it's supposed to be the web interface to the NAV software.  There's about 20 files in there.  I'm trying to figure out if there's an easier way to interface.  Personally, I was looking at my httpd.conf file and wanted to just alias the /usr/local/nav/webroot directory.  (Someone else mailed me with the same idea)  
> 
> Now that I added to the path, I have now encountered this (which seems to point that there is a login attempt into a database, tell me, what information can I send the list to further my cause?):
> 
> Mod_python error: "PythonHeaderParserHandler nav.web"
> 
> Traceback (most recent call last):
> 
>   File "/usr/local/lib/python2.4/site-packages/mod_python/apache.py", line 287, in HandlerDispatch
>     log=debug)
> 
>   File "/usr/local/lib/python2.4/site-packages/mod_python/apache.py", line 464, in import_module
>     module = imp.load_module(mname, f, p, d)
> 
>   File "/usr/local/nav/lib/python/./nav/web/__init__.py", line 28, in ?
>     import nav.web.auth
> 
>   File "/usr/local/nav/lib/python/./nav/web/auth.py", line 31, in ?
>     from nav import db
> 
>   File "/usr/local/nav/lib/python/./nav/db/__init__.py", line 103, in ?
>     setDefaultConnection(getConnection('default'));
> 
>   File "/usr/local/nav/lib/python/./nav/db/__init__.py", line 86, in getConnection
>     connection = psycopg.connect('host=%s dbname=%s user=%s password=%s' %
> 
> OperationalError: fe_sendauth: no password supplied
> 
> Thanks,

I'd say you are pretty close to getting this puppy working. My guess is 
that there is some other spot in the NAV where host, dbname, user and 
password are configured. Once you've found that you should be off to the 
races.

Jim



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20061003/ef8041a4/attachment-0001.html