SphereServer BugTracker - SphereServer |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0001728 | SphereServer | executable - linux build | public | 07-03-10 14:56 | 24-09-10 02:54 |
|
Reporter | wuffel | |
Assigned To | MrSugarCube | |
Priority | high | Severity | block | Reproducibility | sometimes |
Status | closed | Resolution | unable to reproduce | |
Platform | | OS | | OS Version | |
Product Version | 0.56c Nightly | |
Target Version | | Fixed in Version | | |
Nightly Version | Not Available |
Experimental Flags | None |
Option Flags | None |
Internal Build Number | |
|
Summary | 0001728: After logout, account still loged in |
Description | 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 ;) |
Steps To Reproduce | |
Additional Information | Option flags: CommandSysmessages + OSIMultiSight + NoItemNaming + FloodPro
tection + Buffs + NoPrefix
Experimental flags: NetworkOutThread |
Tags | No tags attached. |
Relationships | related to | 0001710 | resolved | MrSugarCube | Server 'crash' at login sporadicly |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
07-03-10 14:56 | wuffel | New Issue | |
07-03-10 14:56 | wuffel | Nightly Version | => Not Available |
07-03-10 14:56 | wuffel | Experimental Flags | => None |
07-03-10 14:56 | wuffel | Option Flags | => None |
16-03-10 10:10 | MrSugarCube | Relationship added | related to 0001710 |
16-03-10 10:29 | MrSugarCube | Note Added: 0000410 | |
17-03-10 20:27 | wuffel | Note Added: 0000416 | |
18-03-10 08:39 | wuffel | Note Added: 0000417 | |
18-03-10 08:41 | wuffel | Note Edited: 0000417 | |
23-08-10 17:27 | MrSugarCube | Priority | normal => high |
25-08-10 15:49 | MrSugarCube | Note Added: 0000599 | |
25-08-10 15:49 | MrSugarCube | Note Edited: 0000599 | |
06-09-10 01:04 | MrSugarCube | Status | new => feedback |
15-09-10 01:18 | Incanus | Note Added: 0000626 | |
15-09-10 01:54 | MrSugarCube | Note Added: 0000629 | |
15-09-10 03:26 | Mirravin | Note Added: 0000632 | |
15-09-10 03:43 | Mirravin | Note Edited: 0000632 | bug_revision_view_page.php?bugnote_id=0000632#r6 |
18-09-10 23:50 | Mirravin | Note Added: 0000644 | |
20-09-10 08:45 | babidi | Note Added: 0000645 | |
20-09-10 09:57 | Mirravin | Note Added: 0000646 | |
20-09-10 16:32 | babidi | Note Added: 0000650 | |
24-09-10 02:54 | MrSugarCube | Note Added: 0000674 | |
24-09-10 02:54 | MrSugarCube | Status | feedback => closed |
24-09-10 02:54 | MrSugarCube | Assigned To | => MrSugarCube |
24-09-10 02:54 | MrSugarCube | Resolution | open => unable to reproduce |
14-11-10 19:54 | MrSugarCube | Category | executable - linux => executable - linux build |
Notes |
|
|
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)
|
|
|
|
Is this problem still present on the latest automated build?
|
|
|
|
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 |
|
|
|
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.
|
|
|
|
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? |
|
|
|
It is questions to author or to me? |
|
|
(0000650)
|
babidi
|
20-09-10 16:32
|
|
|
|
|
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. |
|