I'm still having a similar problem mentioned eariler in the thread at
http://article.gmane.org/gmane.comp.web.midgard.user/6592. I am troubleshooting
this between two similarly configured machines, both running Debian sid. Midgard
works on one, but not on the other. 

The problem is on one machine, when attempting to access
http://localhost:8001/midgard, I get the "Welcome to Midgard CMS" page as I
should, but on the other I get "404 Not Found. The requested URL /midgard/ was
not found on this server."

I tried the various suggestions from the above thread; everything seems
identical on both machines (HOSTS table, permissions, library paths), so assumed
those weren't the problem.

The most hopeful indicator seems to be midgard-pageresolve, which gives the
following:

Machine "happy" (the one where Midgard is working just fine):

 [EMAIL PROTECTED] [~]# midgard-pageresolve -p 8001 -d dump.html -c ls -P [pwd]
 Connecting to mysql://midgard:<hidden>@localhost/midgard
 Resolving host: http://localhost:8001/
 RESULT: No host record match
 [EMAIL PROTECTED] [~]# 

Machine "sad" (where I get the "requested URL /midgard was not found on this
server" error):

 [EMAIL PROTECTED] [~]# midgard-pageresolve -p 8001 -d dump.html -c ls -P [pwd]
 Connecting to mysql://midgard:<hidden>@localhost/midgard
 Resolving host: http://localhost:8001/
 Host found: 4 in sitegroup 0
 Resolving page: http://localhost:8001/
 Page found: 49, active=2, redirect=0
 Path: 49:
 Style: 8
 Rebuilding cache for 49
 Parse page
 Cannot open root file midgard-root.php
 [EMAIL PROTECTED] [~]# 

The file /usr/lib/apache2/modules/midgard-root.php is identical on both 
machines.

With LogLevel set to debug on sad, I get the following when trying to access
http://sad:8001/midgard:

[Sun Dec 05 19:03:27 2004] [error] [client 192.168.2.200] File does not exist:
/var/www/midgard

I'm not quite sure how to interpret the above to fix this; any
suggestions/enlightenment? 

The only significant difference between the two is that sad is also running
tomcat4, and is using mod_jk2 (i.e., workers2.properties, as described on
http://www.junlu.com/msg/46421.html) to use apache to redirect and serve tomcat4
pages. Not sure if this might have something to do with it or not...

Thanks,

B.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to