Answer the question
In order to leave comments, you need to log in
httpd does not start, what to do?
Can't restart httpd, server down.
Centos, vestacp panel.
Today I made yum update packages, I don’t remember if httpd fell off right away or if these events are not connected in any way.
Nginx won't start either. There is access to the panel itself.
Before that, also today all the mysql databases on the server turned out to be empty....
Although the databases are in /var/lib/mysql with info!
So far I have not understood the hacking or a server failure ...
All databases exist, but they are empty, 1kb (not in /var/lib/mysql).
All bases were under different users. mysql service is up and running.
Briefly, the configs are the same as on other servers under Vestacp, everything works there.
Error while restarting httpd:
service httpd restart
httpd: apr_sockaddr_info_get() failed for name32
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Stopping httpd: [FAILED]
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 91.23.210.178:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.210:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.211:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.208:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.209:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 145.202.134.179:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.49:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.48:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.51:8080 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.51:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.50:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 145.202.135.49:8443 has no VirtualHosts
(99)Cannot assign requested address: make_sock: could not bind to address 158.35.234.48:80
no listening sockets available, shutting down
Unable to open logs
Starting httpd: [FAILED]
2015/12/11 02:35:07 [emerg] 7147#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)
2015/12/11 02:36:10 [emerg] 7205#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)
2015/12/11 02:48:37 [emerg] 3806#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)
[Thu Dec 10 17:50:39 2015] [notice] caught SIGTERM, shutting down
NameVirtualHost XX.XX.XXX.XXX:8080
Listen XX.XX.XXX.XXX:8080
NameVirtualHost XX.XX.XXX.XXX:8443
Listen XX.XX.XXX.XXX:8443
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
XX.XX.XXX.XXX ns3008.ip-98-24-201.eu ns3008
Answer the question
In order to leave comments, you need to log in
Have you accidentally lost your network interface? On the 80th port, it can also swear because it cannot find the entire interface.
netstat -ntlp
<code>tcp 0 0 0.0.0.0:3306 0.0.0.0:* LIST EN 3742/mysqld
tcp 0 0 127.0.0.1:3310 0.0.0.0:* LIST EN 3397/clamd
tcp 0 0 127.0.0.1:783 0.0.0.0:* LIST EN 3783/spamd.pid
tcp 0 0 0.0.0.0:8083 0.0.0.0:* LIST EN 3815/nginx
tcp 0 0 0.0.0.0:21 0.0.0.0:* LIST EN 3385/vsftpd
tcp 0 0 XXX.33.XXX.51:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.33.XXX.50:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.32.XXX.211:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.32.XXX.210:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.32.XXX.209:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.33.XXX.49:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.32.XXX.208:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.202.XXX.49:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.202.XXX.179:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 XXX.23.XXX.178:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LIST EN 3296/named
tcp 0 0 0.0.0.0:22 0.0.0.0:* LIST EN 3372/sshd
tcp 0 0 127.0.0.1:953 0.0.0.0:* LIST EN 3296/named
tcp 0 0 :::22 :::* LIST EN 3372/sshd
tcp 0 0 ::1:953 :::* LIST EN 3296/named
</code>
you need to look at the http config, because when updating, the old config could be partially rewritten or replaced.
You seem to have two Apache instances (or someone else) fighting for port 80.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question