Centos 5.5 32 bit, not pingable.

[RoelGellings]

Hello,

This night something wierds happend, when I came out of my bed the server was down, so I wen't to the control panel, but there seems everything to be fine.
Also I can use the console only at the controlpanel itselfs, it's like it doesnt accept connections from outside.
Since the fact that I didn't edited any settings this night at the server isn't it wierd that it suddenly get broken like this?
Well I have a screen shot of the netstat maybe somebody sees a problem? because I don't know that much about those things.

linuxbug.jpg

Thanks!.

[Irithori]

Hi and welcome

your gateway 159.253.5.1 is traceable, but shows packetloss for pings.

# traceroute 159.253.5.1
--snip--
..
--snap--
 4  xe-1-1-0.rt-decix-2.m-online.net (82.135.16.102)  14.369 ms  14.960 ms  15.685 ms
 5  tge1-3.fra01-1.eu.as5580.net (80.81.195.66)  18.800 ms  18.670 ms  19.151 ms
 6  tge2-2.fra02-1.eu.as5580.net (80.94.64.138)  20.102 ms  20.127 ms  16.247 ms
 7  78.152.44.89 (78.152.44.89)  22.653 ms  22.602 ms  22.927 ms
 8  tge2-2-22.edge1.Amsterdam1.as5580.net (78.152.44.62)  24.548 ms  21.749 ms  22.042 ms
 9  78.152.32.206 (78.152.32.206)  77.476 ms *  23.021 ms
10  159.253.5.1 (159.253.5.1)  29.261 ms * *


# ping 159.253.5.1
PING 159.253.5.1 (159.253.5.1) 56(84) bytes of data.
64 bytes from 159.253.5.1: icmp_req=16 ttl=57 time=24.0 ms
64 bytes from 159.253.5.1: icmp_req=17 ttl=57 time=23.6 ms
64 bytes from 159.253.5.1: icmp_req=21 ttl=57 time=22.9 ms
64 bytes from 159.253.5.1: icmp_req=22 ttl=57 time=25.9 ms
64 bytes from 159.253.5.1: icmp_req=24 ttl=57 time=25.1 ms
64 bytes from 159.253.5.1: icmp_req=26 ttl=57 time=23.7 ms
^C
--- 159.253.5.1 ping statistics ---
26 packets transmitted, 6 received, 76% packet loss, time 25011ms
rtt min/avg/max/mdev = 22.929/24.255/25.998/1.033 ms

Your host is not pingable, and the traceroute chokes

# traceroute 159.253.5.205
traceroute to 159.253.5.205 (159.253.5.205), 30 hops max, 60 byte packets
--snip--
..
--snap--
 4  xe-1-1-0.rt-decix-2.m-online.net (82.135.16.102)  16.507 ms  16.489 ms  17.839 ms
 5  tge1-3.fra01-1.eu.as5580.net (80.81.195.66)  23.730 ms  23.069 ms  23.492 ms
 6  * * *
 7  * * *
--repeats until:
30  * * *

Imho, the problem is with the routing before your host.
There is nothing for you to reconfigure or fix.

You should call your provider and open a ticket.

[RoelGellings]

Hi and welcome

your gateway 159.253.5.1 is traceable, but shows packetloss for pings.

# traceroute 159.253.5.1
--snip--
..
--snap--
 4  xe-1-1-0.rt-decix-2.m-online.net (82.135.16.102)  14.369 ms  14.960 ms  15.685 ms
 5  tge1-3.fra01-1.eu.as5580.net (80.81.195.66)  18.800 ms  18.670 ms  19.151 ms
 6  tge2-2.fra02-1.eu.as5580.net (80.94.64.138)  20.102 ms  20.127 ms  16.247 ms
 7  78.152.44.89 (78.152.44.89)  22.653 ms  22.602 ms  22.927 ms
 8  tge2-2-22.edge1.Amsterdam1.as5580.net (78.152.44.62)  24.548 ms  21.749 ms  22.042 ms
 9  78.152.32.206 (78.152.32.206)  77.476 ms *  23.021 ms
10  159.253.5.1 (159.253.5.1)  29.261 ms * *


# ping 159.253.5.1
PING 159.253.5.1 (159.253.5.1) 56(84) bytes of data.
64 bytes from 159.253.5.1: icmp_req=16 ttl=57 time=24.0 ms
64 bytes from 159.253.5.1: icmp_req=17 ttl=57 time=23.6 ms
64 bytes from 159.253.5.1: icmp_req=21 ttl=57 time=22.9 ms
64 bytes from 159.253.5.1: icmp_req=22 ttl=57 time=25.9 ms
64 bytes from 159.253.5.1: icmp_req=24 ttl=57 time=25.1 ms
64 bytes from 159.253.5.1: icmp_req=26 ttl=57 time=23.7 ms
^C
--- 159.253.5.1 ping statistics ---
26 packets transmitted, 6 received, 76% packet loss, time 25011ms
rtt min/avg/max/mdev = 22.929/24.255/25.998/1.033 ms

Your host is not pingable, and the traceroute chokes

# traceroute 159.253.5.205
traceroute to 159.253.5.205 (159.253.5.205), 30 hops max, 60 byte packets
--snip--
..
--snap--
 4  xe-1-1-0.rt-decix-2.m-online.net (82.135.16.102)  16.507 ms  16.489 ms  17.839 ms
 5  tge1-3.fra01-1.eu.as5580.net (80.81.195.66)  23.730 ms  23.069 ms  23.492 ms
 6  * * *
 7  * * *
--repeats until:
30  * * *

Imho, the problem is with the routing before your host.
There is nothing for you to reconfigure or fix.

You should call your provider and open a ticket.

Thanks, well ye I should contact the host company tomorrow, to tell then that I step over to a new one, because this is not the first issue...

[Irithori]

Hmm, what I can say is:
The peer of your provider is also involved.
Because the traceroute has problems long before it reaches you providers net.