starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #4003] [BUG] Barotrauma v22.1.0 fails to launch #2581

New issue

Closed

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

kerem commented

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

Owner

Originally created by @frozenfoxx on GitHub (Oct 5, 2022).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4003

Originally assigned to: @h3o66 on GitHub.

User Story

As a server operator, I want to launch btserver so that players can play on the server.

Basic info

Distro: Ubuntu 22.04
Game: Barotrauma
Command: start
LinuxGSM version: v22.2.0

Further Information

When starting a Barotrauma server after installation it fails. The /home/btserver/log/console/btserver-console.log is blank.

btserver@barotrauma:~$ ./btserver start
[ .... ] Starting btserver: Serverno server running on /tmp/tmux-1000/default
[ FAIL ] Starting btserver: Unable to start Server

The btserver-script.log indicates an issue, but doesn't say what:

btserver@barotrauma:~/log/script$ cat btserver-script.log
Oct 05 22:17:59.582 btserver: START: FATAL: Unable to start Server
Oct 05 22:17:59.589 btserver: START: INFO: LinuxGSM version: v22.2.0
Oct 05 22:17:59.590 btserver: START: FATAL: core_exit.sh exiting with code: 1

To Reproduce

Steps to reproduce the behaviour:

Install Ubuntu 22.04.
Create a btserver unprivileged user.
Install dependencies as root.
As btserver, wget -O linuxgsm.sh https://linuxgsm.sh && chmod +x linuxgsm.sh && bash linuxgsm.sh btserver.
As btserver, ./btserver install.
As btserver, ./btserver start.
Failure, see above.

Expected behaviour

Server starts.

Originally created by @frozenfoxx on GitHub (Oct 5, 2022). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4003 Originally assigned to: @h3o66 on GitHub. ## User Story As a server operator, I want to launch `btserver` so that players can play on the server. ## Basic info - **Distro:** Ubuntu 22.04 - **Game:** Barotrauma - **Command:** start - **LinuxGSM version:** v22.2.0 ## Further Information When starting a Barotrauma server after installation it fails. The `/home/btserver/log/console/btserver-console.log` is blank. ``` btserver@barotrauma:~$ ./btserver start [ .... ] Starting btserver: Serverno server running on /tmp/tmux-1000/default [ FAIL ] Starting btserver: Unable to start Server ``` The `btserver-script.log` indicates an issue, but doesn't say what: ``` btserver@barotrauma:~/log/script$ cat btserver-script.log Oct 05 22:17:59.582 btserver: START: FATAL: Unable to start Server Oct 05 22:17:59.589 btserver: START: INFO: LinuxGSM version: v22.2.0 Oct 05 22:17:59.590 btserver: START: FATAL: core_exit.sh exiting with code: 1 ``` ## To Reproduce Steps to reproduce the behaviour: 1. Install Ubuntu `22.04`. 2. Create a `btserver` unprivileged user. 3. Install dependencies as `root`. 4. As `btserver`, `wget -O linuxgsm.sh https://linuxgsm.sh && chmod +x linuxgsm.sh && bash linuxgsm.sh btserver`. 5. As `btserver`, `./btserver install`. 6. As `btserver`, `./btserver start`. 7. Failure, see above. ## Expected behaviour Server starts.

kerem

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

closed this issue
added the
command: console

distro: Ubuntu

command: install

command: start

game: Barotrauma

info: tmux
labels

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Oct 6, 2022):

I had a simular problem yesterday when i was testing the server.

for me i did need to convert the script to the linux line endings

command:
dos2unix serverfiles/DedicatedServer.exe

if the command is not installed, you can install it with:
apt install dos2unix -y

@h3o66 commented on GitHub (Oct 6, 2022): I had a simular problem yesterday when i was testing the server. for me i did need to convert the script to the linux line endings command: `dos2unix serverfiles/DedicatedServer.exe` if the command is not installed, you can install it with: `apt install dos2unix -y`

kerem commented

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

Author

Owner

@frozenfoxx commented on GitHub (Oct 8, 2022):

Added these to my Ansible deployment and now it functions. Seems like something that should probably be in the system requirements or in the fixes.

@frozenfoxx commented on GitHub (Oct 8, 2022): Added these to my Ansible deployment and now it functions. Seems like something that should probably be in the system requirements or in the fixes.

kerem commented

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

Author

Owner

@Marcin648 commented on GitHub (Oct 22, 2022):

Problem is wrong executable binary in LGSM config.
I just change from executable="./DedicatedServer.exe" to executable="./DedicatedServer" and that fixes the problem.

Yes, both binary exist in this game server ;)

@Marcin648 commented on GitHub (Oct 22, 2022): Problem is wrong executable binary in LGSM config. I just change from `executable="./DedicatedServer.exe"` to `executable="./DedicatedServer"` and that fixes the problem. Yes, both binary exist in this game server ;)

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Oct 22, 2022):

Problem is wrong executable binary in LGSM config. I just change from executable="./DedicatedServer.exe" to executable="./DedicatedServer" and that fixes the problem.

Yes, both binary exist in this game server ;)

the exe is only a script that starts the server with a extra LD_LIBRARY path set

@h3o66 commented on GitHub (Oct 22, 2022): > Problem is wrong executable binary in LGSM config. I just change from `executable="./DedicatedServer.exe"` to `executable="./DedicatedServer"` and that fixes the problem. > > Yes, both binary exist in this game server ;) the `exe` is only a script that starts the server with a extra LD_LIBRARY path set

kerem commented

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

Author

Owner

@Marcin648 commented on GitHub (Oct 22, 2022):

I didn't knows that this exe is a script file. 😃
Anyway, that LD_LIBRARY add linux64 directory, that have only steamclient.so. This lib is provided by other steamclient.so fixes. So it's works anyway. But yes, using this exe and dos2unix is preferable :)

@Marcin648 commented on GitHub (Oct 22, 2022): I didn't knows that this `exe` is a script file. 😃 Anyway, that `LD_LIBRARY` add `linux64` directory, that have only `steamclient.so`. This lib is provided by other steamclient.so fixes. So it's works anyway. But yes, using this `exe` and `dos2unix` is preferable :)

kerem commented

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

Author

Owner

@rainst commented on GitHub (Dec 21, 2022):

I was having this issue too on my ubuntu dedicated server, so this needs to be addressed by the developer?
the dos2unix solution will need to be applied every time an update will be out, correct?

@rainst commented on GitHub (Dec 21, 2022): I was having this issue too on my ubuntu dedicated server, so this needs to be addressed by the developer? the `dos2unix` solution will need to be applied every time an update will be out, correct?

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Dec 21, 2022):

I was having this issue too on my ubuntu dedicated server, so this needs to be addressed by the developer? the dos2unix solution it will need to be applied every time an update will be out, correct?

Would be the best if the game developer could do this.
The solution in the connected PR is applied when needed as a workaround.

@h3o66 commented on GitHub (Dec 21, 2022): > I was having this issue too on my ubuntu dedicated server, so this needs to be addressed by the developer? the `dos2unix` solution it will need to be applied every time an update will be out, correct? Would be the best if the game developer could do this. The solution in the connected PR is applied when needed as a workaround.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Feb 5, 2024):

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

@github-actions[bot] commented on GitHub (Feb 5, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.