
Which log explains why a Rust server quit?
Start with the game’s final console or log entries around the exit. Compare those times with the service or host log so the last visible message does not become an accidental diagnosis.
Build a short timeline
Use one time zone for all entries. In this example, a whole group of services returning together is a reason to look for a host boot at 21:07 UTC.
| Time (UTC) | Observation | Next check |
|---|---|---|
| 21:04 | The Rust log falls silent. | Read back to the last game message that describes an action or failure. |
| 21:05 | The panel reports the process gone. | Look for a recorded stop or exit at the same time. |
| 21:07 | Several unrelated services start again. | Look for a reboot in the host’s system log. |
Check the host record
On a systemd host, inspect the game service’s journal and compare it with kernel messages. On Windows, compare game output with the Application and System logs. If only Rust stopped, read the application or service failure at 21:04 UTC before investigating the later recovery attempt.
Verify the first event you can explain
A save followed by a recorded stop request points to an intentional shutdown. Silence in the game log followed by a new system boot calls for host investigation. A service continuously trying to start after an earlier exit is a consequence. Apply the fix to the earliest supported cause, then check the same log interval during one fresh start.