Zorcon Issues (Valrona Stopped)

[Guest]

[History] [Commands]

[August 03, 2010, 01:25:24 PM] caio_566: quando entro no jogo e coloco minha senha o jogo diz que ela não existe 

[August 19, 2010, 01:34:10 PM] liviaJB95: eu ja ativei minha conta e ojogodiz que não existe

[August 24, 2010, 01:03:01 AM] aip2010: 2010aip

[August 24, 2010, 01:00:48 PM] thamiel: eu aida naum sei kkkkkk

[August 28, 2010, 12:25:52 PM] gaby: como faço para jogar?

[August 28, 2010, 12:26:10 PM] gaby: pq coloco minha senha mas n pega

[Breosa]

Hello, As noted in the Zorcon forum, Zorcon has crashed and backups are not working after February 1st. To try and prevent any issues with Valrona, Valrona has been stopped, gracefully I hope whilst investigations continue.

As soon as I have news I will update.

[Breosa]

The plan at this point it to make a full backup of Valrona as it stands today. Valrona appears to be complete and the Model Server can be started. Once the backup of Valrona is complete I'll restart the planet. (Backup is another 20mins or so to go)

Zorcon will indeed have to be rolled back to Feb 1st. I've not been able to find a reason why the backups don't work despite trying various different approaches, debug code etc. It appears as though the data within the backups is corrupt. Companies don't load cleanly, the connection to the Mail server doesn't work. So there are too many issues to try and fix "quickly".

I am looking at ways to restart the Model Server automatically at intervals but because there are two planets on the same server additional code changes are going to be required to make the Model Server save AND restart by itself without trying to automatically restart the other planet which is already running. So stay tuned on that one.

In the meantime, we will have to move to a manual restart at intervals to ensure that we can continue to move the game forward.

[Breosa]

Zorcon is back from Feb 1st, Valrona has been restarted as well.

The backup corruption goes back prior to Feb 1st. The daily backups from the "running" backups also won't load so whatever is causing it has been there for quite sometime :-(