Further info on this: In one of our websites I set MidgardEngine to off and tried http://<website>/webalizer and it works fine. Its only when MidgardEngine is turned on does it cause problems. It is almost as if it is ignoring the Alias setting in the apache vhost config. All websites not using Aegir/Midgard work fine for webstats. Very strange.
Mike. -----Original Message----- From: Michael Ross (PCT North West) [mailto:[EMAIL PROTECTED] Sent: 28 October 2004 10:49 To: '[EMAIL PROTECTED]' Subject: [midgard-user] Webstats Hi All, I know you have dealt with webstats through webalizer before and until I set up this new machine I have had it working without any problems (thanks :-)). The problem I have is that on this server, when I go to either http://<website>/webalizer/index.html or go through aegir, all I get is the root page of the website being displayed i.e. http://<website>/ - In Aegir all the sites are listed (summary, monthly data etc) as usual, but clicking on Summary for example, once again takes me to http://<website>/ and not the webstats. All the directories exist, so all I could think of is that it is some form of permissions problem. I have aliases set up in all my vhost scripts to point to by webalizer directory: <VirtualHost 217.154.157.227:80> ServerName <website> Port 80 MidgardEngine On #MidgardPageCacheDir /var/www/midgard/livecache MidgardRootFile "/usr/lib/apache/midgard-root.php" php_flag register_globals on php_value magic_quotes_gpc off php_value magic_quotes_runtime off MidgardDatabase midgardlive midgard midgard MidgardBlobDir "/var/www/midgard/liveblobs" CustomLog /var/log/apache/<website>-access.log combined Alias /webalizer/ /var/www/localhost/htdocs/webalizer/<website>/ </VirtualHost> The apache error log reports: [Thu Oct 28 10:48:55 2004] [debug] mod_midgard.c(1325): [client 62.6.139.11] midgard_translate_handler(latin1, http://<website>:80/webalizer/usage_200410.html) [Thu Oct 28 10:48:55 2004] [debug] select_db.h(67): [client 62.6.139.11] Midgard: switching to midgardlive [Thu Oct 28 10:48:55 2004] [debug] mod_midgard.c(852): [client 62.6.139.11] Midgard: resolving path element: user #0 searches link webalizer [Thu Oct 28 10:48:55 2004] [debug] mod_midgard.c(151): [client 62.6.139.11] Midgard: locating blob=[159]/webalizer [Thu Oct 28 10:48:55 2004] [debug] select_db.h(33): [client 62.6.139.11] Midgard: select_database kept current database midgardlive [Thu Oct 28 10:48:55 2004] [debug] mod_midgard.c(1446): [client 62.6.139.11] Midgard: using style #17 (22 elements) [Thu Oct 28 10:48:55 2004] [debug] select_db.h(33): [client 62.6.139.11] Midgard: select_database kept current database midgardlive As far as I can tell it is set up exactly like all the other servers, but for the life of me I cannot figure out why this is happening. any ideas? Cheers Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
