starred/LinuxGSM

Fork 0

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

[GH-ISSUE #2124] jq: Unknown option -sRr (during update-lgsm) #1638

New issue

Closed

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

kerem commented

2026-02-27 02:58:15 +03:00

Owner

Originally created by @jrmain on GitHub (Dec 16, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2124

Both my LGSM servers update themselves automatically and I get cron email showing what happened during the updates. This morning, both showed output similar to this:

 [K[ .... ] Update LinuxGSM ut2k4server: Updating LinuxGSM
    checking config _default.cfg...UPDATE
    fetching _default.cfg...OK
jq: Unknown option -sRr
Use jq --help for help with command-line options,
or see the jq documentation at http://stedolan.github.com/jq
jq: Unknown option -sRr
Use jq --help for help with command-line options,
or see the jq documentation at http://stedolan.github.com/jq
  [K[ .... ] Alert ut2k4server: Sending Discord alertparse error: Expected value before ',' at line 9, column 18
  [K[ FAIL ] Alert ut2k4server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"}
    checking linuxgsm.sh...UPDATE
    fetching linuxgsm.sh...OK
    checking ut2k4server...UPDATE
    backup ut2k4server...OK

The rest looks normal. I re-ran update-lgsm on both servers but everything looked fine and up to date. Both servers are running normally. So, whatever happened, it doesn't appear to have caused any lasting problems.

I appear to be running jr version 1.3 on the server, which is Ubuntu 14. The LGSM servers are UT2004 and UT99.

Originally created by @jrmain on GitHub (Dec 16, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2124 Both my LGSM servers update themselves automatically and I get cron email showing what happened during the updates. This morning, both showed output similar to this: ``` [K[ .... ] Update LinuxGSM ut2k4server: Updating LinuxGSM checking config _default.cfg...UPDATE fetching _default.cfg...OK jq: Unknown option -sRr Use jq --help for help with command-line options, or see the jq documentation at http://stedolan.github.com/jq jq: Unknown option -sRr Use jq --help for help with command-line options, or see the jq documentation at http://stedolan.github.com/jq [K[ .... ] Alert ut2k4server: Sending Discord alertparse error: Expected value before ',' at line 9, column 18 [K[ FAIL ] Alert ut2k4server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"} checking linuxgsm.sh...UPDATE fetching linuxgsm.sh...OK checking ut2k4server...UPDATE backup ut2k4server...OK ``` The rest looks normal. I re-ran update-lgsm on both servers but everything looked fine and up to date. Both servers are running normally. So, whatever happened, it doesn't appear to have caused any lasting problems. I appear to be running jr version 1.3 on the server, which is Ubuntu 14. The LGSM servers are UT2004 and UT99.

kerem

2026-02-27 02:58:15 +03:00

closed this issue
added the
type: bug

distro: Ubuntu

outcome: wontfix
labels

kerem commented

2026-02-27 02:58:15 +03:00

Author

Owner

@h3o66 commented on GitHub (Jan 18, 2019):

https://stedolan.github.io/jq/manual/v1.3/

i would guess that this is caused by the fact that the old jq release does not support the parameters to be written "as one parameter"

But in my opinion i would say that ubuntu 14 is almost out of support, so does this need any attention ?

See:
https://www.ubuntu.com/about/release-cycle

Did you also consider to update to a newer ubuntu release ?

jq 1.3 Manual

Ubuntu release cycle | Ubuntu
Overview of the Ubuntu release cycle - maintenance, support and security coverage, lifetime, upgrade paths, kernel versions and the range of editions and images published by Canonical.

@h3o66 commented on GitHub (Jan 18, 2019): https://stedolan.github.io/jq/manual/v1.3/ i would guess that this is caused by the fact that the old jq release does not support the parameters to be written "as one parameter" But in my opinion i would say that ubuntu 14 is almost out of support, so does this need any attention ? See: https://www.ubuntu.com/about/release-cycle Did you also consider to update to a newer ubuntu release ? <blockquote><div><strong><a href="https://stedolan.github.io/jq/manual/v1.3/">jq 1.3 Manual</a></strong></div></blockquote> <blockquote><div><strong><a href="https://www.ubuntu.com/about/release-cycle">Ubuntu release cycle | Ubuntu</a></strong></div><div>Overview of the Ubuntu release cycle - maintenance, support and security coverage, lifetime, upgrade paths, kernel versions and the range of editions and images published by Canonical.</div></blockquote>

kerem commented

2026-02-27 02:58:15 +03:00

Author

Owner

@h3o66 commented on GitHub (Jan 18, 2019):

to add:
this seems to be only a problem of the discord alert
lgsm/functions/alert_discord.sh

you could try to change "jq -sRr" to "jq -s -R -r" and try again if it works

@h3o66 commented on GitHub (Jan 18, 2019): to add: this seems to be only a problem of the discord alert lgsm/functions/alert_discord.sh you could try to change "jq -sRr" to "jq -s -R -r" and try again if it works

kerem commented

2026-02-27 02:58:15 +03:00

Author

Owner

@jrmain commented on GitHub (Jan 19, 2019):

Actually, for whatever reason, this problem seemed to resolve itself at the next update. At least it's not currently happening.

As for upgrading to a newer Ubuntu release: assuming I had done that and it fixed the problem, you folks would need to review and update the requirements for LinuxGSM.

@jrmain commented on GitHub (Jan 19, 2019): Actually, for whatever reason, this problem seemed to resolve itself at the next update. At least it's not currently happening. As for upgrading to a newer Ubuntu release: assuming I had done that and it fixed the problem, you folks would need to review and update the requirements for LinuxGSM.

kerem commented

2026-02-27 02:58:15 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 31, 2019):

Ubuntu 14.04 LTS is now out of support. I will not be making changes to resolve this.

@dgibbs64 commented on GitHub (Mar 31, 2019): Ubuntu 14.04 LTS is now out of support. I will not be making changes to resolve this.

kerem commented

2026-02-27 02:58:15 +03:00

Author

Owner

@Redeye123 commented on GitHub (Oct 27, 2019):

to add:
this seems to be only a problem of the discord alert
lgsm/functions/alert_discord.sh

you could try to change "jq -sRr" to "jq -s -R -r" and try again if it works

Im so thankfull to you since this just worked to solve it at my end on debian Again thx

@Redeye123 commented on GitHub (Oct 27, 2019): > to add: > this seems to be only a problem of the discord alert > lgsm/functions/alert_discord.sh > > you could try to change "jq -sRr" to "jq -s -R -r" and try again if it works Im so thankfull to you since this just worked to solve it at my end on debian Again thx

kerem referenced this issue

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

[PR #1638] [MERGED] Improved graceful shutdown #3377