starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1266] [RUST] Server Start Issue. "Unable to start rust-server: Tmux error:" #981

New issue

Closed

opened 2026-02-27 02:54:39 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:54:39 +03:00

Owner

Originally created by @OGDugz on GitHub (Jan 22, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1266

Game: Rust.
./rustserver postdetails : https://hastebin.com/melibojawe
Log (I don't think it's that useful): http://pastebin.com/xBD3mfPk
Linux Distro and Version: Centos 7
Other: I noticed some other posts regarding a Tmux error with very similar error messages, they had responses regarding Tmux generally in their systems. I can tell you that I had LGSM Arma 3 running perfectly fine on this same system using Tmux if that's useful in any way.

To add onto that originally it gave me a 'fix' which was "usermod -G tty rustserver", I performed this fix and got identical results.

If any further information is required, I'll provide anything else I can.

Originally created by @OGDugz on GitHub (Jan 22, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1266 **Game:** Rust. **./rustserver postdetails :** https://hastebin.com/melibojawe **Log (I don't think it's that useful):** http://pastebin.com/xBD3mfPk **Linux Distro and Version:** Centos 7 **Other:** I noticed some other posts regarding a Tmux error with very similar error messages, they had responses regarding Tmux generally in their systems. I can tell you that I had LGSM Arma 3 running perfectly fine on this same system using Tmux if that's useful in any way. To add onto that originally it gave me a 'fix' which was "usermod -G tty rustserver", I performed this fix and got identical results. If any further information is required, I'll provide anything else I can.

kerem closed this issue

2026-02-27 02:54:39 +03:00

kerem commented

2026-02-27 02:54:39 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 23, 2017):

Hey.
Thumbs up for reading our "Support" wiki page. However, if this is only a user issue, it'll be better off solved on Discord or Steam.

Tmux error: > Is this the full message? I believe it could not actually be a tmux error. If this is the case, that is something you could probably help us solve.

To diagnose this, nothing better than ./rustserver debug command.
https://github.com/GameServerManagers/LinuxGSM/wiki/debug

Better change this default rcon password within rustserver script (put anything other than that, until we solved your issue, then put a real passowrd, because it might get displayed into logs):

+rcon.password "CHANGE_ME"
Jan 22 04:00:19 rust-server: CHECK: WARN: Default RCON Password detected

Also, a good practice is to define your server IP within rustserver script.

Any gamelog generated ? cat serverfiles/game*.log

(Woops, missclick for closing)

@UltimateByte commented on GitHub (Jan 23, 2017): Hey. Thumbs up for reading our "Support" wiki page. However, if this is only a user issue, it'll be better off solved on Discord or Steam. `Tmux error:` > Is this the full message? I believe it could not actually be a tmux error. If this is the case, that is something you could probably help us solve. To diagnose this, nothing better than `./rustserver debug` command. https://github.com/GameServerManagers/LinuxGSM/wiki/debug Better change this default rcon password within rustserver script (put anything other than that, until we solved your issue, then put a real passowrd, because it might get displayed into logs): ```` +rcon.password "CHANGE_ME" Jan 22 04:00:19 rust-server: CHECK: WARN: Default RCON Password detected ```` Also, a good practice is to define your server IP within rustserver script. Any gamelog generated ? `cat serverfiles/game*.log` (Woops, missclick for closing)

kerem commented

2026-02-27 02:54:39 +03:00

Author

Owner

@OGDugz commented on GitHub (Jan 23, 2017):

Hello, thanks for your response.

Weirdly enough I am no longer getting that error. Now when I use "./rustserver start" it appears to start properly, however, the server never actually starts. Upon trying to connect through direct connect I get a connection failed error and when I use the command "./rustserve stop" it says that the server is already stopped. I've also changed the RCON password as suggested. I have made no changes what so ever since I received the initial error and the box has not gone offline so this different result is especially weird to me.

./rustserver debug results
[ INFO ] Debug rust-server: Stopping any running servers
[ INFO ] Stopping rust-server: rust-server - UP Test Server is already stopped
[ OK ] Debug rust-server: Starting debug
/home/rustserver/lgsm/functions/command_debug.sh: line 107: 19162 Aborted ${executable} ${parms}

Pardon my ignorance, but from what I can tell a debug file hasn't been created due to an error on line 107.

No game logs were created when I was receiving the TMUX error warning, however, now I'm getting some with this issue.

GameLog Paste: http://pastebin.com/81zvf9uT

@OGDugz commented on GitHub (Jan 23, 2017): Hello, thanks for your response. Weirdly enough I am no longer getting that error. Now when I use "./rustserver start" it appears to start properly, however, the server never actually starts. Upon trying to connect through direct connect I get a connection failed error and when I use the command "./rustserve stop" it says that the server is already stopped. I've also changed the RCON password as suggested. I have made no changes what so ever since I received the initial error and the box has not gone offline so this different result is especially weird to me. **./rustserver debug results** [ INFO ] Debug rust-server: Stopping any running servers [ INFO ] Stopping rust-server: rust-server - UP Test Server is already stopped [ OK ] Debug rust-server: Starting debug /home/rustserver/lgsm/functions/command_debug.sh: line 107: 19162 Aborted ${executable} ${parms} Pardon my ignorance, but from what I can tell a debug file hasn't been created due to an error on line 107. No game logs were created when I was receiving the TMUX error warning, however, now I'm getting some with this issue. **GameLog Paste:** http://pastebin.com/81zvf9uT

kerem commented

2026-02-27 02:54:39 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 23, 2017):

