starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1753] gsquery unable to receive - Wolfenstein: Enemy Territory #1369

New issue

Closed

opened 2026-02-27 02:56:44 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:56:44 +03:00

Owner

Originally created by @ghost on GitHub (Dec 28, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1753

While attempting to monitor a Wolfenstein ET server, gsquery reports it's "unable to receive". The engine seems to be the culprit. "idtech3" (default) doesn't provide a response but "idtech2" does. In what aspects is the engine important to other functions? Any feedback on this particular setting would be helpful.

Originally created by @ghost on GitHub (Dec 28, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1753 While attempting to monitor a Wolfenstein ET server, gsquery reports it's "unable to receive". The engine seems to be the culprit. "idtech3" (default) doesn't provide a response but "idtech2" does. In what aspects is the engine important to other functions? Any feedback on this particular setting would be helpful.

kerem

2026-02-27 02:56:44 +03:00

closed this issue
added the
type: bug

outcome: issue resolved
labels

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@UltimateByte commented on GitHub (Dec 28, 2017):

The query string is a bit different between the two engines.
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21-L28

You can try playing around with them and see if you come to some conclusions.

What about details command? The issue could also come from here: does it work as intended?
Provide a postdetails link output to let us check.

@UltimateByte commented on GitHub (Dec 28, 2017): The query string is a bit different between the two engines. https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21-L28 You can try playing around with them and see if you come to some conclusions. What about details command? The issue could also come from here: does it work as intended? Provide a postdetails link output to let us check.

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@ghost commented on GitHub (Dec 28, 2017):

Seems the result of what I was trying to do is okay. No side effects so far.

https://hastebin.com/raw/yazugaloju

I changed the engine in the config and things seems to be responding okay. Monitor works and there don't seem to be errors of other commands so far.

@ghost commented on GitHub (Dec 28, 2017): Seems the result of what I was trying to do is okay. No side effects so far. https://hastebin.com/raw/yazugaloju I changed the engine in the config and things seems to be responding okay. Monitor works and there don't seem to be errors of other commands so far.

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@UltimateByte commented on GitHub (Dec 28, 2017):

Good to know.
Could please you share you changes so that we can reproduce it and fix it natively inside LGSM?

@UltimateByte commented on GitHub (Dec 28, 2017): Good to know. Could please you share you changes so that we can reproduce it and fix it natively inside LGSM?

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@ghost commented on GitHub (Dec 29, 2017):

I just defined the engine variable in my config to "idtech2".

engine="idtech2"

@ghost commented on GitHub (Dec 29, 2017): I just defined the engine variable in my config to "idtech2". engine="idtech2"

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 29, 2017):

The W:ET engine is idtech3 but queries on idtech2 engine...How odd. We will need to put a specific statement in for W:ET as we should not change the engine variable as it would be inaccurate.

@dgibbs64 commented on GitHub (Dec 29, 2017): The W:ET engine is idtech3 but queries on idtech2 engine...How odd. We will need to put a specific statement in for W:ET as we should not change the engine variable as it would be inaccurate.

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 12, 2018):

There appears to be a bug in gsquery that is nearly a year old https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21

the querys are listed the wrong way around.

@dgibbs64 commented on GitHub (Mar 12, 2018): There appears to be a bug in gsquery that is nearly a year old https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21 the querys are listed the wrong way around.

kerem commented

2026-02-27 02:56:44 +03:00

Author

Owner

@lock[bot] commented on GitHub (Mar 12, 2019):

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 (Mar 12, 2019): 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.