Page 1 of 1
TessEQ2 - crashed, then can't login any char
Posted: Sat Jan 09, 2010 12:43 pm
by l333
Can anybody pls kick me from TessEQ2? (char name - Jennova, still shows as online on server status page)
I crashed while playing this character and after that i can't get past the character selection screen anymore - "There was an error that prohibited the server from letting you play...".
Tried to login from 2 different PCs - still the same error. The server is definitely online and alive - my friend can login and play with his account.
Re: TessEQ2 - crashed, then can't login any char
Posted: Sat Jan 09, 2010 2:52 pm
by John Adams
Putting TessEQ2 back in Debug mode. Apparently the world gets into some locked up state yet does not "crash", and then no one can connect. Maybe debug can show us what's happening.
Gonna need LE to look into it when it gets into that state. Crashes I can deal with. Mysterious lockups, I cannot troubleshoot.
Re: TessEQ2 - crashed, then can't login any char
Posted: Sat Jan 09, 2010 4:29 pm
by l333
The only thing I noticed before my crash was that all mobs stopped moving/attacking (I also wasn't able to attack). This actually happened right after I logged in.
Re: TessEQ2 - crashed, then can't login any char
Posted: Sat Jan 09, 2010 5:47 pm
by John Adams
Thanks for the update. Yeah, when everything stops moving/interacting, that's a sign the server is crashing or hit a deadlock. I was trying to run Tess in "release" mode vs slower "debug" mode, but apparently there are still some issues to discover.
Thanks for your bug reports. They are phenomenal

Re: TessEQ2 - crashed, then can't login any char
Posted: Sun Jan 10, 2010 11:05 am
by LethalEncounter
John, any deadlocks in the logs?
Re: TessEQ2 - crashed, then can't login any char
Posted: Sun Jan 10, 2010 11:11 am
by John Adams
I never see anything on the console screen, nothing suspicious. Just a long line of Auth statements, showing people trying to connect but getting rejected. That's usually when I know it's down. I think in Debug, it doesn't do that. Only in Release.
Re: TessEQ2 - crashed, then can't login any char
Posted: Sun Jan 10, 2010 11:12 am
by John Adams
Oh, haha.. right now, TessEQ2 has a deadlock and crash. If you would like to take a look before I reset it

Re: TessEQ2 - crashed, then can't login any char
Posted: Thu Jan 28, 2010 3:22 am
by l333
"There was an error that prohibited the server from letting you play..."
Deadlock again?
Re: TessEQ2 - crashed, then can't login any char
Posted: Thu Jan 28, 2010 7:48 am
by John Adams
No, she's running find. Had my last caller at 5:00am. Check my Server Stats page, last 10 callers.
Scratch that, something is definitely wrong. No more console output since Ochaim logged off at 5:50am, and a stuck Jennova character. I'll see if there are any updates, and put the server back in Debug for the next few days. Thanks for the heads up, I wouldn't have known otherwise.
That's all we need, a server that just stops working but doesn't crash. Weeee!
Re: TessEQ2 - crashed, then can't login any char
Posted: Thu Jan 28, 2010 10:05 am
by l333
In case it (somehow) helps:
right before the crash I've experienced the following bug: i was able to duplicate the amount of some stuff in my bags (i guess i could have done it with any resources stack, i've just stopped after 10 or so) --> dragging and dropping resources stack to another slot in inventory resulted not in "moving" item BUT in "copying" it. Then i moved 1st stack to another slot, then i merged 2 identical stacks and got 2x amount of original one. I've tried this only with harvested resources. After I re-logged to try this with another char's inventory the server crashed.
The bug is gone after server restart and I can't reproduce it. (i still have that 2x amount of some resources in my inventory)
Re: TessEQ2 - crashed, then can't login any char
Posted: Thu Jan 28, 2010 11:00 am
by John Adams
Remember, the server (Tess) is occasionally in "debug mode", which as far as I am concerned, runs a lot slower because it's sniffing for issues. In this, it is possible you moving stacks faster than the server was updating might have caused the initial issue. Now that the server is running debug/slower, maybe you are not seeing the effect?
Just a guess, but me and Debug mode do not like each other much.