starred/LinuxGSM

Fork 0

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

[GH-ISSUE #2570] Teamspeak3 error: list of session leaders OR effective group names must follow -g #1873

New issue

Closed

opened 2026-02-27 02:59:30 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @olokos on GitHub (Oct 30, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2570

User Story

Since a month or so I have noticed that my ts3server is spewing errors when doing ./ts3server start
Specifically error
error: list of session leaders OR effective group names must follow -g
Most likely due to recent lgsm updates

Basic info

Distro: Ubuntu 18.04 LTS running kernel 5
Game: Teamspeak3 server
Command: start

Further Information

I am running latest php7.3, MySQL8, each and every package is up-to-date.
This bug does not occur with csgoserver
This bug does occur even when using the latest _default.cfg

To Reproduce

Steps to reproduce the behaviour:

Go to ts3 server home directory
do ./ts3server start
Error pops up

Expected behaviour

Start without this error.
Because of this bug rc.local fails to continue with the rest of its code

Here's a screenshot, which shows the issue nicely
https://imgur.com/a/zSadcmd

Originally created by @olokos on GitHub (Oct 30, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2570 ## User Story Since a month or so I have noticed that my ts3server is spewing errors when doing ./ts3server start Specifically error error: list of session leaders OR effective group names must follow -g Most likely due to recent lgsm updates ## Basic info * Distro: Ubuntu 18.04 LTS running kernel 5 * Game: Teamspeak3 server * Command: start ## Further Information I am running latest php7.3, MySQL8, each and every package is up-to-date. This bug does not occur with csgoserver This bug does occur even when using the latest _default.cfg ## To Reproduce Steps to reproduce the behaviour: 1. Go to ts3 server home directory 2. do ./ts3server start 3. Error pops up ## Expected behaviour Start without this error. Because of this bug rc.local fails to continue with the rest of its code Here's a screenshot, which shows the issue nicely https://imgur.com/a/zSadcmd

kerem

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

closed this issue
added the
type: bug
label

kerem commented

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

Author

Owner

@issue-label-bot[bot] commented on GitHub (Oct 30, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.83. 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 (Oct 30, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.83. 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:31 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 30, 2019):

Thanks. I am aware of this issue. It will be fixed in the next release. Ts3 will be converted to use tmux.

@dgibbs64 commented on GitHub (Oct 30, 2019): Thanks. I am aware of this issue. It will be fixed in the next release. Ts3 will be converted to use tmux.

kerem commented

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

Author

Owner

@olokos commented on GitHub (Oct 31, 2019):

Glad to hear that. Is there any workaround for now?

@olokos commented on GitHub (Oct 31, 2019): Glad to hear that. Is there any workaround for now?

kerem commented

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

Author

Owner

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

There is no workaround. However, the message does not affect the running of the server in any way.

@dgibbs64 commented on GitHub (Oct 31, 2019): There is no workaround. However, the message does not affect the running of the server in any way.

kerem commented

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

Author

Owner

@olokos commented on GitHub (Nov 1, 2019):

Well, because of this rc.local stops executing and so does its service rc.local.service.d. If there's anything after the code of running the server then anything below that line won't be ran by rc.local.

@olokos commented on GitHub (Nov 1, 2019): Well, because of this rc.local stops executing and so does its service rc.local.service.d. If there's anything after the code of running the server then anything below that line won't be ran by rc.local.

kerem commented

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

Author

Owner

@olokos commented on GitHub (Nov 4, 2019):

@dgibbs64 this issue prevents rc.local from executing.
If there's any lines below lgsm server, then those are ignored as rc.local fails on lgsm.
While it does not affect running of the particular lgsm server, it does disrupt proper autostart of programs on the entire server machine.

@olokos commented on GitHub (Nov 4, 2019): @dgibbs64 this issue prevents rc.local from executing. If there's any lines below lgsm server, then those are ignored as rc.local fails on lgsm. While it does not affect running of the particular lgsm server, it does disrupt proper autostart of programs on the entire server machine.