starred/LinuxGSM

Fork 0

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

2019 #1907

New issue

Closed

opened 2026-02-27 02:59:44 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:59:44 +03:00

Owner

Originally created by @rip1980 on GitHub (Dec 2, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2635

I've been running multiple CS1.6 servers for years, and LGSM for many of those. For some reason, the script broke on 12/1/2019. and MAYBE it's date related?

There have been no changes to my servers experiencing these issues since June, and they've all failed identically on 12/1. So it's a script issue or a Ubuntu update breaking things, bit no overt werrors found so far. I double checked permissions, update the script (ul), etc., and confident I didn't break it, via update or otherwise.

Issue 1:
./hlds_run -game cstrike -strictportbind +ip [EDITED] -port 27018 +clientport 27005 +map de_dust2 +servercfgfile .cfg -maxplayers 32 -tos -pingboost 2 -sys_ticrate 1000

It now not recognizing server.cfg and using ".cfg" instead.

My work around for this currently is edit cssserver.cfg and replace the string with a hard server.cfg

fn_parms(){
parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} +servercfgfile server.cfg -maxplayers ${maxplayers} -tos -pingboost 2 -sys_ticrate 1000"

Issue 2:
Log naming is getting mangled, "csserver" being trimmed from the beginning of the naming convention, as illustrated by the hastebin below.
Examples:
-rw-r--r-- 1 csserver4 csserver4 8747 Dec 1 17:05 -alert.log
-rw-rw-r-- 1 csserver4 csserver4 9526 Dec 1 00:00 csserver-alert.log

Server Details
https://hastebin.com/jowexoyupo

Mangled log naming:
https://hastebin.com/dicicotaba.diff

Originally created by @rip1980 on GitHub (Dec 2, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2635 I've been running multiple CS1.6 servers for years, and LGSM for many of those. For some reason, the script broke on 12/1/2019. and MAYBE it's date related? There have been no changes to my servers experiencing these issues since June, and they've all failed identically on 12/1. So it's a script issue or a Ubuntu update breaking things, bit no overt werrors found so far. I double checked permissions, update the script (ul), etc., and confident I didn't break it, via update or otherwise. Issue 1: ./hlds_run -game cstrike -strictportbind +ip [EDITED] -port 27018 +clientport 27005 +map de_dust2 **+servercfgfile .cfg** -maxplayers 32 -tos -pingboost 2 -sys_ticrate 1000 It now not recognizing server.cfg and using ".cfg" instead. My work around for this currently is edit cssserver.cfg and replace the string with a hard server.cfg fn_parms(){ parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} **+servercfgfile server.cfg** -maxplayers ${maxplayers} -tos -pingboost 2 -sys_ticrate 1000" Issue 2: Log naming is getting mangled, "csserver" being trimmed from the beginning of the naming convention, as illustrated by the hastebin below. Examples: -rw-r--r-- 1 csserver4 csserver4 8747 Dec 1 17:05 -alert.log -rw-rw-r-- 1 csserver4 csserver4 9526 Dec 1 00:00 csserver-alert.log Server Details https://hastebin.com/jowexoyupo Mangled log naming: https://hastebin.com/dicicotaba.diff

kerem

2026-02-27 02:59:44 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Dec 2, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.89. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Dec 2, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.89. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@Frisasky commented on GitHub (Dec 2, 2019):

remove all content below LinuxGSM Settings in config file
btw you should only copy parameters you wanna changed to instance's config file, not the whole file

@Frisasky commented on GitHub (Dec 2, 2019): remove all content below LinuxGSM Settings in config file btw you should only copy parameters you wanna changed to instance's config file, not the whole file

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 2, 2019):

./csserver update-lgsm bug was was released yesterday

@dgibbs64 commented on GitHub (Dec 2, 2019): `./csserver update-lgsm` bug was was released yesterday

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@rip1980 commented on GitHub (Dec 2, 2019):

I did update lgsm before posting the bug, the hastebin is from v19.12.3 unless there's a newer one I'm not seeing.

Frisasky - Not an issue here. I run multiple instances of lgsm separately, not multiple game servers under one script.

@rip1980 commented on GitHub (Dec 2, 2019): I did update lgsm before posting the bug, the hastebin is from v19.12.3 unless there's a newer one I'm not seeing. Frisasky - Not an issue here. I run multiple instances of lgsm separately, not multiple game servers under one script.

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@Frisasky commented on GitHub (Dec 2, 2019):

lgsm got an update without raising the version number, so try update-lgsm

@Frisasky commented on GitHub (Dec 2, 2019): lgsm got an update without raising the version number, so try update-lgsm

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@rip1980 commented on GitHub (Dec 2, 2019):

Thanks guys. That last commit was 2 hours after I posted the bug and updated with ul. Ships passing in the night, lol.

It did indeed update and it did properly show the server.cfg with dt after rolling back my hard edit workaround. Monitoring to see if it still mangles log naming or anything else.

checking function core_legacy.sh...UPDATE

@rip1980 commented on GitHub (Dec 2, 2019): Thanks guys. That last commit was 2 hours after I posted the bug and updated with ul. Ships passing in the night, lol. It did indeed update and it did properly show the server.cfg with dt after rolling back my hard edit workaround. Monitoring to see if it still mangles log naming or anything else. checking function core_legacy.sh...UPDATE

kerem commented

2026-02-27 02:59:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 13, 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 (Mar 13, 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.