Submitted by woltronix on Sat, 05/17/2014 - 05:23
It was working all servers correctly. I started to restore a server, which ultimately had an abortion. Report did not get to give to accept that it might restore. But after that will not let me load apache, I get the following errors. I hope your help, thanks
Iniciando httpd: [Sat May 17 11:56:31 2014] [error] VirtualHost _default_:443 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.140:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.141:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.142:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.143:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.132:80 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.132:443 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.144:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.145:0 has no VirtualHosts
[Sat May 17 11:56:31 2014] [warn] NameVirtualHost 192.168.4.146:0 has no VirtualHosts
(99)Cannot assign requested address: make_sock: could not bind to address 192.168.4.132:443
no listening sockets available, shutting down
Unable to open logs
Status:
Closed (fixed)
Comments
Submitted by andreychek on Sat, 05/17/2014 - 10:00 Comment #1
Howdy -- what is the output of these commands:
grep -i namevirtualhost /etc/httpd/conf/httpd.conf
grep "VirtualHost " /etc/httpd/conf/httpd.conf
ps auxw | grep httpd
Submitted by woltronix on Sat, 05/17/2014 - 19:00 Comment #2
Hi, this response is:
grep -i namevirtualhost /etc/httpd/conf/httpd.conf NameVirtualHost * NameVirtualHost 192.168.4.140 NameVirtualHost 192.168.4.141 NameVirtualHost 192.168.4.142 NameVirtualHost 192.168.4.143 NameVirtualHost 192.168.4.144 NameVirtualHost 192.168.4.145 NameVirtualHost 192.168.4.146 NameVirtualHost 192.168.4.120:80 NameVirtualHost 192.168.4.132:80 NameVirtualHost 192.168.4.132:443
grep "VirtualHost " /etc/httpd/conf/httpd.conf
copying them to /your/include/path/, even on a per-VirtualHost basis.NameVirtualHost * NameVirtualHost 192.168.4.140 NameVirtualHost 192.168.4.141 NameVirtualHost 192.168.4.142 NameVirtualHost 192.168.4.143 NameVirtualHost 192.168.4.144 NameVirtualHost 192.168.4.145 NameVirtualHost 192.168.4.146 NameVirtualHost 192.168.4.120:80 NameVirtualHost 192.168.4.132:80 NameVirtualHost 192.168.4.132:443
machine you can setup VirtualHost containers for them. Most configurations NameVirtualHost *:80 NOTE: NameVirtualHost cannot be used without a port specifier VirtualHost example: Almost any Apache directive may go into a VirtualHost container. The first VirtualHost section is used for requests without a knownps auxw | grep httpdroot 24827 0.0 0.0 105312 892 pts/0 S+ 01:37 0:00 grep httpd
Submitted by andreychek on Sat, 05/17/2014 - 20:01 Comment #3
Okay, thanks, that output helps.
It doesn't look like Apache has any processes running, but it wasn't able to start previously because it couldn't bind to port 443.
Try starting Apache again, with the following command:
service httpd start
Does that work, or do you still receive an error?
If you receive an error, what output do you receive if you run these two commands:
ifconfig
netstat -an | grep :443
Submitted by woltronix on Sun, 05/18/2014 - 08:40 Comment #4
service httpd restart Parando httpd: [FALLĂ“] Iniciando httpd: [Sun May 18 15:15:13 2014] [error] VirtualHost default:443 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.140:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.141:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.142:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.143:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.132:80 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.132:443 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.144:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.145:0 has no VirtualHosts [Sun May 18 15:15:13 2014] [warn] NameVirtualHost 192.168.4.146:0 has no VirtualHosts (99)Cannot assign requested address: make_sock: could not bind to address 192.168.4.132:443 no listening sockets available, shutting down Unable to open logs [FALLĂ“]
ifconfig em1 Link encap:Ethernet HWaddr D4:AE:52:C8:57:92
inet addr:192.168.4.120 Bcast:192.168.4.255 Mask:255.255.255.0 inet6 addr: fe80::d6ae:52ff:fec8:5792/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38279 errors:0 dropped:0 overruns:0 frame:0 TX packets:42630 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4954914 (4.7 MiB) TX bytes:5899695 (5.6 MiB) Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:278 errors:0 dropped:0 overruns:0 frame:0 TX packets:278 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22875 (22.3 KiB) TX bytes:22875 (22.3 KiB)
Submitted by andreychek on Sun, 05/18/2014 - 09:54 Comment #5
Ah, it looks like Apache is trying to listen on several IP addresses, but only one of those IP addresses is active.
Is this a new server?
If so, you may need to setup the IP addresses you're using on this server.
You can do that by going into Webmin -> Networking -> Network Configuration, and there you can add the IP addresses that your domains are using.
Submitted by woltronix on Sun, 05/18/2014 - 17:17 Comment #6
Hello, it goes. The server was working perfectly until yesterday. The only thing I did different was I was going to restore a backup, the subi but I did not apply. So, really I did nothing. I do not know as we have been able to change the settings for anything. It is very rare. I know it has not been able to change the settings.
Submitted by andreychek on Sun, 05/18/2014 - 17:40 Comment #7
Which domain were you attempting to restore?
And what IP address was it running on?
Submitted by JamieCameron on Sun, 05/18/2014 - 18:14 Comment #8
Yeah, it looks like the problem is that the IP 192.168.4.132 is used in one of your virtual hosts but is not active on the system.
What output do you get if you run
grep 192.168.4.132 /etc/httpd/conf/httpd.conf
Submitted by woltronix on Sun, 05/18/2014 - 19:08 Comment #9
grep 192.168.4.132 /etc/httpd/conf/httpd.conf Listen 192.168.4.132:443 NameVirtualHost 192.168.4.132:80 NameVirtualHost 192.168.4.132:443
Submitted by JamieCameron on Sun, 05/18/2014 - 19:40 Comment #10
OK, that's as a I expected. What you need to do is add a virtual interface for the IP 192.168.4.132 at Webmin -> Networking -> Network Configuration -> Network Interfaces.
Submitted by woltronix on Mon, 05/19/2014 - 07:09 Comment #11
Thanks you very much, is already solved the problem
Submitted by JamieCameron on Mon, 05/19/2014 - 12:20 Comment #12
Submitted by Issues on Mon, 06/02/2014 - 12:21 Comment #13
Automatically closed -- issue fixed for 2 weeks with no activity.