starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1103] gsquery.py failed to query: ERROR: Unable to receive #868

New issue

Closed

opened 2026-02-27 02:54:00 +03:00 by kerem · 9 comments

kerem commented

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

Owner

Originally created by @silelmot on GitHub (Oct 5, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1103

Today it seemed, there was installed an update of the ins-server files,
but since then i get an error on one of my servers, running this:

gsquery.py failed to query: ERROR: Unable to receive

Distro Details

Distro: Debian GNU/Linux 8.6 (jessie)
Arch: x86_64
Kernel: 3.16.0-4-amd64
Hostname: server
tmux: tmux 1.9
GLIBC: 2.19

i tested with ports 27016 and 27017, both the same, but running on 27015 the monitoring is working
the servers are running since several months with no errors, just since the update...
any idea what to do, what could help?
thank you very much!

Originally created by @silelmot on GitHub (Oct 5, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1103 Today it seemed, there was installed an update of the ins-server files, but since then i get an error on one of my servers, running this: gsquery.py failed to query: ERROR: Unable to receive # Distro Details Distro: Debian GNU/Linux 8.6 (jessie) Arch: x86_64 Kernel: 3.16.0-4-amd64 Hostname: server tmux: tmux 1.9 GLIBC: 2.19 i tested with ports 27016 and 27017, both the same, but running on 27015 the monitoring is working the servers are running since several months with no errors, just since the update... any idea what to do, what could help? thank you very much!

kerem closed this issue

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

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 5, 2016):

./gameserver pd
also coudl use some log files that will help figure out the issue :)

@dgibbs64 commented on GitHub (Oct 5, 2016): `./gameserver pd` also coudl use some log files that will help figure out the issue :)

kerem commented

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

Author

Owner

@WriggleDev commented on GitHub (Oct 7, 2016):

I am getting this on my 7dtd server
http://hastebin.com/evifoxobaj

Which log files will you require for investigation?

@WriggleDev commented on GitHub (Oct 7, 2016): I am getting this on my 7dtd server http://hastebin.com/evifoxobaj Which log files will you require for investigation?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 7, 2016):

"Change ports by editing the parameters in:
UNKNOWN"

It'as a least enough to explain why LGSM will only be able to monitor on port 27015.
Config file location or name changed ?

@UltimateByte commented on GitHub (Oct 7, 2016): "Change ports by editing the parameters in: UNKNOWN" It'as a least enough to explain why LGSM will only be able to monitor on port 27015. Config file location or name changed ?

kerem commented

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

Author

Owner

@WriggleDev commented on GitHub (Oct 7, 2016):

I configured my port in the sdtdserver file and it's trying to connect to server. But failing. Tried setting it to 27018 as well as my telnet port to see if it made a difference.

@WriggleDev commented on GitHub (Oct 7, 2016): I configured my port in the sdtdserver file and it's trying to connect to server. But failing. Tried setting it to 27018 as well as my telnet port to see if it made a difference.

kerem commented

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

Author

Owner

@silelmot commented on GitHub (Oct 12, 2016):

any solution yet?

@silelmot commented on GitHub (Oct 12, 2016): any solution yet?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 12, 2016):

@Maygus @silelmot
No solution without your config file output, that is most likely the issue here, as i suggested with my previous post.
We also need to know your config file name and location. As i said, your config file is not being recognized by LGSM, and you're both the only ones complaining about such an issue. So LGSM can't know what port to check for listening.

So until proven otherwise, it's a user based issue.

@UltimateByte commented on GitHub (Oct 12, 2016): @Maygus @silelmot No solution without your config file output, that is most likely the issue here, as i suggested with my previous post. We also need to know your config file name and location. As i said, your config file is not being recognized by LGSM, and you're both the only ones complaining about such an issue. So LGSM can't know what port to check for listening. So until proven otherwise, it's a user based issue.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 20, 2016):

Closing as no feedback.

@UltimateByte commented on GitHub (Oct 20, 2016): Closing as no feedback.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Oct 20, 2016):

Not a user issue, see https://github.com/GameServerManagers/LinuxGSM/issues/1139 for more and to learn how to report an issue as well.

@UltimateByte commented on GitHub (Oct 20, 2016): Not a user issue, see https://github.com/GameServerManagers/LinuxGSM/issues/1139 for more and to learn how to report an issue as well.

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

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 (Jul 19, 2018): 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.