I wrote a simple batch file to ensure my server instantly restarts if it crashes or the server window is manually closed (i.e. after config changes, or new mods added to /Resources/Client/, etc., for fast restart).
I use two instances of it on two servers concurrent.
What it is not:
An error handler.
What the batch file does:
Prints usage info about itself
Panic condition check
Launches BeamMP-Server.exe and waits for it to crash or be manually closed
If the server crashes or is manually closed, logs warning in console, backs up server.log, and instantly restarts BeamMP-Server.exe
How to use it:
Extract batch file from .zip, place next to BeamMP-Server.exe
//Provided by Dudekahedron - 2020
@echo off
color 07
SETLOCAL EnableDelayedExpansion
for /F "tokens=1,2 delims=#" %%a in ('"prompt #$H#$E# & echo on & for %%b in (1) do rem"') do (
set "DEL=%%a"
)
cls
title BeamMP Server Watchdog
echo.
echo Protecting BeamMP Server from crashes^^!
echo.
echo Should you want to close BeamMP Server and this script:
echo.
echo 1. Close this window.
echo 2. Close the BeamMP Server window.
echo _________________________________________________________________
echo.
IF NOT EXIST BeamMP-Server.exe (
GOTO:nobmps
) ELSE (
GOTO:bmps
)
:bmps
echo [%date% - %time%]
call :colorEcho 09 " BeamMP Server started"
echo.
call :colorEcho 0A " [MONITORING]"
start "BeamMP Server" /w BeamMP-Server.exe | set /p exitkey= ""
echo.
echo [%date% - %time%]
call :colorEcho 0C " [WARNING] BeamMP Server crashed, or was closed"
echo.
call :colorEcho 0E " Backing up Server.log"
echo.
copy /V /Y Server_previous.log Server_previous_previous.log >nul
copy /V /Y Server.log Server_previous.log >nul
call :colorEcho 06 " Restarting server"
echo.
GOTO:bmps
:nobmps
echo [%date% - %time%]
call :colorEcho 4F "[FATAL] BeamMP-Server.exe NOT FOUND - EXITING"
echo.
pause
GOTO:EOF
:colorEcho
echo off
<nul set /p ".=%DEL%" > "%~2"
findstr /v /a:%1 /R "^$" "%~2" nul
del "%~2" > nul 2>&1i
Any feedback or constructive criticism is welcome!
Thanks!
<standard caveat of non-liability, “use at own risk” type jargon>
Revised 10/5/2020:
I was considering adding in a timed restart as others have demonstrated but am going to instead opt to wait for servers to mature further so I won’t need to remove it in the future.
@Dudekahedron i mean its just like every other game server I’ve ever hosted. You gotta give your router time to realize the computer isn’t hosting it anymore. It’ll close the port which frees it up. Once the server opens it will reopen the port. Restarting instantly is how you get port conflicts. Also known as “Already in use” issues. Hadn’t ran across it yet but could be why so many get stuck at loading.
Revised 10/5/2020:
Small change. A while back I started appending logs from CobaltEssentials into the standard Server.log instead of creating two separate logs and so I’ve simply uploaded an update of this batch file that doesn’t bother checking for a cobalt.log at all. Still has the panic condition and other late changes. I was considering adding in a timed restart as others have demonstrated but am going to instead opt to wait for servers to mature further so I won’t need to remove it in the future.
Revised 8/10/2020:
Found stuff to change!
BeamMP debug logs are much more useful now, and the logs the Watchdog makes when debug=true in Server.cfg will not become massive.
Tossed in a panic condition when BeamMP-Server.exe is not found so that you don’t get batch-bombed if used incorrectly.
Cleaned up timestamps, got rid of mode setting (just because I like the window size doesn’t mean others will), and refined colors.
I have set up my copy of CobaltEssentials (Thanks, @Preston!) to create a Cobalt.log file, so if you happen to have done the same somehow, this will also create backups of that as well, but the log file must be named Cobalt.log. If you do not have a Cobalt.log it will skip this, as there is nothing to backup.
Made Server.log backup system better - keeps current and two most recent logs.
Made the colors easier to look at.
I can’t really think of anything else at this point, as far as I can tell, this should really enable a server to have >99% uptime unless the computer running the server itself somehow has a failure.
I’ve had good success using it to quickly do restarts when troubleshooting a new command, and I’ve had a one actual crash → restart so far and it didn’t skip a beat.
Hopeful for more flexible server debug output in the future so logs don’t get massive.
Cleaned house
Titled the protected BeamMP-Server console properly
Added t e c h n i c o l o r
Most recent Server.log is now dumped to Server_bak.log on crash or close (might get gnarly with huge debug logs?)
colors easier to look at.