SphereServer BugTracker - SphereServer
View Issue Details
0001728SphereServerexecutable - linux buildpublic07-03-10 14:5624-09-10 02:54
wuffel 
MrSugarCube 
highblocksometimes
closedunable to reproduce 
0.56c Nightly 
 
Not Available
None
None
0001728: After logout, account still loged in
There is a curious problem in the last prelease. Client XY logged in normally and builds some stuff, and logged out afterwards. An hour later, XY tried to log in again - without any result. When i have a look in the sphere-console, the client were still connected. Only a sphere-restart fixed this problem. I dont find any log-reports for that issue - if i find out something new -> new commentary ;)
Option flags: CommandSysmessages + OSIMultiSight + NoItemNaming + FloodPro
tection + Buffs + NoPrefix
Experimental flags: NetworkOutThread
No tags attached.
related to 0001710resolved MrSugarCube Server 'crash' at login sporadicly 
Issue History
07-03-10 14:56wuffelNew Issue
07-03-10 14:56wuffelNightly Version => Not Available
07-03-10 14:56wuffelExperimental Flags => None
07-03-10 14:56wuffelOption Flags => None
16-03-10 10:10MrSugarCubeRelationship addedrelated to 0001710
16-03-10 10:29MrSugarCubeNote Added: 0000410
17-03-10 20:27wuffelNote Added: 0000416
18-03-10 08:39wuffelNote Added: 0000417
18-03-10 08:41wuffelNote Edited: 0000417
23-08-10 17:27MrSugarCubePrioritynormal => high
25-08-10 15:49MrSugarCubeNote Added: 0000599
25-08-10 15:49MrSugarCubeNote Edited: 0000599
06-09-10 01:04MrSugarCubeStatusnew => feedback
15-09-10 01:18IncanusNote Added: 0000626
15-09-10 01:54MrSugarCubeNote Added: 0000629
15-09-10 03:26MirravinNote Added: 0000632
15-09-10 03:43MirravinNote Edited: 0000632bug_revision_view_page.php?bugnote_id=0000632#r6
18-09-10 23:50MirravinNote Added: 0000644
20-09-10 08:45babidiNote Added: 0000645
20-09-10 09:57MirravinNote Added: 0000646
20-09-10 16:32babidiNote Added: 0000650
24-09-10 02:54MrSugarCubeNote Added: 0000674
24-09-10 02:54MrSugarCubeStatusfeedback => closed
24-09-10 02:54MrSugarCubeAssigned To => MrSugarCube
24-09-10 02:54MrSugarCubeResolutionopen => unable to reproduce
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build

Notes
(0000410)
MrSugarCube   
16-03-10 10:29   
Does this happen with all clients, or was it just in this one case?
(0000416)
wuffel   
17-03-10 20:27   
Hi!
New Report with the latest Nightly-build.

17:54:2:Client connected [Total:1] ('xx.xx.2.94' 1/1)
17:54:2: 'staff-fionn' bad password
17:54:ERROR:2:Bad Login 3 (The password entered is not correct)
17:54:2:Client disconnected [Total:0] ('xx.xx.2.94')
17:57:3:Client connected [Total:1] ('xx.xx.2.94' 1/1)
17:57:3:Login 'staff-fionn'
17:57:3:Client disconnected [Total:0] ('xx.xx.2.94')
17:57:4:Client connected [Total:1] ('xx.xx.2.94' 1/2)
sphereNightly: ../common/libev/ev.c:2128: ev_io_start: Assertion `("ev_io_start called
with negative fd", fd >= 0)' failed.

(onserver_timer.scp,2)GC: 196397 Objects accounted for
18:09:(onserver_timer.scp,2)World data saved (save/sphereworld.scp).
18:09:(onserver_timer.scp,2)Player data saved (save/spherechars.scp).
18:09:(onserver_timer.scp,2)Multi data saved (save/spheremultis.scp).
18:09:(onserver_timer.scp,2)Context data saved (save/spheredata.scp).
18:09:(onserver_timer.scp,2)World save completed, took 0.0000 seconds
18:09:(onserver_timer.scp,3)Statics data saved (save/spherestatics.scp).
?
Available Commands:
# = Immediate Save world (## to save both world and statics)
A = Accounts file update
B message = Broadcast a message
C = Clients List (1)
D = Dump data to external file (DA to dump areas)
E = Clear internal variables (like script profile)
G = Garbage collection
H = Hear all that is said (ON)
I = Information
L = Toggle log file (CLOSED)
P = Profile Info (OFF) (P# to dump to profiler_dump.txt)
R = Resync Pause
S = Secure mode toggle (ON)
T = List of active Threads
X = immediate exit of the server (X# to save world and statics before exit)
C
Currently there are no clients online
(0000417)
wuffel   
18-03-10 08:39   
(edited on: 18-03-10 08:41)
The last login is date back about 10 houres... And still one Client is connected ;)


C
Currently there are no clients online
?
Available Commands:
# = Immediate Save world (## to save both world and statics)
A = Accounts file update
B message = Broadcast a message
C = Clients List (1)
D = Dump data to external file (DA to dump areas)
E = Clear internal variables (like script profile)
G = Garbage collection
H = Hear all that is said (ON)
I = Information
L = Toggle log file (CLOSED)
P = Profile Info (OFF) (P# to dump to profiler_dump.txt)
R = Resync Pause
S = Secure mode toggle (ON)
T = List of active Threads
X = immediate exit of the server (X# to save world and statics before exit)

(0000599)
MrSugarCube   
25-08-10 15:49   
Is this problem still present on the latest automated build?

(0000626)
Incanus   
15-09-10 01:18   
This problem seems to be fixed. Our server ran build 1332 for 24 hours with up to 40 clients without running into this issue.

Build: 1332
OS: Windows
(0000629)
MrSugarCube   
15-09-10 01:54   
I think this might have been a linux-specific issue, so will need feedback from a linux user too.
(0000632)
Mirravin   
15-09-10 03:26   
(edited on: 15-09-10 03:43)
With 10-25 online I don't have complains from players on this(this problem have to block characters(already online)). So it is fixed, occurs very rarely or it is connected with specific option in ini.

(0000644)
Mirravin   
18-09-10 23:50   
Only one thing, I know: if you reset computer or lose internet connetion, your character will stays in game 5 minutes, until it will be disconnected as inactive socket. But I don't know, is it possible to improve this or not...
(0000645)
babidi   
20-09-10 08:45   
have ye modified
// How long logged out clients linger in seconds
ClientLinger=15

?

o maybe someone steal your password?
(0000646)
Mirravin   
20-09-10 09:57   
It is questions to author or to me?
(0000650)
babidi   
20-09-10 16:32   
ofcourse to author
(0000674)
MrSugarCube   
24-09-10 02:54   
I'll consider this issue closed for now since it doesn't seem anyone can reproduce it in recent builds.

Mirravin:
When a client suddenly loses connection it's normal for their character to stay online for 0001447:0000005 minutes. Setting a lower DeadSocketTime value in sphere.ini will reduce the length of time it takes for a connection to be considered dead.