Configuring a Rust server for auto-reboots

I'm renting a VPS with Windows Server and running Rust on top of it. I'm on the schedule of manually stopping my server every morning and restarting (server.save, server.stop, quit, then reopen my start.bat file). Before I reload Rust my memory sits at ~3GB, after restarting it takes a little under ~2GB of RAM. So the daily reboot is really helpful.

I'm going to be gone for a few days and need to figure out a way to automate the server restarts. I thought server.restart was a thing, but when I tried this morning nothing happened. So I tried doing a server.stop then server.start, but server.start doesn't appear to do anything either.

Is there a way to reboot the Rust server without completely closing RustDedicated.exe and then restarting via a batch file? Since I've not seen it done any other way, the only way I know to keep the memory leak under control is to close RustDedicated.exe and restart it once a day.

How are other admins running with a VPS (not a GSP) managing their server reboots?

Thanks

 

I use vilayer and have scheduled save.all and auto restarts. Its built right in the console. Haven't Used any other host so not sure you might be able to find a plugin to do it

 

U can use my plugin
http://oxidemod.org/plugins/timedexecute.919/
just set in the config the command to restart its "restart" and 86400(one day in secs)

command restart warns people that in 60secs the server will restart and it saves everything unloading every plugin kicking every player that is on and then rebooting

 

Thank you Pain, I had my command wrong and was putting server.restart instead of just restart. Have you seen a similar memory leak issue like I described above, and if yes does the restart command release used memory like restarting RustDedicated.exe does?

 

I dont remember... but command "restart" reports many things spamms the console xD with kicks unloads and other things

 

One way to find out

Thanks for the help.

 

Thanks Wulf. I'll take a look at watchdog. I've used Task Scheduler to launch RustDedicated.exe in the past, but had trouble getting it to close an already open instance of it - the restart command if it shuts it down properly might be the remedy. Then it's a matter of getting the timing right.