Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Help ! VPS Network Down.
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Help ! VPS Network Down.

yokowasisyokowasis Member
edited July 2017 in Help

Out of the blue, My VPS Networking is Down. I can not ping it. Neither the VPS Can Ping the inter (8.8.8.8).

It's OpenVZ. I have tried to reinstall the OS with to result.

I can however login using serial console.

Any idea how to debug and find what is the problem. I am using Centos 7. Since it doesn't have any internet connection, so obviously I can not install any fancy network tools.

And Yes, I have already opened the ticket. But it has been 20 hours. I figure I need something to help the Provider to find the problem so my problem can be solved faster. It has been down for 20 hours.

Thanked by 1DicShit
«1

Comments

  • DicShitDicShit Member

    Sad Story.

  • yokowasisyokowasis Member

    Just reinstall using debian

    root@racksx:/# 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.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:452 (452.0 B)  TX bytes:620 (620.0 B)

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

root@racksx:/#

    Anybody know what Does it mean ? is my VPS Doesn't get IP from DHCP Server ?

  • DicShitDicShit Member

    Wtf...

    How about this or this or this or this ?

    Or just search the Forum / Interwebz for tentacle porn a possible solution.

    Guess Yeti Scum Porn venet0 should yield some results!

  • WSSWSS Member
    edited July 2017

    Go into SolusVM and tell it to "Reconfigure networking". If it still doesn't work, you were probably null routed by your host for <reasons>.

    Thanked by 1vimalware
  • yokowasisyokowasis Member
    edited July 2017

    @WSS said:
    Go into SolusVM and tell it to "Reconfigure networking". If it still doesn't work, you were probably null routed by your host for <reasons>.

    Yeah already did that. No use. Contacted the provider, the CS asked me to reinstall using 32bit image. Not only it feels wrong, the provider doesn't provide any 32 bit image. If I was null routed for some reason, the support should tell me the reason right. All I do is just reinstall OS (almost everyday) to learn how to configure Nameserver. For some reason my nameservers can't work on this vps. In another VPS it works just fine.

    I will ask the CS whether I have been null routed or not.

    @DicShit said:
    Wtf...

    How about this or this or this or this ?

    Or just search the Forum / Interwebz for tentacle porn a possible solution.

    Guess Yeti Scum Porn venet0 should yield some results!

    Yeah I have totally no idea what to search. I don't even know what is the problem. is the problem because The Provider Cut My Internet, or Their image just simply broken, Or their network is down. That's why I am asking in this forum.

    Most of the time, the problem is solved just simply by reinstalling the OS.

  • robohostrobohost Member

    Try to set your ip manually

  • DicShitDicShit Member

    @yokowasis said:

    @WSS said:
    Go into SolusVM and tell it to "Reconfigure networking". If it still doesn't work, you were probably null routed by your host for <reasons>.

    Yeah already did that. No use. Contacted the provider, the CS asked me to reinstall using 32bit image. Not only it feels wrong, the provider doesn't provide any 32 bit image. If I was null routed for some reason, the support should tell me the reason right. All I do is just reinstall OS (almost everyday) to learn how to configure Nameserver.

    A great sign to fuck shit on the provider. Name and blame!

    Beside that, set them a reasonable due date in the ticket for solving this issue. If they do not reply or solve it in time, go the PayPal - route.

    If the provided Images do not work and you are not able to cum solve it with a reasonable amount of sweat effort, it is most likely their problem. Especially if it stopped working randomly.

    Note: Threatening or going the PayPal-route will most likely not end well.

  • MasonRMasonR Community Contributor

    @DicShit said: A great sign to fuck shit on the provider. Name and blame!

    OP already dropped the name :P

    yokowasis said: root@racksx

    Thanked by 1DicShit
  • DicShitDicShit Member

    So let the great shit start!

    @racksx

    Solve this cunt.

  • WSSWSS Member

    @yokowasis said:

    @WSS said:
    Go into SolusVM and tell it to "Reconfigure networking". If it still doesn't work, you were probably null routed by your host for <reasons>.

    Yeah already did that. No use. Contacted the provider, the CS asked me to reinstall using 32bit image. Not only it feels wrong, the provider doesn't provide any 32 bit image. If I was null routed for some reason, the support should tell me the reason right. All I do is just reinstall OS (almost everyday) to learn how to configure Nameserver. For some reason my nameservers can't work on this vps. In another VPS it works just fine.

    There's absolutely no reason to use a 32 vs 64bit these days- although people feel otherwise, I've found the 64 bit builds to have smaller binaries these days.

    If your IP shows OK under venet0:0, and you can't ping your gateway, it's probably null routed.

    Thanked by 1MasonR
  • TheLinuxBugTheLinuxBug Member

    @racksx Could you kindly stop by and help out your customer?

    Cheers!

  • yokowasisyokowasis Member

    I did not see that coming.

    @MasonR said:

    @DicShit said: A great sign to fuck shit on the provider. Name and blame!

    OP already dropped the name :P

    yokowasis said: root@racksx

    I don't want to be a dick and instantly rage blame anyone -yet- or worse paypal dispute. Let's heard the @racksx side of story. Surely there must be reason why my vps suddenly cease to work.

  • yokowasisyokowasis Member
    edited July 2017

    @WSS said:

    @yokowasis said:

    @WSS said:
    Go into SolusVM and tell it to "Reconfigure networking". If it still doesn't work, you were probably null routed by your host for <reasons>.

    Yeah already did that. No use. Contacted the provider, the CS asked me to reinstall using 32bit image. Not only it feels wrong, the provider doesn't provide any 32 bit image. If I was null routed for some reason, the support should tell me the reason right. All I do is just reinstall OS (almost everyday) to learn how to configure Nameserver. For some reason my nameservers can't work on this vps. In another VPS it works just fine.

    There's absolutely no reason to use a 32 vs 64bit these days- although people feel otherwise, I've found the 64 bit builds to have smaller binaries these days.

    If your IP shows OK under venet0:0, and you can't ping your gateway, it's probably null routed.

    How do I find the gateway ? is it using route ?

    root@racksx:/# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         *               0.0.0.0         U     0      0        0 venet0
