Question: why doesn't MARC permit http replies to messages?
Mike
Hi Andreas.
My reply follows:
Hi Mike,
Hi Andreas.
Thanks for your reply. I've done all you mention and think that I am making progress getting this thing going.
Great!
1) Yes, you are correct, /etc/httpd/midgard.conf did set the virtual ports for 80, 8099, 8101 & 8102 AND (most importantly) set the ServerName for <linux.local>.
2) There were inconsistencies between
You need to set it only once, I have mine in midgard.conf as this my/etc/httpd/midgard.conf and /etc/httpd/httpd.conf, specifically as regards ServerName. /etc/httpd/httpd.conf did not have a specified ServerName.
central place for all the midgard host information. just put a "#" in front
of the servername in httpd.conf
3) A review of the host table for the midgard database
4) I have now set, as perwith phpMyAdmin or an sql query from command line indicated that ports for ALL midgard components were set for 80.
your suggestion, components <aegir> & <attachment> to port 8099.5) I
have also rendered the ServerName consistent between /etc/httpd/midgard.conf & /etc/httpd/httpd.conf. ServerName is localhost in /etc/httpd/midgard.conf & 127.0.0.1 in /etc/httpd/httpd.conf
6) It should be noted that the midgard box is on
a LAN and has an internal DHCP served IP of 192.168.168.173. There are consistent issues relative to calling the midgard asgard site from any remote machine. These issues have pervaded the whole process of installing the first two pieces of midgard. Now, asgard can be consistently called from the midgard box, but a call to 192.168.168.173:80/asgard does not serve the page. Can you suggest a better ServerName?
5+6) Okay, thats how it should be.....however every computer that has
a network card installed gets the internal IP of 127.0.0.1 or localhost. If
you are workin on the Midgard box you can access the needed
information, however if you try localhost or 127.... from another
machine, this computer will assume that you want to access itself.
Therefor, if possible(?) give your Midgard box a fixed IP.....if not, right
now you should set (with your IP of 192.168.168.173)
in midgard.conf
ServerName 192.168.168.173
NameVirtualHost 192.168.168.173 for port 80,8099 etc.
and
<VirtualHost 192.168.168.173:80>
<VirtualHost 192.168.168.173:8099> etc. for all host defined.
<reply> OK This has been done
Use phpmyadmin again and change everything in the "name" field from localhost to 192.168.168.173.
<reply> OK This has been done
Now you should be able (after restart of Apache) to access your host from any machine on your network.
7) Now, from the midgard box, the Aegir page can be
called through a couple of clicks on the host tab at the top of the asgard screen.
But the graphics for Aegir do NOT load. As well, the
login <admin> password <password> does NOT work. I must note that as per your suggestion I did move the aegir directory (and subdirectories) to /var/lib. It would seem that some of the files are not being found, correct?
1. Hmm, the images from aegir should be in your blobdir. Can you check what blobdir is defined in repligard.conf (/etc/midgard)and what is defined in midgard.conf (/etc/httpd)?
<reply> INCONSISTENCIES: /etc/httpd/midgard.conf has blobdir as '/var/lib/wwwrun/blob'. /etc/midgard/repligard.conf has blobdir as '/var/www/blobs'. A check of files shows no '/var/www/blobs' There is a '/var/www/midgardblobs' and there is also a 'var/lib/wwwrun/blob'
What do I do to fix this?
2. okay, thats another trick :-) you need to go to your php.in file (located in /etc)
(hmm, have to remember it correctly now.....Piotras, anybody, please correct me if I give wrong information now! )
check wether "register_globals = On" and "magic_quotes_runtime = Off "
<reply>OK, but what about security issues with 'register_globals=On'?
Now restart the server once again (apache).
<reply>Errors. Apache did NOT like
linux:/etc/httpd # rcapache restart
Shutting down httpd done
Starting httpd [ Midgard PHP4 ][Thu May 13 12:21:19 2004] [warn] module midgard_module is already loaded, skipping
[Thu May 13 12:21:20 2004] [warn] module mod_midgard.c is already added, skipping
[Thu May 13 12:21:20 2004] [error] Failed to resolve server name for 192.168.168.173 (check DNS) -- or specify an explicit ServerName
[Thu May 13 12:21:20 2004] [error] Failed to resolve server name for 192.168.168.173 (check DNS) -- or specify an explicit ServerName
[Thu May 13 12:21:20 2004] [error] Failed to resolve server name for 192.168.168.173 (check DNS) -- or specify an explicit ServerName
Well, glad i can help out a bit!
Thanks for any further suggestions on this as we would certainly like to continue efforts to setup midgard.
<reply>What's next?
Mike
Andreas
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
