starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1111] Unhandled single quotes in config #875

New issue

Closed

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

kerem commented

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

Owner

Originally created by @hatbocs on GitHub (Oct 9, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1111

Found when configuring my csgo server.

// Server Name
hostname "Ba-loo's Comp Server"

When restarting the server I get errors.

csgoserver@baloomain:~$ ./csgoserver restart
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
[ .... ] Stopping csgo-server: NOT SETxargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
[ERROR ] Stopping csgo-server: Graceful: rcon quit: FAIL
[ OK ] Stopping csgo-server: NOT SET
[ .... ] Starting csgo-server: NOT SETxargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
[ OK ] Starting csgo-server: NOT SET

Removing the single quote in the hostname will correct this. hostname "Ba-loos Comp Server"

I traced this back to /lgsm/functions/info_config.sh and added a bit to the servername line. Note -e "s/'//g" which removes stray single quotes.

servername=$(grep "hostname" "${servercfgfullpath}" | sed -e 's/^[ \t]*//g' -e '/^//d' -e "s/'//g" -e 's/hostname//g' | tr -d '=";,:' | xargs

Not ideal, I think but the only work around I have right now since I'm not great with bash scripting.

I haven't had this issue until a week ago, or so.

Originally created by @hatbocs on GitHub (Oct 9, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1111 Found when configuring my csgo server. > // Server Name > hostname "Ba-loo's Comp Server" When restarting the server I get errors. > csgoserver@baloomain:~$ ./csgoserver restart > xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option > [ .... ] Stopping csgo-server: NOT SETxargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option > [ERROR ] Stopping csgo-server: Graceful: rcon quit: FAIL > [ OK ] Stopping csgo-server: NOT SET > [ .... ] Starting csgo-server: NOT SETxargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option > [ OK ] Starting csgo-server: NOT SET Removing the single quote in the hostname will correct this. `hostname "Ba-loos Comp Server"` I traced this back to /lgsm/functions/info_config.sh and added a bit to the servername line. Note `-e "s/'//g"` which removes stray single quotes. > servername=$(grep "hostname" "${servercfgfullpath}" | sed -e 's/^[ \t]*//g' -e '/^\//d' -e "s/'//g" -e 's/hostname//g' | tr -d '=\";,:' | xargs Not ideal, I think but the only work around I have right now since I'm not great with bash scripting. I haven't had this issue until a week ago, or so.

kerem

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

closed this issue
added the
type: bug
label

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 9, 2016):

Thanks for your attention. We need to reproduce this. If you're right, then it's a global bug that needs to be fixed with like a line of code or two. :)
Funny this error didn't come up before, maybe single quotes are not very popular in server titles.

@UltimateByte commented on GitHub (Oct 9, 2016): Thanks for your attention. We need to reproduce this. If you're right, then it's a global bug that needs to be fixed with like a line of code or two. :) Funny this error didn't come up before, maybe single quotes are not very popular in server titles.

kerem commented

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

Author

Owner

@hatbocs commented on GitHub (Oct 9, 2016):

Thank you much.

Oddly enough, I'm pretty sure some older version of the scripts were handling it just fine because I could have sworn I was using an apostrophe/single quote in the hostname this whole time. The only thing that would have changed was finally getting the newest version of the csgoserver script. The one I was using before was still looking for dgibbs64, if that helps.

@hatbocs commented on GitHub (Oct 9, 2016): Thank you much. Oddly enough, I'm pretty sure some older version of the scripts were handling it just fine because I could have sworn I was using an apostrophe/single quote in the hostname this whole time. The only thing that would have changed was finally getting the newest version of the csgoserver script. The one I was using before was still looking for dgibbs64, if that helps.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 9, 2016):

Error reproduced on a gmod server, confirmed.
Every source game is concerned, maybe more.
If you put two single quotes the error doesn't happen.

Key to fix it : So the best way would be to set this variable in a way that accepts single quotes... Can't think of one for now, would need some research. Or, using a special sed as suggested.

The only thing that would have changed was finally getting the newest version of the csgoserver script.

Nope, as you said previously, it's not csgoserver itself but info_config.sh. Unless you're talking about a very old time where everything was contained into one single script. :p

@UltimateByte commented on GitHub (Oct 9, 2016): Error reproduced on a gmod server, confirmed. Every source game is concerned, maybe more. If you put two single quotes the error doesn't happen. Key to fix it : So the best way would be to set this variable in a way that accepts single quotes... Can't think of one for now, would need some research. Or, using a special sed as suggested. > The only thing that would have changed was finally getting the newest version of the csgoserver script. Nope, as you said previously, it's not csgoserver itself but info_config.sh. Unless you're talking about a very old time where everything was contained into one single script. :p

kerem commented

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

Author

Owner

@cedarlug commented on GitHub (Oct 9, 2016):

