SphereServer BugTracker - SphereServer
View Issue Details
0001822SphereServerexecutable - linux buildpublic21-09-10 18:4225-10-10 23:28
Mirravin 
MrSugarCube 
normalminorhave not tried
resolvedfixed 
 
0.56c Nightly 
Automated (specify build number)
None
None
1333
0001822: CRITICAL: skill < COUNTOF(m_SkillLock)
14:48:WARNING:92:Unknown game packet (0x14) received.
14:48:WARNING:92:Unknown game packet (0xdb) received.
14:48:CRITICAL:Assert pri=2:'skill < COUNTOF(m_SkillLock)' file 'CCharNPC.cpp', line 253, in SUB: NetworkIn::Network::ProcessMessage() #0 ""
14:48:DEBUG:92:Parsing Packet len=12 id=0x14 [2010/09/20 14:48:42]
        0 1 2 3 4 5 6 7 8 9 A B C D E F
       -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 14 db 3a 7e 54 c3 2f 19 fd f7 79 40 ..:~T./...y@
14:48:ERROR:92:Setup_CreateDialog acct='retry' already online!

Sphere NOT crashed.
Harm not detected.

Experimental=01|08|010000|0800000
OptionFlags=08|0200|080|02000

You can see the old example here:
http://tracker.sphere.torfo.org/bugs/view.php?id=1710#c479 [^]
No tags attached.
Issue History
21-09-10 18:42MirravinNew Issue
21-09-10 18:50MirravinNote Added: 0000656
24-09-10 08:55MirravinNote Added: 0000676
24-09-10 09:13MirravinNote Added: 0000677
24-09-10 09:14MirravinNote Edited: 0000677bug_revision_view_page.php?bugnote_id=0000677#r29
24-09-10 09:17MirravinNote Edited: 0000677bug_revision_view_page.php?bugnote_id=0000677#r30
24-09-10 11:33MrSugarCubeNote Added: 0000678
25-09-10 00:56MirravinNote Added: 0000679
25-09-10 00:58MirravinNote Edited: 0000679bug_revision_view_page.php?bugnote_id=0000679#r32
25-09-10 00:58MirravinNote Edited: 0000679bug_revision_view_page.php?bugnote_id=0000679#r33
04-10-10 03:42MrSugarCubeNote Added: 0000685
25-10-10 23:28MrSugarCubeStatusnew => resolved
25-10-10 23:28MrSugarCubeFixed in Version => 0.56c Nightly
25-10-10 23:28MrSugarCubeResolutionopen => fixed
25-10-10 23:28MrSugarCubeAssigned To => MrSugarCube
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build

Notes
(0000656)
Mirravin   
21-09-10 18:50   
UseAsyncNetwork=0
UsePacketPriority=1
(0000676)
Mirravin   
24-09-10 08:55   
03:53:WARNING:3a:Unknown game packet (0x2e) received.
03:53:CRITICAL:Assert pri=2:'skill < COUNTOF(m_SkillLock)' file 'CCharNPC.cpp', line 253, in SUB: NetworkIn::Network::ProcessMessage() #0 ""
03:53:DEBUG:3a:Parsing Packet len=46 id=0x2e [2010/09/24 03:53:43]
        0 1 2 3 4 5 6 7 8 9 A B C D E F
       -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 2e 3a 3d f2 ac df 5e 04 c9 ba c3 e9 00 00 00 00 .:=...^.........
0010 00 00 00 00 00 00 00 b1 00 17 00 04 fb 78 00 00 .............x..
0020 04 43 00 00 00 00 00 00 00 00 00 00 00 00 .C............
(0000677)
Mirravin   
24-09-10 09:13   
(edited on: 24-09-10 09:17)
I think - the reason of this errors is working(ProcessMessage ?) with packets, what's can't be sent with client(why sphere receive its, I don't know). Sphere receive packet 0xdb, 0x2e etc., what is server-only packets. What is the sense to work with its, and get errors?

(0000678)
MrSugarCube   
24-09-10 11:33   
The error is caused by the client sending data that Sphere doesn't understand (or Sphere isn't reading a certain packet correctly, possibly a previous packet where the full length isn't being read).

Since it doesn't know what '0x2e' is (or '0x14' and '0xdb' in the original example), it keeps skipping bytes until it finds something it thinks it recognises (the '0x3a') and tries to continue from there.

A packet log might help to identify which packets were sent just before the error occurred.
(0000679)
Mirravin   
25-09-10 00:56   
(edited on: 25-09-10 00:58)
Can anyone open this issue? http://tracker.sphere.torfo.org/bugs/view.php?id=1823 [^] Because I can see Fatal Bugtracker error only.
Or I need to write this all again?
There I write about the reasons of these errors or of a part of them...

(0000685)
MrSugarCube   
04-10-10 03:42   
Is this still reproducable on the latest automated build? (if yes, then a packet log still seems to be the best chance for us to see what's going wrong).

For some reason your other report wasn't posted correctly, so you'll need to submit it again.