Groundwork Support Forum

[Mark]

Hello. I realize from the documentation that it is recommended that the Groundwork monitor is intended to run on a dedicated machine. However, I'm wondering what might be involved if one still wanted to run a separate Apache server on the same box.

In our case we've got a server that is currently primarily used for Nagios, but it does serve a few pages for my group. I would like to be able to run Groundwork in parallel with what's already on this machine and not disrupt what's there already (accounting for the load that Groundwork and Nagios would place on the server which should be bearable).

Unfortunately, the Apache that's already on the machine and Groundwork Monitor's httpd both want to run on port 80. Would it be possible to change the port that Groundwork Monitor runs on to allow the existing Apache to run? Might this be as simple as modifying /usr/local/groundwork/apache2/conf/httpd.conf to tell gwhttpd to run on some port other than 80? Or is the expectation that gwhttpd runs on port 80 embedded in too much other code to change this way?

Thanks

Mark

[dblunt]

Mark,

I'm not sure whether this has been tested yet or not, but you might consider exploring Apache virtual hosts to get around the port conflict issue. The following URL has some information on that topic:

http://httpd.apache.org/docs/2.0/vhosts/

It does require HTTP/1.1 support on any browser to implement named virtual hosts but it might be your best bet.


Dave.