starred/LinuxGSM

Fork 0

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

[GH-ISSUE #2342] Command monitor broken on teamspeak #1757

New issue

Closed

opened 2026-02-27 02:58:53 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @xopez on GitHub (May 6, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2342

User Story

Ihave installed the latest LGSM version. I run the command ./ts3server monitor every two minutes via cron. The Log says that the tcp query is failing.

Basic info

Distro: Ubuntu 18.04.2 LTS
Game: Teamspeak
Command: Monitor

Further Information

I found the issue #2335 which might be related.

To Reproduce

Log from file:

May 07 00:14:02.210 ts3server: MONITOR: INFO: Checking session: CHECKING
May 07 00:14:02.714 ts3server: MONITOR: PASS: Checking session: OK
May 07 00:14:03.217 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 1 : QUERYING
May 07 00:14:03.722 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 1: FAIL
May 07 00:14:19.286 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 2 : QUERYING
May 07 00:14:19.791 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 2: FAIL
May 07 00:14:35.313 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 3 : QUERYING
May 07 00:14:35.819 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 3: FAIL
May 07 00:14:51.345 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 4 : QUERYING
May 07 00:14:51.851 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 4: FAIL

Log from console:

teamspeak@mightful-noobs:~$ ./ts3server monitor
[  OK  ] Monitor ts3server: Checking session: OK
[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 0/1: QUERYINGbash: : Name or service not known
bash: /dev/tcp//10011: Invalid argument
[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 15/2: QUERYINGbash: : Name or service not known
bash: /dev/tcp//10011: Invalid argument
[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 30/3: QUERYINGbash: : Name or service not known
bash: /dev/tcp//10011: Invalid argument
[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 45/4: QUERYINGbash: : Name or service not known
bash: /dev/tcp//10011: Invalid argument
[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 60/5: QUERYINGbash: : Name or service not known
bash: /dev/tcp//10011: Invalid argument
[ FAIL ] Monitor ts3server: Querying port: tcp: :10011 : 74/5: WAIT

Port bindings:

teamspeak@mightful-noobs:~$ netstat -tulpn | grep ts3server
tcp        0      0 0.0.0.0:10022           0.0.0.0:*               LISTEN      9787/./ts3server
tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      9787/./ts3server
tcp        0      0 0.0.0.0:10011           0.0.0.0:*               LISTEN      9787/./ts3server
tcp6       0      0 :::10022                :::*                    LISTEN      9787/./ts3server
tcp6       0      0 :::30033                :::*                    LISTEN      9787/./ts3server
tcp6       0      0 :::10011                :::*                    LISTEN      9787/./ts3server
udp        0      0 0.0.0.0:9987            0.0.0.0:*                           9787/./ts3server
udp6       0      0 :::9987                 :::*                                9787/./ts3server

ts3server.ini:

machine_id=
default_voice_port=9987
voice_ip=
licensepath=
filetransfer_port=30033
filetransfer_ip=
query_port=10011
query_ip=0.0.0.0, ::
query_ip_whitelist=query_ip_whitelist.txt
query_ip_blacklist=query_ip_blacklist.txt
dbplugin=ts3db_sqlite3
dbpluginparameter=
dbsqlpath=sql/
dbsqlcreatepath=create_sqlite/
dbconnections=10
logpath=logs
logquerycommands=0
dbclientkeepdays=30
logappend=0
query_skipbruteforcecheck=0
query_buffer_mb=20
http_proxy=
license_accepted=1
serverquerydocs_path=serverquerydocs/
query_ssh_ip=0.0.0.0, ::
query_ssh_port=10022
query_protocols=raw,ssh
query_ssh_rsa_host_key=ssh_host_rsa_key
query_timeout=300

Steps to reproduce the behaviour:

Install ts3server
start the server
do the monitor command an see it failing

Expected behaviour

The server should be queried successfully

Originally created by @xopez on GitHub (May 6, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2342 ## User Story Ihave installed the latest LGSM version. I run the command `./ts3server monitor` every two minutes via cron. The Log says that the tcp query is failing. ## Basic info * Distro: Ubuntu 18.04.2 LTS * Game: Teamspeak * Command: Monitor ## Further Information I found the issue #2335 which might be related. ## To Reproduce Log from file: ``` May 07 00:14:02.210 ts3server: MONITOR: INFO: Checking session: CHECKING May 07 00:14:02.714 ts3server: MONITOR: PASS: Checking session: OK May 07 00:14:03.217 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 1 : QUERYING May 07 00:14:03.722 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 1: FAIL May 07 00:14:19.286 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 2 : QUERYING May 07 00:14:19.791 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 2: FAIL May 07 00:14:35.313 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 3 : QUERYING May 07 00:14:35.819 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 3: FAIL May 07 00:14:51.345 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 4 : QUERYING May 07 00:14:51.851 ts3server: MONITOR: INFO: Querying port: tcp: :10011 : 4: FAIL ``` Log from console: ``` teamspeak@mightful-noobs:~$ ./ts3server monitor [ OK ] Monitor ts3server: Checking session: OK [ .... ] Monitor ts3server: Querying port: tcp: :10011 : 0/1: QUERYINGbash: : Name or service not known bash: /dev/tcp//10011: Invalid argument [ .... ] Monitor ts3server: Querying port: tcp: :10011 : 15/2: QUERYINGbash: : Name or service not known bash: /dev/tcp//10011: Invalid argument [ .... ] Monitor ts3server: Querying port: tcp: :10011 : 30/3: QUERYINGbash: : Name or service not known bash: /dev/tcp//10011: Invalid argument [ .... ] Monitor ts3server: Querying port: tcp: :10011 : 45/4: QUERYINGbash: : Name or service not known bash: /dev/tcp//10011: Invalid argument [ .... ] Monitor ts3server: Querying port: tcp: :10011 : 60/5: QUERYINGbash: : Name or service not known bash: /dev/tcp//10011: Invalid argument [ FAIL ] Monitor ts3server: Querying port: tcp: :10011 : 74/5: WAIT ``` Port bindings: ``` teamspeak@mightful-noobs:~$ netstat -tulpn | grep ts3server tcp 0 0 0.0.0.0:10022 0.0.0.0:* LISTEN 9787/./ts3server tcp 0 0 0.0.0.0:30033 0.0.0.0:* LISTEN 9787/./ts3server tcp 0 0 0.0.0.0:10011 0.0.0.0:* LISTEN 9787/./ts3server tcp6 0 0 :::10022 :::* LISTEN 9787/./ts3server tcp6 0 0 :::30033 :::* LISTEN 9787/./ts3server tcp6 0 0 :::10011 :::* LISTEN 9787/./ts3server udp 0 0 0.0.0.0:9987 0.0.0.0:* 9787/./ts3server udp6 0 0 :::9987 :::* 9787/./ts3server ``` ts3server.ini: ``` machine_id= default_voice_port=9987 voice_ip= licensepath= filetransfer_port=30033 filetransfer_ip= query_port=10011 query_ip=0.0.0.0, :: query_ip_whitelist=query_ip_whitelist.txt query_ip_blacklist=query_ip_blacklist.txt dbplugin=ts3db_sqlite3 dbpluginparameter= dbsqlpath=sql/ dbsqlcreatepath=create_sqlite/ dbconnections=10 logpath=logs logquerycommands=0 dbclientkeepdays=30 logappend=0 query_skipbruteforcecheck=0 query_buffer_mb=20 http_proxy= license_accepted=1 serverquerydocs_path=serverquerydocs/ query_ssh_ip=0.0.0.0, :: query_ssh_port=10022 query_protocols=raw,ssh query_ssh_rsa_host_key=ssh_host_rsa_key query_timeout=300 ``` ## Steps to reproduce the behaviour: 1. Install ts3server 2. start the server 3. do the monitor command an see it failing ## Expected behaviour The server should be queried successfully

kerem

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

closed this issue
added the
priority
label

kerem commented

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

Author

Owner

@0DUDDU commented on GitHub (May 12, 2019):

After some test i saw a difference between the result of my test and yours
When i test, i get this log

[ OK ] Monitor ts3server: Querying port: tcp: 0.0.0.0:10011 : 0/1: OK

In your log the IP is missing before the port

[ .... ] Monitor ts3server: Querying port: tcp: :10011 : 0/1: QUERYING

Can you use the postdetails command and give the url

@0DUDDU commented on GitHub (May 12, 2019): After some test i saw a difference between the result of my test and yours When i test, i get this log > [ OK ] Monitor ts3server: Querying port: tcp: **0.0.0.0:10011** : 0/1: OK In your log the IP is missing before the port >[ .... ] Monitor ts3server: Querying port: tcp: **:10011** : 0/1: QUERYING Can you use the postdetails command and give the url

kerem commented

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

Author

Owner

@xopez commented on GitHub (May 12, 2019):

Sure: https://hastebin.com/egepihusox
I should mention that its happen with latest lgsm version too.

hastebin

@xopez commented on GitHub (May 12, 2019): Sure: https://hastebin.com/egepihusox I should mention that its happen with latest lgsm version too. <blockquote><div><strong><a href="https://hastebin.com/egepihusox">hastebin</a></strong></div></blockquote>

kerem commented

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

Author

Owner

@0DUDDU commented on GitHub (May 12, 2019):

Your voice_ip config is void, you should set it to the same as query_ip or any other ip
for now, the script take voice_ip not query_ip for all thing related to ip

@0DUDDU commented on GitHub (May 12, 2019): Your `voice_ip` config is void, you should set it to the same as `query_ip` or any other ip for now, the script take `voice_ip` not `query_ip` for all thing related to ip

kerem commented

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

Author

Owner

@xopez commented on GitHub (May 12, 2019):

Ok, I don't know why I messed up.
Set voice_ip to 0.0.0.0, :: and now it works.

@xopez commented on GitHub (May 12, 2019): Ok, I don't know why I messed up. Set `voice_ip` to `0.0.0.0, ::` and now it works.

kerem commented

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

Author

Owner

@xopez commented on GitHub (May 12, 2019):

Closing the issue now

@xopez commented on GitHub (May 12, 2019): Closing the issue now

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (May 20, 2020):

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 (May 20, 2020): 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:54:23 +03:00

[PR #1757] [MERGED] Add Stationeers #3406