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

› › Unresponsive Openvz Vps
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.

Unresponsive Openvz Vps

dspblackdspblack Member
in General

So here's my story. I have an Openvz vps running Centos 6 from nodeserv. I rented it as a backup server. Since the past week it has stopped responding and I cannot login via ssh or ftp using the server IP. Funny thing is Solusvm says the server is online, alive and kicking and I can ssh into the server using the Solusvm serial console credentials but that is all I've got for the moment. I cannot ping to any ip from the vps either. Steps I've taken so far in vain:

  1. Rebooted the vps.
  2. Reconfigured Networking via Solusvm.
  3. Disabled iptables and csf.
  4. Submitted a ticket to the provider with no response.

I've got some backup files there and I've tried to scp, sftp etc. using the Solusvm console IP and username but it didn't work. The problem probably is network-related but is there any way I can get around this and download my backup files?

Comments

  • GamerTech24GamerTech24 Member

    So the VPS has no network connectivity at all? Basically cut off from the internet?

    This is a hard one, I'm not entirely sure, at least you have serial console access

  • dspblackdspblack Member
    edited March 2017

    Yes it looks like it because it cannot ping to any ip from within (Pinging to the server ip from multiple locations doesn't work either).

  • nullnotherenullnothere Member

    I have a VPS with NodeServ and I've just had one problem after another for a long time (after Jade left, around the time it was acquired).

    In all probability the routing is all messed up and they'll have to assign new IPs for your VPS. Reach out via ticket to get it sorted out.

    I suspect that it is also no longer in Jacksonville (in my case I've been moved to Seattle).

    Currently IPv4 and/or IPv6 is broken intermittently as well. It's pretty much an unusable VPS (and it has been unusable for over 4 months now because of horrible IO when it was in Jacksonville).

    See: https://www.lowendtalk.com/discussion/comment/2109102/#Comment_2109102

    Thanked by 1dspblack
  • stefemanstefeman Member
    edited March 2017

    Show us ifconfig and whats in the /etc/network/interfaces

  • dspblackdspblack Member
    edited March 2017

    @stefeman said:
    Show us ifconfig and whats in the /etc/network/interfaces

    ipconfig
    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:104 errors:0 dropped:0 overruns:0 frame:0
    TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:8312 (8.1 KiB) TX bytes:8312 (8.1 KiB)

    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:900 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1876 errors:0 dropped:271 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:53229 (51.9 KiB) TX bytes:109762 (107.1 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:107.155.188.xxx P-t-P:107.155.188.xxx Bcast:107.155.188.xxx Mask:255.255.255.255
    UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

    ifcfg-venet0
    DEVICE=venet0
    BOOTPROTO=static
    ONBOOT=yes
    ARPCHECK="no"
    IPADDR=127.0.0.1
    NETMASK=255.255.255.255
    BROADCAST=0.0.0.0
    ARPCHECK="no"
    IPV6INIT="yes"

    ifcfg-venet0:0
    DEVICE=venet0:0
    ONBOOT=yes
    ARPCHECK="no"
    IPADDR=107.155.188.xxx
    NETMASK=255.255.255.255

    Masked the last ip4 address with xxx.

  • stefemanstefeman Member
    edited March 2017

    Whats ur /etc/network/interfaces

    nano and paste that here.

  • dspblackdspblack Member
    edited March 2017

    @stefeman said:
    Whats ur /etc/network/interfaces

    No such file or directory. This is on Centos 6. Or am i missing something? I have /etc/sysconfig/network-scripts/

  • stefemanstefeman Member
    edited March 2017

    Ah.

    Well, ifconfig looks normal to me.. at least I can't spot anything too odd.. venet0:0 is your adapter and it seems to be enabled.

    Thanked by 1dspblack
  • doughmanesdoughmanes Member

    /etc/resolv.conf?

  • AnthonySmithAnthonySmith Member, Patron Provider

    Sounds like you have been null routed, can you even ping the gateway?

    Thanked by 1doughmanes
  • IshaqIshaq Member

    I've pinged a couple of IPs on that subnet and they reply including the possible gateway (107.155.188.1)

  • RadiRadi Host Rep, Veteran

    @AnthonySmith beat me to it. It's nullrouted.

  • dspblackdspblack Member
    edited March 2017

    @doughmanes said:

    /etc/resolv.conf?

    Generated by NetworkManager
    search mydomain.com
    No nameservers found; try putting DNS servers into your
    ifcfg files in /etc/sysconfig/network-scripts like so:
    #
    DNS1=xxx.xxx.xxx.xxx
    DNS2=xxx.xxx.xxx.xxx
    DOMAIN=lab.foo.com bar.foo.com

    There is a # before every line and yes I cannot ping the 'possible gateway'. Anyway, it baffles me that someone would target a backup server and have the provider nullroute the ip :)

    Anyway, thank ya all for chippin in.

  • goodservgoodserv Member

    Did you solved the problem please ? i have similar problem, did you got any answer from the support ?

Sign In or Register to comment.