kvothe, ~8 minute connection down pattern

[Himeko]

8.47 PM GMT, vps has again lost connectivity, ping etc all timeout. this is happening a few times a day. yesterday twice as well.

[Himeko]

now it's back 8.55 PM. same pattern as usual.

[Himeko]

I've been monitoring my node closely, and there's this pattern reoccurring a few times a day: the server -connection- goes down. The VPS keeps running during this time, after connection is back, Apache doesnt show signs of any reboot, no services had errors, nothing, and I get emails from my crons that -were running- during the outage: their message is clear, they couldn't access the outside, couldnt load any address, which exposes the problem to be a connectivity issue with the node.

But this is a clear pattern now, every time it lasts -exactly around 8-9 minutes.

What's going on?

[Ron]

Run traceroutes while it's down and send them to support in a ticket.

[Himeko]

Will do, but it's down also for my customers in very different geographical locations. In fact it's down even from within the server, because the cron jobs have no internet access when this happens, I get the email reports from them after connection is back that they couldn't access the net.

<b>Cerberus</b> [Errno: 2]: fsockopen(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in <b>/home/*/public_html/support/cerberus-api/pop3/cer_Pop3.class.php</b> at line <b>238</b>.<br>

Looking up *
Unable to locate remote host *
Alert!: Unable to connect to remote host.

(url removed)

that's from within the server itself.

[Ron]

Ahhhh. Well,m the tracerotues help identify the problem even near/around the server and network, and help to rule out your connection route.

That said, I've seen they are having serious name-server issues all day, that might be your issue.

[Frank Broughton]

I've been monitoring my node closely, and there's this pattern reoccurring a few times a day: the server -connection- goes down. The VPS keeps running during this time, after connection is back, Apache doesnt show signs of any reboot, no services had errors, nothing, and I get emails from my crons that -were running- during the outage: their message is clear, they couldn't access the outside, couldnt load any address, which exposes the problem to be a connectivity issue with the node.

But this is a clear pattern now, every time it lasts -exactly around 8-9 minutes.

What's going on?

Is your node using openVZ?

[Himeko]

SolusVM. The machine always appears as "online" during the outage.

[Frank Broughton]

I asked cause there was an openvz bug that did just what is happening to you.

[Ron]

try reaching it directly by IP address during the outage.
With SSH and with a browser with an IP instead of the domain name.

That might be instructive.

[Himeko]

IP times out during the outage, I'm actively monitoring it pinging the main IP.

[JPC-Bilal]

I've been monitoring my node closely, and there's this pattern reoccurring a few times a day: the server -connection- goes down. The VPS keeps running during this time, after connection is back, Apache doesnt show signs of any reboot, no services had errors, nothing, and I get emails from my crons that -were running- during the outage: their message is clear, they couldn't access the outside, couldnt load any address, which exposes the problem to be a connectivity issue with the node.

But this is a clear pattern now, every time it lasts -exactly around 8-9 minutes.

What's going on?

Hi Himeko,

We are sorry to hear that you are facing this issue. In order to investigate please submit a ticket if you have not already done so that techs can look into this issue. Thank you.

[Himeko]

Hi Himeko,

We are sorry to hear that you are facing this issue. In order to investigate please submit a ticket if you have not already done so that techs can look into this issue. Thank you.

[JPC-Bilal]

I am checking this ticket and will update you there shortly. Please follow up there. Thank you.

[Himeko]

It's down right now again, for the 3rd time today.

8.27 AM GMT - 8.41 AM GMT
12.16 AM GMT - 12.17 AM GMT
12.30 AM GMT - ... (still down)

6 44 ms 43 ms 44 ms xe-5-0-0-0.mad-001-score-2-re1.interoute.net [212.23.53.89]
7 70 ms 68 ms 69 ms ae0-0.mad-001-score-1-re1.interoute.net [89.202.161.17]
8 61 ms 61 ms 61 ms ae3-0.par-gar-score-1-re0.interoute.net [89.202.161.22]
9 67 ms 67 ms 67 ms ae1-0.lon-004-score-1-re0.interoute.net [212.23.42.22]
10 76 ms 72 ms 72 ms xe-0-3-0.cr1.lhr1.uk.nlayer.net [195.66.224.37]
11 70 ms 71 ms 70 ms ae2-70g.cr1.lhr1.uk.nlayer.net [69.22.139.62]
12 143 ms 152 ms 142 ms xe-7-2-0.cr1.nyc2.us.nlayer.net [69.22.142.62]
13 155 ms 156 ms 156 ms xe-4-3-1.cr1.atl1.us.nlayer.net [69.22.142.14]
14 153 ms 153 ms 154 ms ae1-40g.ar1.atl1.us.nlayer.net [69.31.135.130]
15 304 ms 223 ms 205 ms as16626.xe-2-0-5-102.ar1.atl1.us.nlayer.net [69.31.135.46]
16 166 ms 156 ms 156 ms core-gi1-4.nocdirect.com [207.210.95.134]
17 155 ms 155 ms 155 ms kvothe.nocdirect.com [209.217.243.130]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.