rc.httpd won't start on boot

pioniere · 06-25-2006, 11:53 PM

For some reason that eludes me, /etc/rc.d/rc.httpd will not start apache automatically when my Slackware 10.2 server boots. I can start apache manually after the fact using apachectl start, but the rc.httpd script is not starting in on boot.

I have verified the permissions on rc.httpd to be 755, and owned by root. Can anyone suggest anything I might be missing? Thanks.

prozac · 06-26-2006, 12:01 AM

have you run the rc.httpd script manually and verified that apache runs successfully? might be a problem there. care to post it here?

Vgui · 06-26-2006, 01:18 PM

It could also be that the rc.httpd script is not called from another script (such as rc.M). Try "grep rc.httpd *" inside of /etc/rc.d/ and ensure that another script is calling it. Just putting the script to executable does not mean it will run, often times you need to add it to rc.M, rc.S, or rc.local.

pioniere · 06-27-2006, 05:18 PM

Looking inside rc.httpd, it starts apache using

Code:

apachectl startssl

This is the statement that it fails on. So the question now is why?

gilead · 06-27-2006, 05:34 PM

If you haven't set up keys/certs and configured Apache to use SSL then it won't start. You could try changing rc.httpd to use start instead of startssl or you could set it up to use ssl. There are plenty of tutorials on doing this - one of them that should help is at http://www.vanemery.com/Linux/Apache/apache-SSL.html

pioniere · 06-27-2006, 05:56 PM

I did some more digging (prior to reading the last post by Gilead), and found that in mod_ssl.conf it is set to Listen on both port 80 and port 443. I commented out the Listen 80 statement, and apachectl startssl started successfully:

Code:

root      6451     1 16 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6452  6451 19 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6453  6451  0 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6454  6451  0 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6455  6451  0 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6456  6451  0 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL
nobody    6458  6451  0 15:41 ?        00:00:00 /usr/sbin/httpd -DSSL

In reply to Gilead's post, the certs had already been created, and as far as I know they were done correctly.

I was able to connect to my site using https.

So... does that Listen 80 statement really need to be there? Or am I missing something (or leaving something open/broken) by not having it?

gilead · 06-27-2006, 06:51 PM

If you're only serving up pages via SSL you only need port 443 open, so removing the Listen 80 directive won't cause any problems. You should be able to have both though, so I'm confused as to why that fixed the problem.

In any case I'm glad that it's working for you...

pioniere · 06-27-2006, 08:39 PM

Interesting, because I serve pages also through port 80, and this change has not affected them. So, like you, I am confused as well.