[GH-ISSUE #2148] Teamspeak3 Error #1654

New issue

Closed

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

kerem commented

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

Owner

Originally created by @ZigaZG on GitHub (Jan 4, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2148

So i installed server 2 days ago and it was working fine but i messed up something so i shutdown the server and tryed to install it again but i get this every time i try

[ts3server@vmi234087 ~]$ ./ts3server monitor
[ERROR ] Monitor ts3server: Checking session: Server seems to have died: FAIL
[ INFO ] Stopping ts3server: TeamSpeak 3 Server is already stopped
[  OK  ] Starting ts3server: TeamSpeak 3 Server
[ .... ] Monitor ts3server: Querying port: tcp: MY IP : /1: QUERY                 INGbash: connect: Connection refused
bash: /dev/tcp/207.180.208.30/10011: Connection refused
[ FAIL ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 14/1: WAIT[ FAIL ] Monitor ts3server: Querying port: tcp: 207.180.208.30:10011 : 13/1: WAIT
[ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 15/2: QUERYINGbash: connect: Connection refused
bash: /dev/tcp/207.180.208.30/10011: Connection refused
[ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 30/3: QUERYINGbash: connect: Connection refused
bash: /dev/tcp/207.180.208.30/10011: Connection refused
[ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 45/4: QUERYINGbash: connect: Connection refused
bash: /dev/tcp/207.180.208.30/10011: Connection refused
[ .... ] Monitor ts3server: Querying port: tcp: MY IP : 60/5: QUERYINGbash: connect: Connection refused
bash: /dev/tcp/207.180.208.30/10011: Connection refused
[ FAIL ] Monitor ts3server: Querying port: tcp: MY IP : 74/5: WAIT[ts3server@vmi233/1: WAIT[ FAIL ] Monitor ts3server: Querying port: tcp: MY IP : 1
-bash: [: missing `]'

Originally created by @ZigaZG on GitHub (Jan 4, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2148 So i installed server 2 days ago and it was working fine but i messed up something so i shutdown the server and tryed to install it again but i get this every time i try ``` [ts3server@vmi234087 ~]$ ./ts3server monitor [ERROR ] Monitor ts3server: Checking session: Server seems to have died: FAIL [ INFO ] Stopping ts3server: TeamSpeak 3 Server is already stopped [ OK ] Starting ts3server: TeamSpeak 3 Server [ .... ] Monitor ts3server: Querying port: tcp: MY IP : /1: QUERY INGbash: connect: Connection refused bash: /dev/tcp/207.180.208.30/10011: Connection refused [ FAIL ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 14/1: WAIT[ FAIL ] Monitor ts3server: Querying port: tcp: 207.180.208.30:10011 : 13/1: WAIT [ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 15/2: QUERYINGbash: connect: Connection refused bash: /dev/tcp/207.180.208.30/10011: Connection refused [ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 30/3: QUERYINGbash: connect: Connection refused bash: /dev/tcp/207.180.208.30/10011: Connection refused [ .... ] Monitor ts3server: Querying port: tcp: MY IP:10011 : 45/4: QUERYINGbash: connect: Connection refused bash: /dev/tcp/207.180.208.30/10011: Connection refused [ .... ] Monitor ts3server: Querying port: tcp: MY IP : 60/5: QUERYINGbash: connect: Connection refused bash: /dev/tcp/207.180.208.30/10011: Connection refused [ FAIL ] Monitor ts3server: Querying port: tcp: MY IP : 74/5: WAIT[ts3server@vmi233/1: WAIT[ FAIL ] Monitor ts3server: Querying port: tcp: MY IP : 1 -bash: [: missing `]' ```

kerem

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

closed this issue
added the
type: bug

command: monitor

outcome: unconfirmed

game: Teamspeak 3
labels

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jan 10, 2019):

it is unable to query the port 10011 which might not be the correct port. I would ensure everything is deleted in the directory and start again from scratch. If its still an issue might be something I need to look at

@dgibbs64 commented on GitHub (Jan 10, 2019): it is unable to query the port 10011 which might not be the correct port. I would ensure everything is deleted in the directory and start again from scratch. If its still an issue might be something I need to look at

kerem commented

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

Author

Owner

@ZigaZG commented on GitHub (Jan 10, 2019):

it is unable to query the port 10011 which might not be the correct port. I would ensure everything is deleted in the directory and start again from scratch. If its still an issue might be something I need to look at

I tryed like 5-6 times when i had my vps on Centos 7, now i reinstalled do Debain 9 and now works fine, but also when i 1st tryed installed on Centos 7 also worked but 2nd other times didnt work

@ZigaZG commented on GitHub (Jan 10, 2019): > it is unable to query the port 10011 which might not be the correct port. I would ensure everything is deleted in the directory and start again from scratch. If its still an issue might be something I need to look at I tryed like 5-6 times when i had my vps on Centos 7, now i reinstalled do Debain 9 and now works fine, but also when i 1st tryed installed on Centos 7 also worked but 2nd other times didnt work

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 23, 2019):

I tested this myself and unable to replicate. Placing on hold to close if no updates

@dgibbs64 commented on GitHub (Feb 23, 2019): I tested this myself and unable to replicate. Placing on hold to close if no updates

kerem commented

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

Author

Owner

@ZigaZG commented on GitHub (Feb 23, 2019):

/Close

@ZigaZG commented on GitHub (Feb 23, 2019): /Close

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Feb 23, 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 (Feb 23, 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:18 +03:00

[PR #1655] [MERGED] Disabled Lua AutoRefresh #3384