[GH-ISSUE #2812] ROServer _default.cfg contains formatting error causing server not to start #2026

New issue

Closed

opened 2026-02-27 03:00:25 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @AlbinoJack on GitHub (Apr 8, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2812

User Story

When attempting to start the ROServer a miss-typed line in _default.cfg causes the command-line launch parameters to not find the executable and fail to launch to server.

Basic info

Distro: [Debian 10]
Game: [Red Orchestra: Ostfront 41-45]
Command: [Start]
LinuxGSM version: [v20.1.5]

Further Information

After updating LGSM version sometime in the past few months the ROServer failed to start, citing an executable was not found.

##Found a miss-typed line in the _default.cfg file for ROServer under:

##Game Server Directories
serverfiles="${rootdir}/serverfiles"
systemdir="${serverfiles}/system"
executabledir="${systemdir}"
executable="./ucc-bin"servercfgdir="${systemdir}"
servercfgdir="${systemdir}"
servercfg="${selfname}.ini"
servercfgdefault="default.ini"
servercfgfullpath="${servercfgdir}/${servercfg}"
compressedmapsdir="${rootdir}/Maps-Compressed"

##Incorrect line is line 153 of the file:
[...]
executable="./ucc-bin"servercfgdir="${systemdir}"
[...]

##Corrected line should exclude characters after column 23
executable="./ucc-bin"

##Characters currently printed past column 23 on line 153 are duplicates of line 154 and shifted up to interfere with the executable line.

To Reproduce

Steps to reproduce the behaviour:

Command: ./roserver st
See error:
[ FAIL ] Starting roserver: executable was not found

/servers/roserver/serverfiles/system/system

Expected behaviour

Server successfully starts after altering config-lgsm file to remove incorrect, duplicate, code.

Originally created by @AlbinoJack on GitHub (Apr 8, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2812 ## User Story When attempting to start the ROServer a miss-typed line in _default.cfg causes the command-line launch parameters to not find the executable and fail to launch to server. ## Basic info * **Distro:** [Debian 10] * **Game:** [Red Orchestra: Ostfront 41-45] * **Command:** [Start] * **LinuxGSM version:** [v20.1.5] ## Further Information After updating LGSM version sometime in the past few months the ROServer failed to start, citing an executable was not found. ##Found a miss-typed line in the _default.cfg file for ROServer under: ##Game Server Directories serverfiles="${rootdir}/serverfiles" systemdir="${serverfiles}/system" executabledir="${systemdir}" executable="./ucc-bin"servercfgdir="${systemdir}" servercfgdir="${systemdir}" servercfg="${selfname}.ini" servercfgdefault="default.ini" servercfgfullpath="${servercfgdir}/${servercfg}" compressedmapsdir="${rootdir}/Maps-Compressed" ##Incorrect line is line 153 of the file: [...] executable="./ucc-bin"servercfgdir="${systemdir}" [...] ##Corrected line should exclude characters after column 23 executable="./ucc-bin" ##Characters currently printed past column 23 on line 153 are duplicates of line 154 and shifted up to interfere with the executable line. ## To Reproduce Steps to reproduce the behaviour: 1. Command: ./roserver st 4. See error: [ FAIL ] Starting roserver: executable was not found * /servers/roserver/serverfiles/system/system ## Expected behaviour Server successfully starts after altering config-lgsm file to remove incorrect, duplicate, code.

kerem

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

closed this issue
added the
game: Red Orchestra: Ostfront 41-45
label

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Apr 8, 2020):

see mentioned pull request that should fix that

@h3o66 commented on GitHub (Apr 8, 2020): see mentioned pull request that should fix that

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 26, 2021):

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 (Apr 26, 2021): 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.

kerem referenced this issue

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

[PR #2026] [CLOSED] Add fn_start_docker #3456