[GH-ISSUE #1409] G-Mod Server won't start but on debug mode #1096

New issue

Closed

opened 2026-02-27 02:55:17 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:55:17 +03:00

Owner

Originally created by @jantede on GitHub (Apr 25, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1409

Hi folks,

I've got quite a weird issue with my g-mod server ran with LinuxGSM. The server is set up in an debian 8 LXC Container with no other software but the requirements and the GSM.
Everything worked fine until i wanted to start the server today: Using the command ./gmodserver start, I only got the following output:

gmod@gameserver01:~$ ./gmodserver start
[ .... ] Starting gmod-server: failed to connect to server: Connection refused
[ FAIL ] Starting gmod-server: Unable to start KampfKielings GMOD Server 2017

The next thing I did was starting the server in debug mode which surprisingly worked seamlessly without any errors or problems (Log).
The logs in the log/server/ and log/console/ directory are completely empty. The only log I could find was in log/script. I've uploaded it to HasteBin.

Interestingly when I used the "postdetails" function it says the server is online which it isn't (Have a look).

The last thing I tried was backing up my configuration and completely reinstall the GSM which didn't help, I've got the exact same issue (even with the stock configuration and no addons).

I really don't know how to fix that issue. Do you have any ideas on how to resolve it? The next thing I'd probably do is resetting the whole Container. Thanks in advance for your help!

Originally created by @jantede on GitHub (Apr 25, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1409 Hi folks, I've got quite a weird issue with my g-mod server ran with LinuxGSM. The server is set up in an debian 8 LXC Container with no other software but the requirements and the GSM. Everything worked fine until i wanted to start the server today: Using the command `./gmodserver start`, I only got the following output: ``` gmod@gameserver01:~$ ./gmodserver start [ .... ] Starting gmod-server: failed to connect to server: Connection refused [ FAIL ] Starting gmod-server: Unable to start KampfKielings GMOD Server 2017 ``` The next thing I did was starting the server in debug mode which surprisingly worked seamlessly without any errors or problems ([Log](https://hastebin.com/oqegacihak.erl)). The logs in the log/server/ and log/console/ directory are completely empty. The only log I could find was in log/script. I've uploaded it to [HasteBin](https://hastebin.com/qolidiligo). Interestingly when I used the "postdetails" function it says the server is online which it isn't ([Have a look](https://hastebin.com/ividipojuc)). The last thing I tried was backing up my configuration and completely reinstall the GSM which didn't help, I've got the exact same issue (even with the stock configuration and no addons). I really don't know how to fix that issue. Do you have any ideas on how to resolve it? The next thing I'd probably do is resetting the whole Container. Thanks in advance for your help!

kerem closed this issue

2026-02-27 02:55:17 +03:00

kerem commented

2026-02-27 02:55:18 +03:00

Author

Owner

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

For an LXC container, test to see if the user can create a tmux session.

Just issue tmux and see if you get a tmux session or just the prompt back.

@cedarlug commented on GitHub (Apr 26, 2017): For an LXC container, test to see if the user can create a tmux session. Just issue `tmux` and see if you get a tmux session or just the prompt back.

kerem commented

2026-02-27 02:55:18 +03:00

Author

Owner

@jantede commented on GitHub (Apr 26, 2017):

I just get the prompt back which got me thinking:
I've tried the things above attached to the server via lxc-attach. The problem is that it creates the terminal as a TTY on the host system. As a consequence, users cannot start tmux sessions out of this terminal which causes the problem as described

When I connect to the container using SSH, everything works just fine as the terminal is created inside it.
So this is probably kind of a bug in LXC or tmux. Thanks for your help!

@jantede commented on GitHub (Apr 26, 2017): I just get the prompt back which got me thinking: I've tried the things above attached to the server via `lxc-attach`. The problem is that it creates the terminal as a TTY on the host system. As a consequence, users cannot start tmux sessions out of this terminal which causes the problem as described When I connect to the container using SSH, everything works just fine as the terminal is created inside it. So this is probably kind of a bug in LXC or tmux. Thanks for your help!

kerem commented

2026-02-27 02:55:18 +03:00

Author

Owner

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

Yes - it's an lxc issue. There's no initial PTY for tmux to attach to, which is why it works when you ssh in (you get a pty), but not when you do an lxc attach.

@cedarlug commented on GitHub (Apr 26, 2017): Yes - it's an lxc issue. There's no initial PTY for tmux to attach to, which is why it works when you ssh in (you get a pty), but not when you do an lxc attach.

kerem commented

2026-02-27 02:55:18 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 18, 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 18, 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.