httpd no start, Error after update Ispconfig. 3.
Hello to all.
Long time to dont ask nothing just because ispconfig works fine.
Last nigth i update my ispconfig 3.0.4 to 220.127.116.11 and all works fine after update. But today i restart httpd and dont start. He show this error:
[Wed May 15 10:02:36 2013] [warn] NameVirtualHost *:443 has no VirtualHosts
[Wed May 15 10:02:36 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
and httpd dont start it. I read a lot on forums, and till says that this is not an error, but in my case something happened since my apache server dont star and show me the error of virtualhost. I looked at several options but none I've fixed the problem. Can you help? Thank you.
i'd say you're right in that those two messages on their own are not a problem - its just that apache is listening on a port with no vhosts. There are lots of notes around about resolving that but on its own not a problem.
Are you saying that httpd fails to start altogether? Are you saying you cannot see httpd in a process list or access any of the sites?
You don't say what OS you're running, have a look in the log files see if there's any errors. This could be /var/log/httpd/error.log or similar.
You might try "httpd -D FOREGROUND" see if it spits out any errors there as well?
Hello monkfish, yes i know that this is not error. But after update my ispconfig and restart my apache it dont start it and show me:
starting httpd: [Wed May 15 10:56:17 2013] [warn] NameVirtualHost *:443 has no VirtualHosts
[Wed May 15 10:56:17 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
so now i dont have my web sites online, obviously because my apache stop it.
I have centos 6.3, i have it ispconfig 3.0.4 and all works fine but i update to 18.104.22.168 and get this error. Logs dont show any erros about this. And httpd -D FOREGROUND show this
[Wed May 15 10:43:54 2013] [warn] NameVirtualHost *:443 has no VirtualHosts
[Wed May 15 10:43:54 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
Thank you for you reply.
Right, so you have got it running in the foreground or does it bail with further error?
If it just sits there after spitting those lines out and doesnt return you to a prompt, I would suggest thats its running.
If its running can you access your sites then? Can you ssh back into the box and do a netstat or a ps and see if httpd shows up.
also try a "apachectl -t" see if your config files check out OK?
maybe a " apachectl -t -D DUMP_VHOSTS" see if your vhost files show up OK.
Once you get your httpd started perhaps go for a resync within the ispconfig interface, the config files will be rewritten
Monkfish thank you for you reply.
Apache is no runing.
If its not running it should put an entry in /var/log/httpd/error.log as to why its unable to start?
error.log show this on final line:
[Wed May 15 11:14:58 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed May 15 11:14:58 2013] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Wed May 15 11:14:58 2013] [error] Unable to configure RSA server private key
[Wed May 15 11:14:58 2013] [error] SSL Library Error: 185073780 error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch
I dont know if this error has something to do with the NameVirtualHost error which leaves no start the apache.
Thats suggesting one or more SSL certificates you have applied have an issue which is why apache is prevented from starting.
Have you recently changed/altered ssl certs? Have any expired?
Google is your friend on private key errors.
This user dealt with it previously;
However, I'd try commenting out " SSLEngine on" in any vhost files in /etc/httpd/conf/sites-enabled and see if apache then starts. Suppose it depends if you have https just for ispconfig or you have client sites using it.
If you get it back up you can always reapply the certs through the interface.
hunnn monkfish you have rigth, is the FUC?=")/$!"/$ certificates, no i dont changed my certificates, but maybe when I upgrade my ispconfig I think i was create certificates again and that caused this problem, i ll reinstall now SSL certificates again to keep things running well. Thanks a lot, really i did not know what affected the apache certificates. Thanks for your help.
Hmm, you don't really say whether it was ispconfig SSL cert or a client cert.
If it was ispconfig look in /usr/local/ispconfig/interface/ssl/ - you may find older certificates in there and could simply swap the files over, then uncomment the entry again, that may work for you.
I was under the impression there was an option during upgrade to recreate SSL certificates and the default is NO?
|All times are GMT +2. The time now is 23:33.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.