Try adding -e 's/0x27/\\\'/g'into the expression (if you want to preserve the tick/apostrophe).

(This is off the top of my head - I'll check to see what that does here in a moment.)

@cedarlug commented on GitHub (Oct 9, 2016): Try adding `-e 's/0x27/\\\'/g'`into the expression (if you want to preserve the tick/apostrophe). (This is off the top of my head - I'll check to see what that does here in a moment.)

kerem commented

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

Author

Owner

@cedarlug commented on GitHub (Oct 9, 2016):

Are either/both of you getting a message about xargs with the single tick? If so, I think that I have the global fix.

@cedarlug commented on GitHub (Oct 9, 2016): Are either/both of you getting a message about xargs with the single tick? If so, I think that I have the global fix.

kerem commented

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

Author

Owner

@hatbocs commented on GitHub (Oct 9, 2016):

The quote I had in the first post was exactly what the script was spitting out to console when I first reported the issue (before attempting to fix). So in short, yes.

@hatbocs commented on GitHub (Oct 9, 2016): The quote I had in the first post was exactly what the script was spitting out to console when I first reported the issue (before attempting to fix). So in short, yes.

kerem commented

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

Author

Owner

@cedarlug commented on GitHub (Oct 9, 2016):

./csgoserver uf
sed -i 's/xargs)$/xargs -0)/g' lgsm/functions/info_config.sh
./csgoserver details

Please try.

@cedarlug commented on GitHub (Oct 9, 2016): ``` bash ./csgoserver uf sed -i 's/xargs)$/xargs -0)/g' lgsm/functions/info_config.sh ./csgoserver details ``` Please try.

kerem commented

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

Author

Owner

@cedarlug commented on GitHub (Oct 9, 2016):

Oh - but if you edited the file first, then probably the full shabang is necessary:

rm lgsm/functions/info_config.sh                             #remove existing version
./csgoserver details 2>&1 > /dev/null                        # forces it to be re-downloaded
sed -i 's/xargs)$/xargs -0)/g' lgsm/functions/info_config.sh #fixes the pristine source
./csgoserver details                                         # All good?

@cedarlug commented on GitHub (Oct 9, 2016): Oh - but if you edited the file first, then probably the full shabang is necessary: ``` bash rm lgsm/functions/info_config.sh #remove existing version ./csgoserver details 2>&1 > /dev/null # forces it to be re-downloaded sed -i 's/xargs)$/xargs -0)/g' lgsm/functions/info_config.sh #fixes the pristine source ./csgoserver details # All good? ```

kerem commented

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

Author

Owner

@hatbocs commented on GitHub (Oct 9, 2016):

Worked for me.

Now to figure out why rcon won't gracefully quit. And why my server doesn't show up in the server browser.

@hatbocs commented on GitHub (Oct 9, 2016): Worked for me. Now to figure out why rcon won't gracefully quit. And why my server doesn't show up in the server browser.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 9, 2016):

@hatbocs Start by watching your console logs. Those two errors (graceful and not showing up) might be related. I bet on a GSLT issue.

@UltimateByte commented on GitHub (Oct 9, 2016): @hatbocs Start by watching your console logs. Those two errors (graceful and not showing up) might be related. I bet on a GSLT issue.

kerem commented

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

Author

Owner

@hatbocs commented on GitHub (Oct 9, 2016):

Of course, the logs! For some reason I didn't look through them. And there's a segmentation fault as it's starting the server. I'll have to tackle that one later on today.

Thanks for the help @UltimateByte and @cedarlug

@hatbocs commented on GitHub (Oct 9, 2016): Of course, the logs! For some reason I didn't look through them. And there's a segmentation fault as it's starting the server. I'll have to tackle that one later on today. Thanks for the help @UltimateByte and @cedarlug

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 9, 2016):

@hatbocs If you're using sourcemod/metamod, the last csgo update broke it. You need to update your addons. Watch out your config files, don't overwrite them. :)

@UltimateByte commented on GitHub (Oct 9, 2016): @hatbocs If you're using sourcemod/metamod, the last csgo update broke it. You need to update your addons. Watch out your config files, don't overwrite them. :)

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 9, 2016):

Merged, we can close now.
To get the update : ./gameserver uf
Thanks for reporting.

@UltimateByte commented on GitHub (Oct 9, 2016): Merged, we can close now. To get the update : ./gameserver uf Thanks for reporting.

kerem commented

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

Author

Owner

@hatbocs commented on GitHub (Oct 9, 2016):

Awesome, thanks for the heads up.

@hatbocs commented on GitHub (Oct 9, 2016): Awesome, thanks for the heads up.

kerem commented

2026-02-27 02:54:05 +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:37 +03:00

[PR #875] [MERGED] Ark server updates to enable the details command #3192