Login problem after Popham crash

[aageldof]

While wandering in Popham yesterday the server crashed (ended) and of course I couldn't log in anymore. But what is bothering: also my alts in Providence were not reachable anymore... Restarts and emptying caches did not help. Did anyone experience a similar problem? (and found any solution?)

[lachlaan]

Oh yeah, I remember this. When one server would crash the character, as well as the account would count as still online, for lack of any updated data due to the crash. Sadly this won't take forever to fix. Perhaps try to make a new character see if that unclogs the pipes and changes your account's log-in status.

Edit : Yeah had to check some older posts, seems that when one of the old servers went down the account was still flagged as offline to the other servers, so you might be stuck until JC processes the data manually and purges all the logins, or forces them offline or whatever magic he does.

[TotalyMeow]

you might be stuck until JC processes the data manually and purges all the logins, or forces them offline or whatever magic he does.

Indeed, this is probably the case.

[aageldof]

OK - thnx for your reaction. I hope this can and will be corrected.

[TotalyMeow]

It can and it will be soon.

[lachlaan]

OK - thnx for your reaction. I hope this can and will be corrected.

It can, it will, give it time as it needs to be done manually and JC is also processing the popham data for whatever he needs to hand out prizes, and possibly statistics for his own benefit to see how to set the parameters of the next expedition. But it's definitely fixable meanwhile perhaps play some alt account and farm charms

Edit: darn it meow beat me to it xD with the same phrasing too

[Jennyferi]

What about this feature on Latikai's client:


Doesn't it help or am i wrong?

[lachlaan]

Help with what?

The issue is that the server probably has an SQL table of accounts and characters and it likely only ever changes the "online" status of an account when it stops getting data from a client logged on that account, or when the server process is running and shuts down properly thus iterating through all "account" SQL entries and setting them all to offline. Alternatively JC can do it manually, but as it stands popham's process just isn't working, and when it stopped it wasn't set to cycle through all the stuff it should've done on a normal shutdown, instead it just killed the process to preserve it in time so JC can peep on it.