[GH-ISSUE #921] Can't start rust #737

New issue

Closed

opened 2026-02-27 02:53:12 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:53:12 +03:00

Owner

Originally created by @stanislawszenk on GitHub (Jul 15, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/921

Hi,
I'm actually getting some error trying to launch Rust server after the update.
In fact It said Failed when doing ./rustserver start
In the logs:


juil. 15 14:12:39 rust-server: Starting: FATAL: Unable to start [FR] Rust Server <|R-E|>.x3
juil. 15 14:12:40 rust-server: Starting: FATAL: command_start.sh exiting with code: 1
juil. 15 14:13:16 rust-server: PASS: downloading command_update.sh: OK
juil. 15 14:13:17 rust-server: Update: PASS: downloading update_steamcmd.sh: OK
juil. 15 14:13:18 rust-server: Update: INFO: Starting SteamCMD
Redirecting stderr to '/root/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...Created shared memory when not owner SteamController_Shared_mem
OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for license info...OK
Success! App '258550' already up to date.
juil. 15 14:13:22 rust-server: Update: PASS: command_update.sh exiting with code: 0
juil. 15 14:13:32 rust-server: PASS: downloading command_debug.sh: OK
juil. 15 14:13:39 rust-server: Debug: INFO: Stopping any running servers
juil. 15 14:13:40 rust-server: Debug: PASS: downloading command_stop.sh: OK
juil. 15 14:13:42 rust-server: Stopping: ERROR: [FR] Rust Server <|R-E|>.x3 is already stopped
juil. 15 14:13:42 rust-server: Debug: INFO: Starting debug
juil. 15 14:13:43 rust-server: Debug: PASS: command_debug.sh exiting with code: 0
juil. 15 14:18:00 rust-server: PASS: downloading command_details.sh: OK
juil. 15 14:18:00 rust-server: Details: PASS: downloading info_parms.sh: OK
juil. 15 14:18:00 rust-server: Details: PASS: command_details.sh exiting with code: 0
juil. 15 14:18:12 rust-server: Log-Manager: INFO: Moving game logs to /home/rust/log/server
juil. 15 14:18:13 rust-server: Starting: INFO: Rotating log files

Originally created by @stanislawszenk on GitHub (Jul 15, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/921 Hi, I'm actually getting some error trying to launch Rust server after the update. In fact It said Failed when doing ./rustserver start In the logs: ``` juil. 15 14:12:39 rust-server: Starting: FATAL: Unable to start [FR] Rust Server <|R-E|>.x3 juil. 15 14:12:40 rust-server: Starting: FATAL: command_start.sh exiting with code: 1 juil. 15 14:13:16 rust-server: PASS: downloading command_update.sh: OK juil. 15 14:13:17 rust-server: Update: PASS: downloading update_steamcmd.sh: OK juil. 15 14:13:18 rust-server: Update: INFO: Starting SteamCMD Redirecting stderr to '/root/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...Created shared memory when not owner SteamController_Shared_mem OK. Connecting anonymously to Steam Public...Logged in OK Waiting for license info...OK Success! App '258550' already up to date. juil. 15 14:13:22 rust-server: Update: PASS: command_update.sh exiting with code: 0 juil. 15 14:13:32 rust-server: PASS: downloading command_debug.sh: OK juil. 15 14:13:39 rust-server: Debug: INFO: Stopping any running servers juil. 15 14:13:40 rust-server: Debug: PASS: downloading command_stop.sh: OK juil. 15 14:13:42 rust-server: Stopping: ERROR: [FR] Rust Server <|R-E|>.x3 is already stopped juil. 15 14:13:42 rust-server: Debug: INFO: Starting debug juil. 15 14:13:43 rust-server: Debug: PASS: command_debug.sh exiting with code: 0 juil. 15 14:18:00 rust-server: PASS: downloading command_details.sh: OK juil. 15 14:18:00 rust-server: Details: PASS: downloading info_parms.sh: OK juil. 15 14:18:00 rust-server: Details: PASS: command_details.sh exiting with code: 0 juil. 15 14:18:12 rust-server: Log-Manager: INFO: Moving game logs to /home/rust/log/server juil. 15 14:18:13 rust-server: Starting: INFO: Rotating log files ```

kerem closed this issue

2026-02-27 02:53:12 +03:00

kerem commented

2026-02-27 02:53:12 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 15, 2016):

Hi,
Sorry to hear that. Unfortunately, this kind of issues are to be expected with Rust, as it's an alpha game. Hopefully they didn't make an update that fucks up LGSM.

You should output the Rust log, it'd be the most useful.

Last current log is always in server files, that one is moved to the log folder upon Rust start (the game gave no other choice, you can't specify log location).
Please not that i'll be mostly AFK for 2 days, so hopefully this clue helps you solving the issue. Otherwise, close this and open an issue in the general help https://steamcommunity.com/groups/linuxgsm/discussions, or Oxide forums, they're quite competent.

@UltimateByte commented on GitHub (Jul 15, 2016): Hi, Sorry to hear that. Unfortunately, this kind of issues are to be expected with Rust, as it's an alpha game. Hopefully they didn't make an update that fucks up LGSM. You should output the Rust log, it'd be the most useful. Last current log is always in server files, that one is moved to the log folder upon Rust start (the game gave no other choice, you can't specify log location). Please not that i'll be mostly AFK for 2 days, so hopefully this clue helps you solving the issue. Otherwise, close this and open an issue in the general help https://steamcommunity.com/groups/linuxgsm/discussions, or Oxide forums, they're quite competent.

kerem commented

2026-02-27 02:53:12 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 21, 2016):

Closing as no answer. Feel free to re-open if needed.

@UltimateByte commented on GitHub (Jul 21, 2016): Closing as no answer. Feel free to re-open if needed.

kerem commented

2026-02-27 02:53:12 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.