Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Hello,

you should check your issue at any time from both directions.

Update: it's the network!

I'm running a cronjob that logs the default route and then does a traceroute to an external host.

2022-07-01 04:08:42 UTC: external ping monitor detected the VPS went offline
2022-07-01 11:03:13 UTC: VPS rebooted from control panel

Once it was back up and running, I examined the log.

Here's the last entry before it went offline:

Code: [Select]

2022-07-01, 04:05:01 UTC:

2a02:180:6:1::659 dev eth0 proto kernel metric 256 pref medium
fd78:232c:fe45:934b::1 dev eth0 metric 1024 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd78:232c:fe45:934b::1 dev eth0 metric 1024 pref medium

Start: 2022-07-01T04:05:01+0000
HOST: eu2                                                                                         Loss%   Snt   Last   A
vg  Best  Wrst StDev
  1. AS???    fd78:232c:fe45:934b::1                                                               0.0%    10    0.2   0.2   0.2   0.2   0.0
  2. AS35366  2a02-0180-0006-0001-0000-0000-0000-0001.blue.kundencontroller.de (2a02:180:6:1::     0.0%    10    3.3  24.6   0.7 178.3  54.6
  3. AS35366  po161.ipv6.bbsw-h2-j1a.as35366.net (2a02:180:6:9::6)                                 0.0%    10    3.4   6.3   0.8  38.0  11.4
  4. AS35366  po205.ipv6.bbsw-h4a-fra.as35366.net (2a02:180:6:7::16)                               0.0%    10   10.6  18.3   7.4  51.8  15.6
  5. AS174    2001:978:2:42::e8:1                                                                  0.0%    10   19.0  14.4   8.3  27.3   6.5
  6. AS174    te0-6-0-1.agr21.fra06.atlas.cogentco.com (2001:550:0:1000::9a19:175)                 0.0%    10   22.9  36.1   7.6 146.2  41.5
  7. AS174    multi-use.cogentco.com (2001:550:0:1000::8275:d)                                    80.0%    10    9.6  29.2   9.6  48.9  27.8
  8. AS174    be2846.ccr42.fra03.atlas.cogentco.com (2001:550:0:1000::9a36:251d)                  70.0%    10   19.0  12.6   8.6  19.0   5.6
  9. AS???    ???                                                                                 100.0    10    0.0   0.0   0.0   0.0   0.0
 10. AS174    be2154.rcr22.ams06.atlas.cogentco.com (2001:550:0:1000::8275:32ce)                  10.0%    10   22.7  24.9  15.6  48.0  10.4
 11. AS???    ???                                                                                 100.0    10    0.0   0.0   0.0   0.0   0.0
 12. AS12876  2001:bc8:400:100::b6                                                                70.0%    10   15.1  17.1  15.1  21.3   3.6
 13. AS12876  2001:bc8:1404:104::1                                                                 0.0%    10   16.0  33.5  16.0  87.7  21.8
 14. AS???    ???                                                                                 100.0    10    0.0   0.0   0.0   0.0   0.0
 15. AS12876  2001:bc8:1404:104::4                                                                 0.0%    10   23.1  27.6  15.2  71.0  18.1
 16. AS12876  2001:bc8:1830:201::1                                                                 0.0%    10   33.1  29.9  15.2  61.8  13.8

From then on, the log shows that the traceroute failed. This proves the VPS was powered on and running, but it had no network access. The network gateway was replying to pings, but not routing.

Code: [Select]

2022-07-01, 04:10:01 UTC:

2a02:180:6:1::659 dev eth0 proto kernel metric 256 pref medium
fd78:232c:fe45:934b::1 dev eth0 metric 1024 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd78:232c:fe45:934b::1 dev eth0 metric 1024 pref medium

Start: 2022-07-01T04:10:02+0000
HOST: eu2                             Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS???    fd78:232c:fe45:934b::1   0.0%    10    0.2   0.4   0.1   1.5   0.5
  2. AS???    ???                     100.0    10    0.0   0.0   0.0   0.0   0.0

Pretty conclusive that the problem is with the gateway, right?

2a02:180:6:1::659 has been terribly unreliable the last few weeks. Seems like I'm using the Server :: Webreboot to reboot it every day. Sometimes more often than that!

I'm nearly certain it's the host node that's the problem. I suspect it's overloaded.

My guest isn't heavily loaded at all. In comparison, we also have one of the original beta test instances (2a02:180:6:1::4a8) as well, running about the same mix of stuff, and it's not been nearly as much trouble.

I'd really appreciate it if someone would check the host and see what's going on with it.

Thanks!

The problem still exists. My VS becomes unreachable a few hours after each reboot.
Could someone please comment on why the routing does not work, what is the expected network configuration? Why can the /etc/network/interfaces shown above (2022-06-21_09-35-53.png) not be applied? I never touched this file, so it was pre-provisioned.
If the file should contain something else, please advise.
Thanks
 

It's the minimal system and I didn't install anything new.

[root@srv24271 ~]# top
top - 15:40:24 up  6:05,  1 user,  load average: 175.04, 171.10, 174.08
Tasks:  14 total,   1 running,  13 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  1000000 total,   934508 free,    22704 used,    42788 buff/cache
KiB Swap:  1000000 total,  1000000 free,        0 used.   977296 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                   
    1 root      20   0   43248   4992   3900 S   0.0  0.5   0:00.24 systemd                                   
   35 root      20   0   39092   8068   7780 S   0.0  0.8   0:00.86 systemd-journal                           
   50 root      20   0   42888   3264   2796 S   0.0  0.3   0:00.00 systemd-udevd                             
   60 root      20   0   21540   2772   2528 S   0.0  0.3   0:01.37 irqbalance                                 
   61 dbus      20   0   58136   4372   3856 S   0.0  0.4   0:00.06 dbus-daemon                               
   66 polkitd   20   0  612236  12712   9340 S   0.0  1.3   0:00.03 polkitd                                   
   67 root      20   0   26384   2948   2672 S   0.0  0.3   0:00.03 systemd-logind                             
   68 root      20   0  126284   3168   2548 S   0.0  0.3   0:00.01 crond                                     
   78 root      20   0  110104   2112   1984 S   0.0  0.2   0:00.00 agetty                                     
  280 root      20   0  112872   7584   6556 S   0.0  0.8   0:00.00 sshd                                       
  281 root      20   0  218544   6408   5508 S   0.0  0.6   0:00.89 rsyslogd                                   
  534 root      20   0  159416   9860   8488 S   0.0  1.0   0:00.05 sshd                                       
  536 root      20   0  115440   3472   3088 S   0.0  0.3   0:00.00 bash                                       
  554 root      20   0  161880   4444   3884 R   0.0  0.4   0:00.00 top

Hello,

I have rebooted your server, it works now fine.

You should do a reboot first before posting here. Additional you should check your configured services if they work with your assigned ressources and take care that you do not have any ressource shortage to bring a service down.

double request

my vServer 's ipv6 address is 2a02:0180:0006:0001:0000:0000:0000:49ca.
Customer ID: 13220732    Contract: 380325.

After the reinstallation, I didn't change anything. But it became unreachable .

Hello,

this server is installed atm with CentOS7 and is reachable with ICMP.

I am sad that it becomes unreachable again, just after the reinstallation and I didn't change anything,which means the new installed OS will became unreachable.

Hello,

this server is installed atm with CentOS7 and is reachable with ICMP.