Looks like you got a residual process in the background.
ps aux | grep Rust will tell you that.
Kill it (with fire... or rather with kill {appid} command) if needed.

I can see you updated your tmux. In some cases with CentOS, the update is partly made and you got one more step to do so that there is not a version conflict. @cedarlug knows more than i do about this, but if you're patient enough you can find back the process of diagnosing and solving this by searching here. http://steamcommunity.com/groups/linuxgsm/discussions/0/

@UltimateByte commented on GitHub (Jan 23, 2017): Looks like you got a residual process in the background. `ps aux | grep Rust` will tell you that. Kill it (with fire... or rather with `kill {appid}` command) if needed. I can see you updated your tmux. In some cases with CentOS, the update is partly made and you got one more step to do so that there is not a version conflict. @cedarlug knows more than i do about this, but if you're patient enough you can find back the process of diagnosing and solving this by searching here. http://steamcommunity.com/groups/linuxgsm/discussions/0/

kerem commented

2026-02-27 02:54:39 +03:00

Author

Owner

@cedarlug commented on GitHub (Jan 24, 2017):

@Nobbyblue It looks like you have a lot of "could be's" going on related to other threads.

Could be that /sys/class/net isn't readable. Why that matters is a mystery on par with why people park on driveways and drive on parkways. Reference this discussion regarding similar output, try this first (as root):

chmod a+x /sys 
chmod a+rx /sys/class 
chmod a+r /sys/class/net

Start it up. If it stays running your bug is due to /sys/class/net not being readable. That's the quick fix.

If it doesn't run, then it could be that you're running an OVH kernel (based on the version of the kernel in your post details output). Why that matters is a mystery on par with why Unix programmers dislike certain letters such as the e missing from resolv.conf and the n missing in umount. You might have been bitten by the recent issues revolving around their specific kernel. Try upgrading to their latest experimental kernel as described in the the OVH howto (linked in the git discussion).

@cedarlug commented on GitHub (Jan 24, 2017): @Nobbyblue It looks like you have a lot of "could be's" going on related to other threads. Could be that `/sys/class/net` isn't readable. Why that matters is a mystery on par with why people park on driveways and drive on parkways. Reference [this discussion regarding similar output](http://steamcommunity.com/groups/linuxgsm/discussions/0/154645427520545953/#c154645497345689334), try this first (as root): ```bash chmod a+x /sys chmod a+rx /sys/class chmod a+r /sys/class/net ``` Start it up. If it stays running your bug is due to `/sys/class/net` not being readable. That's the quick fix. If it doesn't run, then it could be that you're running an OVH kernel (based on the version of the kernel in your post details output). Why that matters is a mystery on par with why Unix programmers dislike certain letters such as the `e` missing from `resolv.conf` and the `n` missing in `umount`. You might have been bitten by the recent [issues revolving around their specific kernel](https://github.com/GameServerManagers/LinuxGSM/issues/1254). Try upgrading to their latest experimental kernel as described in the the OVH howto (linked in the git discussion).

kerem commented

2026-02-27 02:54:39 +03:00

Author

Owner

@cedarlug commented on GitHub (Jan 26, 2017):

Re-open if the issue hasn't been solved.

@cedarlug commented on GitHub (Jan 26, 2017): Re-open if the issue hasn't been solved.

kerem commented

2026-02-27 02:54:39 +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.

kerem referenced this issue

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

[PR #981] [MERGED] check_deps.sh improvements #3222