Page 1 of 1
Full debug analysis
Posted: Thu Aug 20, 2009 11:47 pm
by Pere
L2J Revision
Custom 
:
L2JDP Revision
Custom 
:
Well, these last weeks, my high rate server suffers mass DCs. I guess that this is on EnterWorld. People gets stucked on start screen and they simply do CTRL+ALT+SUPR to close the client.
The server doesn't log any nullpointer, only "XXX disconnected abnormally" almost every 5 seconds.
I can say too that I have 3 servers, and they are sharing the same l2jserver.jar file. Their only differences are on configs and datapack.
The high rate server is the most populated, but not too much more than the low one (and this NEVER suffered this problem).
2 days ago I enabled telnet, and today I could do a full debug while this problem was happening. Here we go:
http://94.23.16.191/Debug.txt
I know that you don't support custom cores, but it could be a huge favor.. I don't know how to analize these debugs >.<
Re: Full debug analysis
Posted: Fri Aug 21, 2009 12:28 am
by toastgodsupreme
Your abnormal disconnects may be caused by this:
viewtopic.php?f=81&t=11574
Re: Full debug analysis
Posted: Fri Aug 21, 2009 12:46 am
by Pere
No. This happens after a few online hours, normally on top hours. And then, until restart, anyone can enter.
Re: Full debug analysis
Posted: Fri Aug 21, 2009 1:13 am
by _DS_
Re: Full debug analysis
Posted: Fri Aug 21, 2009 2:09 pm
by Pere
Does this deadlock block the enterworld packets? :S
Re: Full debug analysis
Posted: Fri Aug 21, 2009 2:47 pm
by _DS_
If all threadpool already deadlocked - sure.
[3411]
Re: Full debug analysis
Posted: Fri Aug 21, 2009 5:01 pm
by Pere
I've updated this morning, let's see if it happens again ^^
Re: Full debug analysis
Posted: Fri Aug 21, 2009 9:05 pm
by e-KaOs
same for me and testing.
Re: Full debug analysis
Posted: Sat Aug 22, 2009 2:52 am
by Pere
It's working for now
Now I have another [private] support question (I don't want to open another topic for this, it's embarassing xD).
I have all the handlers on core (when you moved them on DP I didn't like it and reverted), and I guess that someday, while updating DP, I've updated the scripts without changing them on core.
Since then, on startup the server logs the following error 20-30 times: "Missing effectType for effect: Debuff".
What could it be in handlers?
Re: Full debug analysis
Posted: Sat Aug 22, 2009 5:11 am
by toastgodsupreme
Migi wrote:It's working for now
Now I have another [private] support question (I don't want to open another topic for this, it's embarassing xD).
I have all the handlers on core (when you moved them on DP I didn't like it and reverted), and I guess that someday, while updating DP, I've updated the scripts without changing them on core.
Since then, on startup the server logs the following error 20-30 times: "Missing effectType for effect: Debuff".
What could it be in handlers?
lol, time to move them out of the core
Honestly, it SUCKS having them dp side. Since a failure in one of the handlers (or scripts for that matter) typically breaks more than the one that failed (hey nBd, LOVE that "feature"

). And honestly, I've NEVER found a use to reloading handlers on my server. But meh, I won't go into that argument again. Really though, probably time to bite the bullet and do it.

I did the same thing as you but not for nearly as a long. I probably skipped that update for about 2 weeks until I sat down and did it all.
Re: Full debug analysis
Posted: Sat Aug 22, 2009 3:22 pm
by DrHouse
Is that error connected to handlers on DP?
http://www.l2jserver.com/trac/changeset/2983
How smart look your opinions about "handlers on DP suckzzz" now?

Re: Full debug analysis
Posted: Tue Aug 25, 2009 1:15 am
by Pere
Ok, changed to DP! Finally I can see errors and I'm able to see the differences between current revision and mine!! xD
Now I could see what happened with this and fix it, thanks house ^^