starred/LinuxGSM

Fork 0

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

[GH-ISSUE #3762] [BUG] jq: error (at <stdin>:0): Expected JSON value (while parsing '') #2473

New issue

Closed

opened 2026-02-27 03:03:11 +03:00 by kerem · 13 comments

kerem commented

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

Owner

Originally created by @Frag1337 on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3762

User Story

Starting my CS:GO server with ./csgoserver start double prints jq: error (at <stdin>:0): Expected JSON value (while parsing '') but the server still successfully starts.

Basic info

Distro: [Debian GNU/Linux 10]
Game: [CS:GO]
Command: [Start]
LinuxGSM version: [v21.5.1]

To Reproduce

Steps to reproduce the behaviour:

Start Server
See double print Error

*******@*******~$ ./csgoserver start
jq: error (at <stdin>:0): Expected JSON value (while parsing '')
jq: error (at <stdin>:0): Expected JSON value (while parsing '')

Originally created by @Frag1337 on GitHub (Jan 21, 2022). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3762 ## User Story Starting my CS:GO server with ```./csgoserver start``` double prints ```jq: error (at <stdin>:0): Expected JSON value (while parsing '')``` but the server still successfully starts. ## Basic info * **Distro:** [Debian GNU/Linux 10] * **Game:** [CS:GO] * **Command:** [Start] * **LinuxGSM version:** [v21.5.1] ## To Reproduce Steps to reproduce the behaviour: 1. Start Server 2. See double print Error ``` *******@*******~$ ./csgoserver start jq: error (at <stdin>:0): Expected JSON value (while parsing '') jq: error (at <stdin>:0): Expected JSON value (while parsing '') ```

kerem

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

closed this issue
added the
type: bug

distro: Debian

command: start
labels

kerem commented

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

Author

Owner

@maclarens commented on GitHub (Jan 28, 2022):

jq: error (at :0): Expected JSON value (while parsing '')
jq: error (at :0): Expected JSON value (while parsing '')
same bug on left 4 dead 2

@maclarens commented on GitHub (Jan 28, 2022): jq: error (at <stdin>:0): Expected JSON value (while parsing '') jq: error (at <stdin>:0): Expected JSON value (while parsing '') same bug on left 4 dead 2

kerem commented

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

Author

Owner

@tt2468 commented on GitHub (Feb 19, 2022):

Same here, Ubuntu 20.04

@tt2468 commented on GitHub (Feb 19, 2022): Same here, Ubuntu 20.04

kerem commented

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

Author

Owner

@maclarens commented on GitHub (Feb 19, 2022):

debian 10 if not apt-get upgrade then fine for me!

@maclarens commented on GitHub (Feb 19, 2022): debian 10 if not apt-get upgrade then fine for me!

kerem commented

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

Author

Owner

@olokos commented on GitHub (Mar 23, 2022):

Same problem here Ubuntu 20.04 with all the latest updates from all corresponding PPAs.

Odd thing is that only first 2 out of 6 servers I have have this bug, all of them being csgoservers.

@olokos commented on GitHub (Mar 23, 2022): Same problem here Ubuntu 20.04 with all the latest updates from all corresponding PPAs. Odd thing is that only first 2 out of 6 servers I have have this bug, all of them being csgoservers.

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Mar 24, 2022):

I hope the connected pr fixes this with the next release.
This can occour as well when no query port is set for a game.
If you have this problem as well with another game (not CSGO) then feel free to test this.

@h3o66 commented on GitHub (Mar 24, 2022): I hope the connected pr fixes this with the next release. This can occour as well when no query port is set for a game. If you have this problem as well with another game (not CSGO) then feel free to test this.

kerem commented

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

Author

Owner

@olokos commented on GitHub (Jun 23, 2022):

I'm pretty sure it did fix the issue, thanks!

@olokos commented on GitHub (Jun 23, 2022): I'm pretty sure it did fix the issue, thanks!

kerem commented

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

Author

Owner

@Fasteroid commented on GitHub (Aug 23, 2022):

