> I also installed this from cooker along with mod_perl and now I get
> "connection refused" trying to access my site on port 80.
> I even get refused trying to telnet to port 80 on loclhost, although I can
> telnet to 22/23/25/443... What went wrong ?
>
> I noticed that when I start up httpd, I now get new perl processes...
> root 11118 1 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
> root 11126 1 0 Aug10 ? 00:00:00 httpd-perl -f
>/etc/httpd/conf/httpd-perl.conf -DPERLPROXIED
> root 11131 11118 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
> www 11132 11118 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
> www 11133 11118 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
> www 11137 11126 0 Aug10 ? 00:00:00 httpd-perl -f
>/etc/httpd/conf/httpd-perl.conf -DPERLPROXIED
> www 11140 11126 0 Aug10 ? 00:00:00 httpd-perl -f
>/etc/httpd/conf/httpd-perl.conf -DPERLPROXIED
> www 11141 11118 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
> www 11142 11118 0 Aug10 ? 00:00:00 httpd -DPERLPROXIED
>
> I am just trying mod_perl for the first time, so is this normal ?
> Why has this disabled port 80 ?
>
> I noticed that the cooker version is changing the /etc/httpd/conf/httpd.conf
> so that the web root path is now /var/www instead. Although it seems they
> have /var/www linked back to /home/httpd... so what's the point of that ?
I fixed the problem. I don't know if this is how Linux-Mandrake has set this up
or this is how mod_perl does things. First, the perl proxy was now using port 8200
instead of 80. So nothing was running on port 80. I changed /etc/rc.d/rc3.d/S85httpd
to disable the lines that set "PERLPROXIED"
# if [ -x /usr/sbin/httpd -a -x /usr/sbin/httpd-perl ];then
# DEFINE="-DPERLPROXIED"
# fi
This way it uses port 80 and the default html document location.
However I found that all my virtual websites were pulling up the default index.shtml
instead of their respective ones. As well, no logging was done for virtual websites.
I needed to modify /etc/httpd/conf/httpd-perl.conf (which seems to now override
httpd.conf) to add in the <VirtualHosts ...> section I had before.
This fixed both problems. One problem was that
RefererLog logs/site1/referer_log
AgentLog logs/site1/agent_log
worked in httpd.conf but not in httpd-perl.conf, so I had to use this instead.
CustomLog logs/site1/referer_log referer
CustomLog logs/site1/agent_log agent
Also note that I found that if I did not manually create logs/site1/ directory,
then the httpd daemon would not start (nor create the directory).
>From my understanding, mod_perl enhanced Apache is better on a different server
than the regular one used for HTML requests, in order to offset heavier load.
For this case, using port 8200 could make sense but it's not much good if you
only use one server.
Thanks... Dan.
