Source Code Project Mantis - FSSCP
View Issue Details
0001081FSSCPmultiplayerpublic2006-10-03 16:142007-10-17 21:28
Assigned Totaylor 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.6.10 
Summary0001081: Standalone server disappear from list over time
DescriptionLeaving a standalone server up over a period of time results in its eventual disappearace from the list of available servers. This occurs on both the FS2netD list and the actual game list. Almos always happens unless the server crashes for other reasons.
Additional InformationNo errors are reported but I do notice in the multi.log file that eventually the server quits receiving the pong from the server. I am uploading 2 files containing the logs and config files from each server I left up last night. This was also with the 3.6.9 rc7do8 but was also a problem in 1.3.6. Only other thing I noticed is that when this happens sometimes it leaves a copy of fs2 running in memory on XP.
TagsNo tags attached.
Attached Filesrar Media-10-03-06.rar (103,845) 2006-10-03 16:14
rar P3-866-10-03-06.rar (112,177) 2006-10-03 16:15
rar P3-866-10-05-06.rar (328,869) 2006-10-05 15:58
rar Media-10-05-06.rar (107,256) 2006-10-05 15:58
txt dsl.txt (3,469) 2006-10-05 18:28

2006-10-03 22:48   
The FS2NetD server was restarted in the morning, so that's probably why it dropped you offline then (the times from you log appear to match up).

You have said that this happens at other times as well though correct? I'll need logs from another session in which the server didn't go offline in order to try and track this down (I need logs from both sides, but with the server down it obviously wasn't logging at the time).
2006-10-04 11:56   
Ok, think I can get this worked out on a real case. I added some code to make sure that a pong is received within 2 minutes of a ping being sent. If it doesn't get the pong then the connection is assumed to be dead and it is reset. If it still can't connect then it gives an error popup (but not with a standalone server) and then FS2NetD support is disabled until you try to reconnect (either by restarting the standalone server in that case, or exiting back to the mainhall and then going back in).

This condition (that the connection was dropped, was or wasn't restored) is logged to the multi log too.

For now this is in the new FS2NetD code that I'm working on. Not sure when this will be in a testable build but I'll leave this bug open until then at least.
2006-10-04 17:20   
That'll be a great-to-have - obviously it will mean that standalones will be able to run more resiliently without needed monitoring & restarting.

If you need another log from such a case, I have one from today. But it sounded like you didn't need more...
2006-10-05 16:26   
(Last edited: 2006-10-05 16:27)
In the new set of logs (@FUBAR) the server registered you as logging off at the time the connection to the server appears to have dropped in your logs. This is on IP

On IP the same thing happened at the exact same time. For this IP it has you logging back on at around 16:05 (GMT-6).

Neither set of logs gives much in the way of useful info, but the problem would appear to be client side rather than server side. From the logs it appears that the client side sent a ping, the server responded with a pong less than a second later, and the client logged off almost immediately.

Hopefully the new changes will fix all of that though.

edited on: 10-05-06 16:27
2006-10-05 18:29   
Looks like my DSL was reset early today. That might be the reason for the disconnect. The only thing that doesn't make sense is the times don't match up.

edited on: 10-05-06 18:29
2006-10-21 00:32   
Just marking as feedback those bugs which should either be fixed in the next available build from me, or need to be tested as fixed in the next available build.

(There are so many new bugs right now, it's easier for me to keep up with the fixed or almost-fixed bugs this way.)
2007-10-15 07:16   
Give the test build a try and let me know if this still happens:,49939.0.html

I think that this is fixed, but I can't really say for sure. I just know that I was unable to reproduce it.
2007-10-17 21:28   
Assuming that this is fixed, but reopen if you are able to replicate it in a newer build.

Issue History
2006-10-03 16:14FUBAR-BDHRNew Issue
2006-10-03 16:14FUBAR-BDHRFile Added: Media-10-03-06.rar
2006-10-03 16:15FUBAR-BDHRFile Added: P3-866-10-03-06.rar
2006-10-03 22:48taylorNote Added: 0006793
2006-10-04 11:31Goober5000Category--------- => multiplayer
2006-10-04 11:56taylorNote Added: 0006794
2006-10-04 11:56taylorStatusnew => assigned
2006-10-04 11:56taylorAssigned To => taylor
2006-10-04 17:20martellatoNote Added: 0006796
2006-10-05 15:58FUBAR-BDHRFile Added: P3-866-10-05-06.rar
2006-10-05 15:58FUBAR-BDHRFile Added: Media-10-05-06.rar
2006-10-05 16:26taylorNote Added: 0006806
2006-10-05 16:27taylorNote Edited: 0006806
2006-10-05 18:28FUBAR-BDHRFile Added: dsl.txt
2006-10-05 18:29FUBAR-BDHRNote Added: 0006809
2006-10-05 18:29FUBAR-BDHRNote Edited: 0006809
2006-10-21 00:32taylorNote Added: 0006949
2006-10-21 00:32taylorStatusassigned => feedback
2007-10-15 07:16taylorNote Added: 0008568
2007-10-17 21:28taylorStatusfeedback => resolved
2007-10-17 21:28taylorFixed in Version => 3.6.10
2007-10-17 21:28taylorResolutionopen => fixed
2007-10-17 21:28taylorNote Added: 0008577