~~Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally.~~
~~Ubuntu 20.04.4 LTS~~

~~EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to?~~

@Fasteroid commented on GitHub (Aug 23, 2022): ~~Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally.~~ ~~Ubuntu 20.04.4 LTS~~ ~~EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to?~~

kerem commented

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

Author

Owner

@olokos commented on GitHub (Aug 24, 2022):

Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally. Ubuntu 20.04.4 LTS

EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to?

If you would read the issue, you would know that this bug did not prevent server from starting at all.

to update lgsm you do ./gameserver u - RTFM! :)

@olokos commented on GitHub (Aug 24, 2022): > Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally. Ubuntu 20.04.4 LTS > > EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to? If you would read the issue, you would know that this bug did not prevent server from starting at all. to update lgsm you do `./gameserver u` - RTFM! :)

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Aug 24, 2022):

Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally. Ubuntu 20.04.4 LTS

EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to?

Please condider to get help via the discussions or via the LinuxGSM
Discord server

@h3o66 commented on GitHub (Aug 24, 2022): > Garry's Mod, still experiencing this issue. Some idiot crashed my server and now I can't start it normally. Ubuntu 20.04.4 LTS > > EDIT: My LGSM is still on v21.5.1 and has not updated for some reason... how to? Please condider to get help via the discussions or via the LinuxGSM Discord server

kerem commented

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

Author

Owner

@Fasteroid commented on GitHub (Aug 24, 2022):

to update lgsm you do ./gameserver u - RTFM! :)

This doesn't actually update the lgsm script, I'm still on release v21.5.1 after running this.
I mean, I could always just replace the current linuxgsh.sh with the newest release, but something tells me this isn't how I should be doing it.

If you would read the issue, you would know that this bug did not prevent server from starting at all.

Fair assertion. Turns out the server not starting correctly was unrelated to this (weekly steam maintenence = no workshop collection = missing gm_bigcity). I just assumed my server not starting was due to this bug I never remembered seeing. Apologies for being stupid and not reading the whole issue.

@Fasteroid commented on GitHub (Aug 24, 2022): > to update lgsm you do `./gameserver u` - RTFM! :) This doesn't actually update the lgsm script, I'm still on release v21.5.1 after running this. I mean, I could always just replace the current linuxgsh.sh with the newest release, but something tells me this isn't how I should be doing it. > If you would read the issue, you would know that this bug did not prevent server from starting at all. Fair assertion. Turns out the server not starting correctly was unrelated to this (weekly steam maintenence = no workshop collection = missing gm_bigcity). I just assumed my server not starting was due to this bug I never remembered seeing. Apologies for being stupid and not reading the whole issue.

kerem commented

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

Author

Owner

@olokos commented on GitHub (Aug 30, 2022):

@Fasteroid but you still haven't read the docs or guide at all otherwise you would have known why it doesn't update the script ;)

Anyway, just do:
./gameserver and you will know what to do from there :)

@olokos commented on GitHub (Aug 30, 2022): @Fasteroid but you still haven't read the docs or guide at all otherwise you would have known why it doesn't update the script ;) Anyway, just do: `./gameserver` and you will know what to do from there :)

kerem commented

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

Author

Owner

@Fasteroid commented on GitHub (Aug 31, 2022):

@olokos I do not remember seeing such a command listed in the list you get from running ./gameserver with no args, but perhaps I missed it.

For future reference in case anyone ends up here with the same question, the command to update LGSM itself is ./gameserver update-lgsm, which can be found on the docs here.

Would've at least been nice to link the docs imo, but whatever. Mystery is solved for now.

@Fasteroid commented on GitHub (Aug 31, 2022): @olokos I do not remember seeing such a command listed in the list you get from running `./gameserver` with no args, but perhaps I missed it. For future reference in case anyone ends up here with the same question, the command to update LGSM itself is `./gameserver update-lgsm`, which can be found on the docs [here](https://docs.linuxgsm.com). Would've at least been nice to link the docs imo, but whatever. Mystery is solved for now.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Sep 4, 2023):

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 (Sep 4, 2023): 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.