I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I’m at a loss. I don’t really understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I suspect the recent issue relates to the death of our Peer1 firewall,
and it’s replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I’m going to catch the train into work now. I’d appreciate it if
someone else with some Apache/Drupal-fu could look into this. I have
–
---------------------------------------±-------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Software Developer
I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I'm at a loss. I don't really understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I *suspect* the recent issue relates to the death of our Peer1 firewall,
and it's replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I'm going to catch the train into work now. I'd appreciate it if
someone else with some Apache/Drupal-fu could look into this. I have
gotten the ssh issue fixed. Some info in:
Generally a firewall would simply block port 80/443, but since osgeo.org
seems to be working that doesn't seem the case. Now if for some reason
there are proxies going on and these are not localhost addressed they
might get broken. But generally php is directory based.
My guess is that vhosting is either off, or for some reason the vhosts
for fdo and mapguide got disabled since everything seems to point at
osgeo.org
I'm referring this to my drupal coworker who might have some ideas.
I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I'm at a loss. I don't really understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I *suspect* the recent issue relates to the death of our Peer1 firewall,
and it's replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I'm going to catch the train into work now. I'd appreciate it if
someone else with some Apache/Drupal-fu could look into this. I have
gotten the ssh issue fixed. Some info in:
Generally a firewall would simply block port 80/443, but since osgeo.org
seems to be working that doesn't seem the case. Now if for some reason
there are proxies going on and these are not localhost addressed they
might get broken. But generally php is directory based.
My guess is that vhosting is either off, or for some reason the vhosts
for fdo and mapguide got disabled since everything seems to point at
osgeo.org
I'm referring this to my drupal coworker who might have some ideas.
Thanks,
Alex
I checked the ports are open. So this does appear to be a vhost
configuration issue. It seems only the osgeo.org conf is being loaded,
which I assume is /etc/httpd/conf.d/hosts/osgo.conf ?
From my experience with apache the vhost files do not appear correct. On
my Debian/Ubuntu boxes when using named vhosts you set the opening line
as *:80 and then the ServerName line determines what is loaded.
I'm not sure if redhat style is different.
Also all 3 configurations point to the same /var/www/html documentroot
Are they all using the same Drupal site (shared code and database)? If
so then this makes sense and the issue is actually with drupal. But I
suspect it should be /var/www/fdo
So it looks like the apache confs are just all wrong.
I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I’m at a loss. I don’t really understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I suspect the recent issue relates to the death of our Peer1 firewall,
and it’s replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I’m going to catch the train into work now. I’d appreciate it if
someone else with some Apache/Drupal-fu could look into this. I have
gotten the ssh issue fixed. Some info in:
Generally a firewall would simply block port 80/443, but since osgeo.org
seems to be working that doesn’t seem the case. Now if for some reason
there are proxies going on and these are not localhost addressed they
might get broken. But generally php is directory based.
My guess is that vhosting is either off, or for some reason the vhosts
for fdo and mapguide got disabled since everything seems to point at osgeo.org
I’m referring this to my drupal coworker who might have some ideas.
Thanks,
Alex
I checked the ports are open. So this does appear to be a vhost
configuration issue. It seems only the osgeo.org conf is being loaded,
which I assume is /etc/httpd/conf.d/hosts/osgo.conf ?
From my experience with apache the vhost files do not appear correct. On
my Debian/Ubuntu boxes when using named vhosts you set the opening line
as *:80 and then the ServerName line determines what is loaded.
I’m not sure if redhat style is different.
Also all 3 configurations point to the same /var/www/html documentroot
Are they all using the same Drupal site (shared code and database)? If
so then this makes sense and the issue is actually with drupal. But I
suspect it should be /var/www/fdo
So it looks like the apache confs are just all wrong.
–
---------------------------------------±-------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Software Developer
I didn't manage to fix it. At least not on purpose. Mapguide does seem
to be working but not FDO.
Really I just couldn't make head or tails of the Redhat style Apache
config, the main site didn't seem to be configured anywhere obvious and
the vhost confs all look broken based on how I understand Apache syntax.
So its still a mystery.
Thanks,
Alex
On 11/11/2013 06:47 AM, Frank Warmerdam wrote:
Alex,
I see the FDO and MapGuide sites are available. Could you or your friend
update the Trac ticket with details of what was done?
On Fri, Nov 8, 2013 at 9:56 AM, Alex Mandel <tech_dev@wildintellect.com>wrote:
On 11/08/2013 09:43 AM, Alex Mandel wrote:
On 11/08/2013 09:37 AM, Frank Warmerdam wrote:
Folks,
I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I'm at a loss. I don't really
understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I *suspect* the recent issue relates to the death of our Peer1 firewall,
and it's replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I'm going to catch the train into work now. I'd appreciate it
if
someone else with some Apache/Drupal-fu could look into this. I have
gotten the ssh issue fixed. Some info in:
Generally a firewall would simply block port 80/443, but since osgeo.org
seems to be working that doesn't seem the case. Now if for some reason
there are proxies going on and these are not localhost addressed they
might get broken. But generally php is directory based.
My guess is that vhosting is either off, or for some reason the vhosts
for fdo and mapguide got disabled since everything seems to point at
osgeo.org
I'm referring this to my drupal coworker who might have some ideas.
Thanks,
Alex
I checked the ports are open. So this does appear to be a vhost
configuration issue. It seems only the osgeo.org conf is being loaded,
which I assume is /etc/httpd/conf.d/hosts/osgo.conf ?
From my experience with apache the vhost files do not appear correct. On
my Debian/Ubuntu boxes when using named vhosts you set the opening line
as *:80 and then the ServerName line determines what is loaded.
I'm not sure if redhat style is different.
Also all 3 configurations point to the same /var/www/html documentroot
Are they all using the same Drupal site (shared code and database)? If
so then this makes sense and the issue is actually with drupal. But I
suspect it should be /var/www/fdo
So it looks like the apache confs are just all wrong.
FDO is working fine for me now too. So it seems it fixed itself, or perhaps depends on some other factor (assuming FDO is still broken for you) that we haven’t characterized yet?
I didn’t manage to fix it. At least not on purpose. Mapguide does seem
to be working but not FDO.
Really I just couldn’t make head or tails of the Redhat style Apache
config, the main site didn’t seem to be configured anywhere obvious and
the vhost confs all look broken based on how I understand Apache syntax.
So its still a mystery.
Thanks,
Alex
On 11/11/2013 06:47 AM, Frank Warmerdam wrote:
Alex,
I see the FDO and MapGuide sites are available. Could you or your friend
update the Trac ticket with details of what was done?
I have tried to investigate why the FDO and MapGuide sites are
no longer worked on osgeo1, but I’m at a loss. I don’t really
understand
how Drupal and Apache virtual hosts well enough to figure out what is
going wrong.
I suspect the recent issue relates to the death of our Peer1 firewall,
and it’s replacement. It may be that the firewall used to have some
rules related to virtual hosting that are now lost and forgotten, or it
might just be that this trigger a reboot of osgeo1 that turned on
configuration changes made a while ago.
Anyways, I’m going to catch the train into work now. I’d appreciate it
if
someone else with some Apache/Drupal-fu could look into this. I have
gotten the ssh issue fixed. Some info in:
Generally a firewall would simply block port 80/443, but since osgeo.org
seems to be working that doesn’t seem the case. Now if for some reason
there are proxies going on and these are not localhost addressed they
might get broken. But generally php is directory based.
My guess is that vhosting is either off, or for some reason the vhosts
for fdo and mapguide got disabled since everything seems to point at osgeo.org
I’m referring this to my drupal coworker who might have some ideas.
Thanks,
Alex
I checked the ports are open. So this does appear to be a vhost
configuration issue. It seems only the osgeo.org conf is being loaded,
which I assume is /etc/httpd/conf.d/hosts/osgo.conf ?
From my experience with apache the vhost files do not appear correct. On
my Debian/Ubuntu boxes when using named vhosts you set the opening line
as *:80 and then the ServerName line determines what is loaded.
I’m not sure if redhat style is different.
Also all 3 configurations point to the same /var/www/html documentroot
Are they all using the same Drupal site (shared code and database)? If
so then this makes sense and the issue is actually with drupal. But I
suspect it should be /var/www/fdo
So it looks like the apache confs are just all wrong.
–
---------------------------------------±-------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Software Developer