"Another instance is already running" since the last update

It's not a bug. Install seperate copies of the server in different folders.

 

This is a bug released with a recent update.

To get round this you need to delete the line "single-instance=" from your boot.config file in RustDedicated_Data/

Hope this helps !

 

Yeah, it works for me. Thanks!

 

Sigh...

 

It IS a bug. There's a lot of us been using a single installation of Rust and then running servers in sub-directories under that one installation. Since the last update, it doesn't work any more.

Long term server ops will know that by default all servers used to run under a single installation of Rust. This was changed in the last 12-18 months, but Wulf allowed us to continue to do so by using this method in the start.bat job.

Code:

RustDedicated.exe -batchmode -nographics ^
+server.identity "PvP01" ^
+oxide.directory "\server\{server.identity}\oxide" ^

This then allowed us to run multiple servers under the single Rust installation. Every Thursday at update time all we had to do was update that single installation and ALL our servers running on that machine would be updated at the same time.

The directory structure looked like this:-

C:\GameServers\Rust\server\PvP01
C:\GameServers\Rust\server\PvP02
C:\GameServers\Rust\server\PvE01

Each directory would have its own \cfg\ and \oxide\ directories with a unique set of plugins, config, data, etc for each server.

So please stop sighing and accept there are server admins who have run servers like this for a very long time (in game terms). As of the last update, we can no longer do this because of the error reported by several people.

IT'S A BUG. Until Wulf tells us otherwise.

 

RIP using RMS For multiple servers ;(

 

Hi guys just had a look into this one and I've found cause and the fix.

Seems the latest releases have enabled the unity player single instance mode by default.

The fix is to remove:

Code:

single-instance=

From the configuration file:

Code:

RustDedicated_Data/boot.config

Once you have done this you can once again start multiple instances on the same machine.

Hope this helps.

 

Thank you, I was fairly certain it wasn't an Oxide thing, but the only way to know for sure was for you to say so.

I've now applied the Multiplay fix.

Thanks again.