All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
OpenVZ VPS connectivity issue
I got a VPS with one of the providers here (not going to name them for now since I don't want to turn this into a bashing thread, and it could be my fault as well). However I really hope someone could help me to point out where, if any, I did wrong, or if this is something that has to be fixed on the provider side:
Anyways, the issue right now is it does not respond to the outside ping:
ping 198.144.xxx.xxx
PING 198.144.xxx.xxx (198.144.xxx.xxx) 56(84) bytes of data.
^C
--- 198.144.xxx.xxx ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
ping google from the VPS does not return anything.
network is up:
service network status
Configured devices:
lo venet0
Currently active devices:
lo venet0
Stop the IP tables on the VPS with issue does not seem to help:
service iptables stop
iptables: Setting chains to policy ACCEPT: mangle filter na[ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
when I ping the VPS I still got 100% packet loss:
ping 198.144.xxx.xxx
PING 198.144.xxx.xxx (198.144.xxx.xxx) 56(84) bytes of data.
^C
--- 198.144.xxx.xxx ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms
Traceroute seem to be stuck halfway:
Traceroute seems to show it was stuck at somewhere halfway through (50.31.154.182):
7 ae12.cr2.ord6.us.scnet.net (204.93.xxx) 25.393 ms ae4.cr2.ord6.us.scnet.net (204.93.xxx) 25.320 ms 25.348 ms
8 72.ae2.ar1.ord6.us.scnet.net (204.93.xxx) 24.639 ms 24.748 ms 72.ae2.ar2.ord6.us.scnet.net (204.93.xxx) 25.414 ms
9 as36352.xe-1-0-2.ar1.ord6.us.scnet.net (50.31.xx) 25.759 ms as36352.xe-2-1-3.ar1.ord6.us.scnet.net (50.31.xxx) 26.085 ms as36352.xe-2-1-3.ar2.ord6.us.scnet.net (50.31.xxx) 26.893 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Interesting enough ping to the internal IPs are fine (108.174.xxx.xxx is the IP on the host):
ping 108.174.xxx.xxx
PING 108.174.xxx.xxx (108.174.xxx.xxx) 56(84) bytes of data.
64 bytes from 108.174.xxx.xxx: icmp_seq=1 ttl=64 time=0.064 ms
64 bytes from 108.174.xxx.xxx: icmp_seq=2 ttl=64 time=0.083 ms
64 bytes from 108.174.xxx.xxx: icmp_seq=3 ttl=64 time=0.077 ms
64 bytes from 108.174.xxx.xxx: icmp_seq=4 ttl=64 time=0.076 ms
64 bytes from 108.174.xxx.xxx: icmp_seq=5 ttl=64 time=0.080 ms
64 bytes from 108.174.xxx.xxx: icmp_seq=6 ttl=64 time=0.070 ms
--- 108.174.xxx.xxx ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5742ms
rtt min/avg/max/mdev = 0.064/0.075/0.083/0.006 ms
Resolver seem to be OK too:
cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 4.2.2.2
Shutting down and restarting network service seems to be fine as well:
service network stop
Shutting down interface venet0: [ OK ]
Shutting down loopback interface: [ OK ]
service network start
Bringing up loopback interface: [ OK ]
Bringing up interface venet0: Determining if ip address 198.144.xxx.xxx is already in use for device venet0...
Determining if ip address 198.144.178.38 is already in use for device venet0...
[ OK ]
The network configuration on my VPS looks pretty normal
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:16436 Metric:1
RX packets:10370 errors:0 dropped:0 overruns:0 frame:0
TX packets:10370 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1785425 (1.7 MiB) TX bytes:1785425 (1.7 MiB)
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:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:19435 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:504 (504.0 b) TX bytes:1328411 (1.2 MiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:198.144.xxx.xxx P-t-P:198.144.xxx.xxx Bcast:198.144.xxx.xxx Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:198.144.xxx.yy P-t-P:198.144.xxx.yy Bcast:198.144.xxx.yy Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
Any idea what might be the cause, this is a centOS VPS.
2.6.18-308.el5.028stab099.3 #1 SMP Wed Mar 7 15:56:00 MSK 2012 x86_64 x86_64 x86_64 GNU/Linux
Comments
Are you fearful of raising a ticket incase you get your service suspended/cancelled?
hmm I've seen that nick many times over somewhere before.......
Not sure if its related but you can have a look at this..
http://lowendtalk.com/discussion/comment/1017531/#Comment_1017531
Looks like an inbound,I'd be surprised if outbound can go that far but can't ping Google
That is correct, this is a traceroute from an external working VPS to this VPS which is having issue.
Nope, I have sent in the ticket but I was just worried it was something got to do with my configuration and the VPS is unmanaged.
probably null routed by your provider's network
Provider fixed it:
Thanks for everyone's help!
haha funny~~~