Site errors, sluggishness, and crashes
- Thread starter Mook
- Start date
Consistent 25-35% packet loss
Swapped the cable, changed to a different NIC, swapped ports on the switch.
problem persists.
This is driving me nuts.
Colo guys are saying it's nothing on their end.. say it might be a bad NIC. (server has one NIC with 4 ports)
however, when I ping within the rack, to or from any of the 8 servers. There's zero packet loss.
If I ping outside of the rack, to the gateway or any place beyond that.. there's 25-35% packet loss.
There's a single network cable coming into the rack.. and yet none of the other servers have issues at all.
not sure what else to do.
Colo guys are saying it's nothing on their end.. say it might be a bad NIC. (server has one NIC with 4 ports)
however, when I ping within the rack, to or from any of the 8 servers. There's zero packet loss.
If I ping outside of the rack, to the gateway or any place beyond that.. there's 25-35% packet loss.
There's a single network cable coming into the rack.. and yet none of the other servers have issues at all.
not sure what else to do.
as of 4:20 or so central, i'm not having any PL issues myself
Ping statistics for 104.25.171.17:
Packets: Sent = 107, Received = 107, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 27ms, Average = 15ms
site actually feels like it's being pretty normal for me right now too.
Ping statistics for 104.25.171.17:
Packets: Sent = 107, Received = 107, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 27ms, Average = 15ms
site actually feels like it's being pretty normal for me right now too.
Ping statistics for 104.25.171.17:
Packets: Sent = 574, Received = 574, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 496ms, Average = 32ms
so i poked around some more, sometimes felt normal, other times had odd slowsss. during the slows it didn't really seem to correlate with the higher ping times. i also got 2x error 522s.
https://support.cloudflare.com/hc/en-us/articles/200171906-Error-522-Connection-timed-out
i do see one of those causes is dropped packets on the host network, is db on a separate server and maybe there is a problem between them? my pings kept chooching along though, still zero lost. my traceroute:
Tracing route to thechicagogarage.com [104.25.170.17]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.16.1
2 17 ms 12 ms 13 ms 96.120.27.25
3 20 ms 23 ms 23 ms ge-111-0-0-33-sur03.homewood.il.chicago.comcast.net [68.86.185.105]
4 12 ms 12 ms 11 ms be-110-ar01.area4.il.chicago.comcast.net [68.86.184.253]
5 22 ms 31 ms 27 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
6 19 ms 14 ms 11 ms be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158]
7 12 ms 13 ms 10 ms 50.248.119.42
8 16 ms 14 ms 15 ms 104.25.170.17
Packets: Sent = 574, Received = 574, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 496ms, Average = 32ms
so i poked around some more, sometimes felt normal, other times had odd slowsss. during the slows it didn't really seem to correlate with the higher ping times. i also got 2x error 522s.
https://support.cloudflare.com/hc/en-us/articles/200171906-Error-522-Connection-timed-out
i do see one of those causes is dropped packets on the host network, is db on a separate server and maybe there is a problem between them? my pings kept chooching along though, still zero lost. my traceroute:
Tracing route to thechicagogarage.com [104.25.170.17]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.16.1
2 17 ms 12 ms 13 ms 96.120.27.25
3 20 ms 23 ms 23 ms ge-111-0-0-33-sur03.homewood.il.chicago.comcast.net [68.86.185.105]
4 12 ms 12 ms 11 ms be-110-ar01.area4.il.chicago.comcast.net [68.86.184.253]
5 22 ms 31 ms 27 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
6 19 ms 14 ms 11 ms be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158]
7 12 ms 13 ms 10 ms 50.248.119.42
8 16 ms 14 ms 15 ms 104.25.170.17
oh interesting i didn't realize that is how it worked. i suppose i thought something along the lines of my request hitting the core server but it then being able to direct assets from the cdn edge servers.
so if i'm in south africa i get a different ip for thechicagogarage.com? how does that actually work, that the dns resolves to this ip over here and that ip over there?
https://support.cloudflare.com/hc/en-us/articles/205177068-Step-1-How-does-Cloudflare-work-
If you’re really interested.
thanks, looks like that comes down to anycast https://www.incapsula.com/blog/how-anycast-works.html
which i was unfamiliar with. neat.
which i was unfamiliar with. neat.
Thread Info
-
Created -
83Replies
-
2KViews
-
Participants list
