there seems to be currently a problem with the lobby server, i personally got a "Bad username/password" while i didn't touch my springlobby settings.

some other users seems to be affected, too...

it seems like aegis is already investigating....

the same

Aegis migrated accounts to mysql, but something went wrong.

Going down for restart?

why was there no announce? (+ still thumbs up for migrating to sql, but something seems broken :-/)

for me, it looks similar to the error that happened after the restart, something like logged in users when server went down couldn't re-login.

No heads up and "live testing" is indeed somewhat ridiculous.

yeah, thats bad, but last time licho restarted the server something similar happened...

Why are there no backup servers anymore? We used to have two.

there are backupservers... but for example they are useless when i want to talk to a specific person who is on a different server...

Backup servers dont work for me either,

There should be one backup server that is always up. Doesn't even need the same level of capability as the main server, so long as it can serve as even a basic IRC it's worth it.

I agree that when we had two backup servers it was a bit silly, but still better than zero.

lobby.zydox.se:8200 / #sy seems to work.. but only 3 users there :D (server is in lan-mode, means no password / accounts)

"real backup" for me is the irc-channel...(irc.quakenet.org in #sy)

as most of you have noticed, it should be fixed now...

afaik the cause was, aegis tried to migrate to sql but something failed and he had to switch back... next time it hopefully works...

Problem wasnt caused by aegis or SQL migration, that was just speculation. It is fixed now. All accounts should be working.

then licho: shame on you for spreading miss-information here


still thumbs up for the sql migration! :D

it can't get worse than with a plain text file...


[topic closed i would say...]

Well indirectly was because it freezed during migration and after restart some accounts were gone :)

It was partly my fault partly SL fault (sending invalid id in login message)