0001919: New problems in build 1427. - SphereServer BugTracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001919

SphereServer

executable - linux build

public

24-02-11 18:58

23-04-11 20:23

Reporter

Mirravin

Assigned To

MrSugarCube

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

0.56c Nightly

Summary

0001919: New problems in build 1427.

Description

Have found in logs. Server not crashed.

Network:
DeadSocketTime=5
MaxPacketsPerTick=100
MaxPings=3500
MaxQueueSize=0
MaxSizePerTick=18000//12000//36000
NetTTL=300
UseAsyncNetwork=2
UsePacketPriority=1
UseExtraBuffer=1
TooltipMode=1
TooltipCache=0
AutoTooltipResend=0f

1)

06:26:WARNING:Forcing thread 'Main' to terminate...
06:26:CRITICAL:(data9.scp,5792)'Main' thread hang, restarting...
06:26:(data28.scp,1614)SERVER_TIMER: 2011/02/23 06:26:46
06:29:WARNING:Forcing thread 'Main' to terminate...
06:29:CRITICAL:'Main' thread hang, restarting...

[FUNCTION SERVER_TIMER]
...
SERV.LOG SERVER_TIMER: <SERV.RTIME>//this line
TIMERF 58,SERVER_TIMER
RETURN 1

2)

19:52:DEBUG:Receiving new connection
19:52:DEBUG:Retrieving IP history for 'IP1'.
19:52:DEBUG:Incoming connection from 'IP1' [blocked=0, ttl=300, pings=0, connecting=0, connected=0]
19:52:DEBUG:b6:Allocated slot for client (20).
19:52:DEBUG:b6:Clearing client state.
19:52:DEBUG:b6:Initialising client
19:52:b6:Client connected [Total:10] ('188.230.24.47' 1/1)
19:52:DEBUG:b6:Registering async client
19:52:DEBUG:b6:Opening network state
19:52:DEBUG:b6:Determining async mode
19:52:DEBUG:b6:State initialised, registering client instance.
19:52:DEBUG:b6:Client successfully initialised.
19:52:DEBUG:b6:Receiving new client login handshake.
19:52:DEBUG:b6:Client connected with a seed of 0xbce6182f (new handshake=1, seed length=20, received=4, version=0x56669443).
19:52:DEBUG:__ thread (3040234384) __ | # | _____ function _____________ | ticks passed from previous function start ______
19:52:DEBUG:>> 3040234384 | 0 | CServer::OnTick | +0
19:52:DEBUG:>> 3040234384 | 1 | CDataBase::OnTick | +8
19:52:DEBUG:>> 3040234384 | 2 | CServer::OnTick | +137984
19:52:DEBUG:>> 3040234384 | 3 | CDataBase::OnTick | +4
19:52:DEBUG:>> 3040234384 | 4 | NetworkIn::tick | +48331868 <-- exception catch point (below is guessed and could be incorrect!)
19:52:DEBUG:>> 3040234384 | 5 | ProfileData::Start | +1
19:52:CRITICAL:Assert pri=2:'iLen <= sizeof(bincopy)' file 'CClientLog.cpp', line 659, in NetworkIn::NetworkIn() #569 "messages - setup"
19:52:ERROR:b6:Bad Login 10 (Encryption error (packet length does not match what was expected))
19:52:DEBUG:b6:Client being closed by read-thread
19:52:DEBUG:b6:Flushing data for client.
19:52:DEBUG:b6:Client being closed by write-thread
19:52:DEBUG:b6:Client is being cleared since marked to close.
19:52:DEBUG:b6:Clearing client state.
19:52:b6:Client disconnected [Total:9] ('IP1')

Tags

No tags attached.

Nightly Version

Automated (specify build number)

Experimental Flags

NetworkOutThread

Option Flags

None

Internal Build Number

1427

Attached Files

Relationships

Notes
(0001029) Mirravin (reporter) 15-04-11 19:53	Both problems very rarely, but occur in Build: #1419 Linux, that I'm using now: 2) 18:52:DEBUG:Receiving new connection 18:52:DEBUG:Retrieving IP history for 'IP2'. 18:52:DEBUG:Incoming connection from 'IP2' [blocked=0, ttl=300, pings=0, connecting=0, connected=1] 18:52:DEBUG:bd:Allocated slot for client (18). 18:52:DEBUG:bd:Clearing client state. 18:52:DEBUG:bd:Initialising client 18:52:bd:Client connected [Total:9] ('IP2' 1/2) 18:52:DEBUG:bd:Registering async client 18:52:DEBUG:bd:Opening network state 18:52:DEBUG:bd:Determining async mode 18:52:DEBUG:bd:State initialised, registering client instance. 18:52:DEBUG:bd:Client successfully initialised. 18:52:DEBUG:bd:Receiving new client login handshake. 18:52:DEBUG:bd:Client connected with a seed of 0x4d5d1b41 (new handshake=1, seed length=20, received=4, version=0x86300000). 18:52:CRITICAL:Assert pri=2:'iLen <= sizeof(bincopy)' file 'CClientLog.cpp', line 659, in NetworkIn::NetworkIn() #588 "messages - setup" 18:52:ERROR:bd:Bad Login 10 (Encryption error (packet length does not match what was expected)) 18:52:DEBUG:bd:Client being closed by read-thread 18:52:DEBUG:bd:Flushing data for client. 18:52:DEBUG:bd:Client being closed by write-thread 18:52:DEBUG:bd:Client is being cleared since marked to close. 18:52:DEBUG:bd:Clearing client state. 18:52:bd:Client disconnected [Total:8] ('IP2')

(0001041) MrSugarCube (administrator) 23-04-11 05:01	The login error looks like it is caused by the client sending incomplete/corrupted/unexpected login data, do you know if there's a specific client version that causes it?

(0001042) MrSugarCube (administrator) 23-04-11 20:23	The error should be fixed in the next automated build anyway, although the client connection will be rejected because we don't know how to handle the data its sending (assuming it's valid) - I'd need to be able to reproduce it here to work out if it's something new we need to support. If the thread hang issue is still present in the latest automated build then please raise a separate report.

Issue History
Date Modified	Username	Field	Change
24-02-11 18:58	Mirravin	New Issue
15-04-11 19:53	Mirravin	Note Added: 0001029
23-04-11 05:01	MrSugarCube	Note Added: 0001041
23-04-11 20:23	MrSugarCube	Note Added: 0001042
23-04-11 20:23	MrSugarCube	Status	new => resolved
23-04-11 20:23	MrSugarCube	Fixed in Version	=> 0.56c Nightly
23-04-11 20:23	MrSugarCube	Resolution	open => fixed
23-04-11 20:23	MrSugarCube	Assigned To	=> MrSugarCube