On 10 May 2002, Armand A. Verstappen wrote: > First check if it will log db hits if you create them yourself, just to > verify if sql-logging is working at all.
It does. > Then, move the 'MidgardEngine On' statement out of the virtual host > context into the global context. After stopping and starting apache you > should check the error_log again (still on debug). If you find messages > about 'midgard_translate_handler', this means that apache fails to [Fri May 10 14:24:51 2002] [info] mod_unique_id: using ip addr 192.168.0.2 [Fri May 10 14:24:52 2002] [notice] Apache/1.3.24 (Unix) PHP/4.0.6 Midgard/1.4.2-1/SG configured -- resuming normal operations [Fri May 10 14:24:52 2002] [info] Server built: May 10 2002 06:24:56 [Fri May 10 14:24:52 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) [Fri May 10 14:26:11 2002] [debug] mod_midgard.c(1286): [client 12.23.198.199] midgard_translate_handler(latin1, http://bajan.cricalix.net:8181/asgard) [Fri May 10 14:26:11 2002] [debug] select_db.h(51): [client 12.23.198.199] Midgard: select_database opened database midgard [Fri May 10 14:26:11 2002] [debug] mod_midgard.c(1333): [client 12.23.198.199] Midgard: host record for bajan.cricalix.net:8181 not found [Fri May 10 14:26:11 2002] [error] [client 12.23.198.199] File does not exist: /devel/midgard/apache/htdocs/asgard Ahhh.. and therein lies the problem. Its querying with port 8181, despite the fact that the virtual host that should have /asgard is on port 8102 (and I'm calling for port 8102 in the browser). Thank you for the pointers - I think I'm going to go poke a bit harder now :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
