[41.78] [Multiplayer] Server doesn't release lock on sqlite file upon failure to start

[Guest]

• Version?
• Singleplayer/Multiplayer? 
• Host or dedicated? 
• Mods? 
• Old or new save?
• Reproduction steps:
	
• 41.78
• Multiplayer.
• Dedicated on Debian 11
• Yes.
• N/A
• Reproduction steps:
        1. Start server 1.
        2. Start server 2.
        3. Exit server 1, exit server 2.
        4. Restart server 1.

Expected: Server 1 starts with no issues.
Actual: Server 2 still has a lock on the database file and exists as a zombie process. Server 1 throws error in logfile but continues operating as normal without saving player data.

Edited July 15, 2023 by CoreByte

[EnigmaGrey]

Two simultaneous severs need unique names, such as with the -servername name flag.

 

 They can’t share the same files.

[Guest]

That's a given, the problem is that exiting the server didn't release the lock on the file, even though server that errored due to the port conflict etc on startup should've released the lock once it failed to start and was exited.

[EnigmaGrey]

How are you controlling this; how’d you shut them down?

 

If you followed along with the guide in the pzwiki, you might have missed the warnings about setting up the sever as a background process. The server is not meant to be run in this manner.