Page 1 of 2

Services Stopped | httpd + nginx + named

Posted: Tue May 03, 2016 9:26 pm
by celsowebmax
Hi Guys...
I have one VPS with 02 IPs. One IP is to NS1 and other IP is to NS2.
Example:
ns1.xxx.xxx.xxx.88 and ns2.xxx.xxx.xxx.87

When I add the second IP and restart the VPS, all services are stopped. I receive this message below:

[Tue May 03 17:37:00 2016] [warn] NameVirtualHost xxx.xxx.xxx.87:8080 has no VirtualHosts
[Tue May 03 17:37:00 2016] [warn] NameVirtualHost xxx.xxx.xxx.87:8443 has no VirtualHosts
[Tue May 03 17:37:00 2016] [warn] NameVirtualHost xxx.xxx.xxx.88:8443 has no VirtualHosts
(99)Cannot assign requested address: make_sock: could not bind to address xxx.xxx.xxx.87:8080
no listening sockets available, shutting down Unable to open logs

Anybody can help me? I'm already in despair with this problem. Please any help me !
Thank in advance !!!

Re: Services Stopped | httpd + nginx + named

Posted: Tue May 03, 2016 10:40 pm
by ShaunWHD
Are you adding the IP manually or via VestaCP?

Re: Services Stopped | httpd + nginx + named

Posted: Tue May 03, 2016 10:56 pm
by celsowebmax
Via VestaCP. On IP list ( 8083/list/ip/)
After add, I reboot the vps and the services stopped.
Just back to work if I delete the IP.
As I said, I just need to add a second IP to point to ns2
What to do now?
Thank in advance

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:09 am
by ShaunWHD
You'll need to make sure your server interface is configured with the second IP also... open a SSH and type

Code: Select all

ifconfig
If your server is configured with two IP's, you should see something like eth0 and eth0:1 after the above command. Let me know.

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:15 am
by celsowebmax
This is result of ifconfig below:


[root@bkp ~]# ifconfig
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:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:76 errors:0 dropped:0 overruns:0 frame:0
TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9972 (9.7 KiB) TX bytes:12230 (11.9 KiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.69.89.88 P-t-P:192.69.89.88 Bcast:192.69.89.88 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

[root@bkp ~]#

On my SolusVM show 2 IPs
This is correct is ifconfig ?

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:20 am
by celsowebmax
This has given me so much headache that already formatted the vps again to try to install everything from scratch...

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:26 am
by ShaunWHD
Maybe, are the two IP's that you're trying to configure in VestaCP 127.0.0.1 and 192.69.89.88?

AFAIK, best practice is to have at least two public IPs to establish a name service. I've never tried to set it up with a private IP before but if so, i'm not sure if 127.0.0.1 would work. Could you try assigning another 192 ip?

An example of how I did my VestaCP installation:
1. Deploy VPS Instance
2. Install VestaCP
3. Configure VPS Interface with secondary public IP
4. Configure VestaCP with secondary IP

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:32 am
by celsowebmax
My IPs are:
192.*.*.88 - Primary
199.*.*.87 - Secondary
I think now no more how to fix. I have just got format the server.
I want to see if it will install and recognize the second IP ( 199.*.*.87 )

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:34 am
by celsowebmax
Drug....Arrghhhhhh
Error: yum install failed
And Now ?

Re: Services Stopped | httpd + nginx + named

Posted: Wed May 04, 2016 2:37 am
by ShaunWHD
what are you trying to yum install?
by the way, mask your public IP like this 199.*.*.* so spam bots and hackers don't get at it.