On Thu, 2006-03-23 at 01:13 -0500, Jerry Geis wrote:
/ After updating to 4.3 I cant get httpd to startup.
/>/ I see no messages in /var/log/message other that httpd failed. />/ />/ I see no errors in /var/log/httpd/error_log />/ />/ there is mention in ssl_error_log that no RSA or DSA certificate is found. />/ I dont know what to do about that.I tried starting in the non fork mode />/ but all it does is give me a prompt no error message . />/ />/ Also of note I am having issue with sshd. It starts up but I cannot connect />/ to the machine. />/ />/ I have been at this for a couple hours now. trying anything... />/ />/ Jerry /
Please look hard at your selinux. I suspect that is where your problems lie if it is turned on.
Johnny and all,
My selinux is turned off.
doing rpm -qa | grep httpd does not show duplicate packages.
Is there a way to "freshen" the new packages for 4.3. Kind of a way to reload the packages without SCRAPPING the partition and starting from scratch? just a thought.
Is there someway to tell what httpd doesnt like? When I run httpd with options to check config files and things like that it runs an prints a couple lines and prints status OK. So the exe is running just not as a background process.
Thanks
Jerry
On Thu, 2006-03-23 at 07:35 -0500, Jerry Geis wrote:
On Thu, 2006-03-23 at 01:13 -0500, Jerry Geis wrote:
/ After updating to 4.3 I cant get httpd to startup.
/>/ I see no messages in /var/log/message other that httpd failed. />/ />/ I see no errors in /var/log/httpd/error_log />/ />/ there is mention in ssl_error_log that no RSA or DSA certificate is found. />/ I dont know what to do about that.I tried starting in the non fork mode />/ but all it does is give me a prompt no error message . />/ />/ Also of note I am having issue with sshd. It starts up but I cannot connect />/ to the machine. />/ />/ I have been at this for a couple hours now. trying anything... />/ />/ Jerry /
Please look hard at your selinux. I suspect that is where your problems lie if it is turned on.
Johnny and all,
My selinux is turned off.
doing rpm -qa | grep httpd does not show duplicate packages.
Is there a way to "freshen" the new packages for 4.3. Kind of a way to reload the packages without SCRAPPING the partition and starting from scratch? just a thought.
Is there someway to tell what httpd doesnt like? When I run httpd with options to check config files and things like that it runs an prints a couple lines and prints status OK. So the exe is running just not as a background process.
Thanks
Jerry
Seems to me that you had a problem generating the ssl keys for this and sshd ... (by what I read before).
Removing and reinstalling these pacakges should help.
Jerry Geis wrote on Thu, 23 Mar 2006 07:35:56 -0500:
When I run httpd with options to check config files and things like that it runs an prints a couple lines and prints status OK
You mentioned an SSL error message earlier. The configtest parameter unfortunately doesn't test SSL. All the SSL is in conf.d/ssl.conf, rename it to ssl.conf.stop or whatever you like and try again. Only .conf files are read.
Kai
Kai Schaetzl wrote:
doesn't test SSL. All the SSL is in conf.d/ssl.conf, rename it to ssl.conf.stop or whatever you like and try again. Only .conf files are read.
I would not recommend renaming it; instead, edit the file and put a hash (#) in front of all the lines. The reason is that a future upgrade of mod_ssl will install a stock ssl.conf if it's missing, whereas if it's present (and commented out) it will remain intact.
Same goes for any of the other conf.d/ files (mailman, welcome, etc). I usually comment all of them out and encapsulate the needed code into virtual include files other places, which can then be tracked in version control.
-te
Troy Engel wrote on Thu, 23 Mar 2006 16:51:00 -0800:
I would not recommend renaming it; instead, edit the file and put a hash (#) in front of all the lines. The reason is that a future upgrade of mod_ssl will install a stock ssl.conf if it's missing, whereas if it's present (and commented out) it will remain intact.
Good advice. I didn't think about long term, though, just renaming is quickly done and he can get going (if that was the problem) quickly while starting to comment out or actually fix it ... BTW: I'd expect newer config files go to *.rpmnew. I have done too few upgrades on CentOS to know if that expectation is valid.
Kai
Kai Schaetzl wrote:
BTW: I'd expect newer config files go to *.rpmnew. I have done too few upgrades on CentOS to know if that expectation is valid.
Same here, I haven't really paid attention. I can confirm though that the commented out files are not overwritten, which is what we want. I'd have to poke around on some servers for .rpmnew files.
-te
-
Jerry Geis -
Johnny Hughes -
Kai Schaetzl -
Troy Engel