root@racksx:/# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 venet0
root@racksx:/#

    This feels totally wrong.

    root@racksx:/# ip route
default dev venet0  scope link

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

    The vnet0:0 inet addr, P-t-P, and Bcast all shown the same IP (my vps IP).

  • blackjack4494blackjack4494 Member

    Maybe dhclient? Use man or google it there are many entries about it. Hope this will help. Good luck!

  • yokowasisyokowasis Member

    @blackjack4494 said:
    Maybe dhclient? Use man or google it there are many entries about it. Hope this will help. Good luck!

    Google Suggest using route.

    root@racksx:/# dhclient
-bash: dhclient: command not found
  • MasonRMasonR Community Contributor

    @yokowasis said: The vnet0:0 inet addr, P-t-P, and Bcast all shown the same IP (my vps IP).

    Looking at one of my VPS's it also shows the same IP for those three fields as well and has the same routing table output as you, so that's not an issue.

    The issue likely resides on the host-side not in your VM.

  • SaragoldfarbSaragoldfarb Member

    Maybe it's time to change hosts. Not sure what you're paying them but it's probably not worth the hassle.

  • yokowasisyokowasis Member

    @Saragoldfarb said:
    Maybe it's time to change hosts. Not sure what you're paying them but it's probably not worth the hassle.

    Yeah, Probably. But I will wait what they have to say first. If there is no response in ticket or this forum, then I'll find a better provider.

  • BlaZeBlaZe Member, Host Rep

    Your VM is not connected to the internet though it should be since I suppose you're not using a custom ISO but rather the template provided by the host.

    You'll manually need to configure your network (/etc/sysconfig/network-scripts/ifcfg-* for CentOS 6/7) with GATEWAY, IPADDR & subnet mask.

  • yokowasisyokowasis Member

    @BlaZe said:
    Your VM is not connected to the internet though it should be since I suppose you're not using a custom ISO but rather the template provided by the host.

    You'll manually need to configure your network (/etc/sysconfig/network-scripts/ifcfg-* for CentOS 6/7) with GATEWAY, IPADDR & subnet mask.

    I am still strugling finding what is my gateway IP. Google Suggest using route. But it seems that is not the case if using openvz.

  • DamianDamian Member
    edited July 2017

    BlaZe said: You'll manually need to configure your network (/etc/sysconfig/network-scripts/ifcfg-* for CentOS 6/7) with GATEWAY, IPADDR & subnet mask.

    Making adjustments to the network configuration on an OpenVZ VPS will result in a severely broken OpenVZ VPS.

    Most of the "suggestions" in this thread border on hilarious.

    If networking is not working inside the VM container on a brand new installation, there's absolutely nothing you can do about it from the VM container itself.

    If the host has truly suggested that reinstalling with a 32-bit OS template is going to solve the problem, take this as your hint that you should kindly ask for a refund (if you're within the host's refund policy) and look for a more competent host. Otherwise it's just going to end in heartache later.

    Thanked by 3MasonR DicShit Falzo
  • nicenice Member

    @yokowasis said:

    @BlaZe said:
    Your VM is not connected to the internet though it should be since I suppose you're not using a custom ISO but rather the template provided by the host.

    You'll manually need to configure your network (/etc/sysconfig/network-scripts/ifcfg-* for CentOS 6/7) with GATEWAY, IPADDR & subnet mask.

    I am still strugling finding what is my gateway IP. Google Suggest using route. But it seems that is not the case if using openvz.

    Really? You should ask that to your provider/hoster. Usually the gw is the first usable ip x.x.x.1

  • BlaZeBlaZe Member, Host Rep
    edited July 2017

    @Damian,
    Oh my bad, idk how I missed that it was OVZ. Apologies for the wrong guidance.

    @yokowasis,
    My reply is for KVM VPS & not OpenVZ, so ignore.

  • yokowasisyokowasis Member

    @nice said:

    @yokowasis said:

    @BlaZe said:
    Your VM is not connected to the internet though it should be since I suppose you're not using a custom ISO but rather the template provided by the host.

    You'll manually need to configure your network (/etc/sysconfig/network-scripts/ifcfg-* for CentOS 6/7) with GATEWAY, IPADDR & subnet mask.

    I am still strugling finding what is my gateway IP. Google Suggest using route. But it seems that is not the case if using openvz.

    Really? You should ask that to your provider/hoster. Usually the gw is the first usable ip x.x.x.1

    I don't think I can ask them anything at this time. Last reply I received from them is they ask me to reinstall using 32bit image and asked my root password.

    I have tried to ping the first x.x.x.1 and x.x.x.254. None of them responded.

  • SaragoldfarbSaragoldfarb Member

    @yokowasis said:

    @Saragoldfarb said:
    Maybe it's time to change hosts. Not sure what you're paying them but it's probably not worth the hassle.

    Yeah, Probably. But I will wait what they have to say first. If there is no response in ticket or this forum, then I'll find a better provider.

    Yeah probably. Not sure if this was your DNS VM but I'd suggest getting 2 vms from some more reputable hosts around here. Or if you're set on ovh go with them directly.

    On another note, if you want to treat your domains with some extra love concider using PowerDns/MariaDb instead of bind :)

  • mustafaramadhanmustafaramadhan Member

    Try change 'NM_CONTROLLED="no"' to 'NM_CONTROLLED="yes"' in '/etc/sysconfig/network-scripts/ifcfg-venet0:0' and then reboot.

  • yokowasisyokowasis Member

    @mustafaramadhan said:
    Try change 'NM_CONTROLLED="no"' to 'NM_CONTROLLED="yes"' in '/etc/sysconfig/network-scripts/ifcfg-venet0:0' and then reboot.

    You the creator kloxo-mr ?

  • mustafaramadhanmustafaramadhan Member

    @yokowasis said:

    @mustafaramadhan said:
    Try change 'NM_CONTROLLED="no"' to 'NM_CONTROLLED="yes"' in '/etc/sysconfig/network-scripts/ifcfg-venet0:0' and then reboot.

    You the creator kloxo-mr ?

    Yes.

  • yokowasisyokowasis Member

    Cool, Love your work man.

    @mustafaramadhan said:

    @yokowasis said:

    @mustafaramadhan said:
    Try change 'NM_CONTROLLED="no"' to 'NM_CONTROLLED="yes"' in '/etc/sysconfig/network-scripts/ifcfg-venet0:0' and then reboot.

    You the creator kloxo-mr ?

    Yes.

  • FalzoFalzo Member

    @racksx on vacation probably. His domain seems expired also...

    Thanked by 1MasonR
Sign In or Register to comment.