Cannot restart server right away.

[DevRain2500]

You can not restart your server within a certain amount of time. You have to wait for the master server to clear out its entry.

Error:

03-11-2016 21:17:16|t01| INFO| Attempting to register on serverlist (//server-list)
03-11-2016 21:17:17|t01| INFO| Registration failed, response code: HTTP 409, body: {"result":false,"message":"Your server name is already used."}
03-11-2016 21:17:17|t01|ERROR| Failed to register on serverlist. Exit
SWBaseSocket::disconnect() error: Socket is not connected!
Press any key to continue . . .

---

Edit: Server was cleared from the master server, but the rorserver says it is still there.

[ohlidalp]

It's true, the master server doesn't recognize server restarts. Every registration is considered new.

AFAIK the previous versions recognized restarted servers by IP + name. I'll restore the functionality.

[DevRain2500]

@only-a-ptr How long does it take for the master server to clear out the entry? It says it is still registered, but does not show on http://multiplayer.rigsofrods.org/server-list

[ohlidalp]

@Dogy144 Sorry for the late response.
It's 1500sec = 25min, but the cleanup is only done upon GET request (someone displays the serverlist): https://github.com/RigsOfRods/multiplayer.rigsofrods.org/blob/master/server-list.php#L108-L111 So it's possible that even after the timeout your registration will still fail because nobody did a GET in the meantime.

It's really bad design. At the very least, the cleanup should be done at every request type, so we're not looking at dirty data.

[AnotherFoxGuy]

The problem is actually that the server doesn't shut down properly.
When you try to stop it, it crashes before sending a deregistration message to the master server

[DevRain2500]

How would you shut it down properly then? The only way that I know of is closing the prompt.

[ohlidalp]

@Dogy144 AFG says there's a bug in the server which causes bad shutdown.

I faintly recall this was also happening to me. I'll take a look at it: #35

[CuriousMike56]

The master server currently just hides the server from the list, then deletes the entry later. It should delete the entry as soon the server fails to respond.
It's currently impossible to restart the server without manually removing the entry from the database or wait for the entry to be cleared.