ATTENTION: Server Migration Tomorrow

Started by goate, May 16, 2017, 12:21:11 AM

Previous topic - Next topic

goate

QuoteI lag a lot, consistently, on the server, it's not my own connection. Definitely needs a change, you should complain to the host.

Already have, they're working on it, but we're not waiting around on them to fix it.

goate

= The server was migrated again on 2017-05-17 at 21:30 PM EST (2:30 AM GMT) =

Please post possibly related issues below.

Paha

Having ran a connection test period, it is at the least half of the old latency that I get (when we measure from europe) compared to previous migration, and it is stable without any losses so far in around 10 minute run. Seems better for sure.

Vlaid

Seems much better. Very few if any noticeable lag issues.
[url=https://www.efupw.com/forums/index.php?topic=706473.msg747918#msg747918]The Entirely True Legends of Velan Volandis[/url]

MessengerGirl

Much better here as well.  I have noticed occasional lag spikes but I got those on the old server, too.

goate

There have been two crashes since the move to the current server (about one every 24 hours or so).   I'll be trying a couple things to mitigate in the next 48 hours.

goate

Despite several attempts at mitigation, the server crashes are still happening.  I'll get back to crunching on them after the weekend.

Random_White_Guy

from like 1 AM to 5:44 AM CST (GMT -5) the server was crashing every 15-40 minutes regardless of the PCs online. An hour later it seemed to get worse as it dropped 6-10 minutes uptime then reset.
[11:23 PM] Howlando: Feel free LealWG
[11:23 PM] Howlando: I'll give you a high five + fist bump tip

[1:34 AM] BigOrcMan: RwG, a moment on the lips, forever on the hips

goate

Thanks;  Ironically this was likely caused by something I put in to try to stop the crashes.  That particular addition was removed at 8:50 AM CST today (1:50 PM GMT).

Spiffy Has

Every single time I take a quest, the server goes down. 8:27 AM EST on June 2nd 2017.

goate

Due to an oversight on my part the change that caused the constant reboots got re-applied.  It's persistently gone now.