New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gsquery unable to receive - Wolfenstein: Enemy Territory #1753

Closed
jimwald1221 opened this Issue Dec 28, 2017 · 6 comments

Comments

3 participants
@jimwald1221
Contributor

jimwald1221 commented Dec 28, 2017

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.

@jimwald1221 jimwald1221 changed the title from gsquery unable to receive to gsquery unable to receive - Wolfenstein: Enemy Territory Dec 28, 2017

@UltimateByte

This comment has been minimized.

Collaborator

UltimateByte commented 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.

@jimwald1221

This comment has been minimized.

Contributor

jimwald1221 commented 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.

@UltimateByte

This comment has been minimized.

Collaborator

UltimateByte commented Dec 28, 2017

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

@jimwald1221

This comment has been minimized.

Contributor

jimwald1221 commented Dec 29, 2017

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

engine="idtech2"

@dgibbs64

This comment has been minimized.

Member

dgibbs64 commented 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

This comment has been minimized.

Member

dgibbs64 commented 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 added a commit that referenced this issue Mar 12, 2018

@dgibbs64 dgibbs64 closed this Mar 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment