We are certainly getting there anyway :-)

Have su'ed in as apache and created a test file in /var/local/cache/midgard
without any problems.  I also wrote a simple php program to write a test
file to this directory - it appears that apache cannot 'see' into the cache
directory in /var/local/cache and with a bit of investigation found that
indeed /var/local/cache had root 700 permissions only.  Setting this to 755
sorted that out.  Shouldn't this be set to either apache accessible or world
readable on installation?

I commented out
MidgardPageCacheDir /var/local/cache/midgard
MidgardRootFile /usr/lib/apache2/modules/midgard-root.php

(forgot to comment out midgard-root.php last time)

And uncommented 

MidgardRootfile /usr/lib/apache2/modules/midgard-root-nommp.php

And we are back to the start again with:

Fatal error: Not a midgard request. In
/usr/lib/apache2/modules/midgard-root-nommp.php on line 40

AGHHHHHHHHHH! Sorry had to vent.  I have to admit that this has gone through
annoying into that state of amusement where it is better to laugh than cry.

Apache log:

[Fri Feb 04 11:16:59 2005] [debug] midgard-apache2.c(2077): [client
192.168.6.64] midgard_translate_handler(UTF-8,
http://192.168.6.64:8080/spider-admin/)
[Fri Feb 04 11:16:59 2005] [debug] select_db2.h(51): [client 192.168.6.64]
Midgard: select_database opened database midgard
[Fri Feb 04 11:16:59 2005] [debug] midgard-apache2.c(513): [client
192.168.6.64] Midgard: lang set to 0
[Fri Feb 04 11:16:59 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 11:16:59 2005] [debug] midgard-apache2.c(443): [client
192.168.6.64] Midgard: user admin (1) authorized
[Fri Feb 04 11:16:59 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 11:16:59 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 11:16:59 2005] [debug] midgard-apache2.c(2288): [client
192.168.6.64] Midgard: serving page
/usr/lib/apache2/modules/midgard-root-nommp.php
[Fri Feb 04 11:16:59 2005] [debug] midgard-apache2.c(2293): [client
192.168.6.64] Midgard: setting blobdir /var/local/lib/midgard/blobs/midgard

So having fixed the cache problem, I reversed the actions above to re-enable
the caching and disable nommp and tried again.

The browser remained blank and the apache log provided me with something i
really didn't want to see:

[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(2077): [client
192.168.6.64] midgard_translate_handler(UTF-8,
http://192.168.6.64:8080/spider-admin/)
[Fri Feb 04 12:02:23 2005] [debug] select_db2.h(51): [client 192.168.6.64]
Midgard: select_database opened database midgard
[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(513): [client
192.168.6.64] Midgard: lang set to 0
[Fri Feb 04 12:02:23 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(443): [client
192.168.6.64] Midgard: user admin (1) authorized
[Fri Feb 04 12:02:23 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(1287): [client
192.168.6.64] Midgard: extension = .php, default: .php, parser = UTF-8
[Fri Feb 04 12:02:23 2005] [debug] select_db2.h(33): [client 192.168.6.64]
Midgard: select_database kept current database midgard
[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(2288): [client
192.168.6.64] Midgard: serving page /var/local/cache/midgard/7-57-12-0.php
[Fri Feb 04 12:02:23 2005] [debug] midgard-apache2.c(2293): [client
192.168.6.64] Midgard: setting blobdir /var/local/lib/midgard/blobs/midgard
[Fri Feb 04 12:02:24 2005] [notice] child pid 18538 exit signal Segmentation
fault (11)

If I had hair, I would be tearing it out right now.  Php segfaults again.

I think I will stick with 1.6.2 but revert back to apache 1 (oh joy I get to
do this all over again) as it appears to be the only working solution for
me.

Cheers

Mike.

----------------------------------------------------
Michael Ross - Pan Leeds Web Developer

Health Informatics Service����� Tel: (0113) 305 7416
2nd Floor������ ������� ������� Fax: (0113) 305 7398
North West House
West Park Ring Road
West Park
Leeds
LS16 6QG 


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

Reply via email to