Skip to content
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

Notice when Halflife websocket goes away #11

Open
tripleee opened this issue May 24, 2018 · 1 comment
Open

Notice when Halflife websocket goes away #11

tripleee opened this issue May 24, 2018 · 1 comment

Comments

@tripleee
Copy link
Member

If the websocket disappears, PulseMonitor should notice, and perhaps try restarting.

Currently, it looks like it simply keeps listening to the old, now dead websocket forever if Halflife is restarted.

There is also the scenario of Halflife dying, so it should probably not attempt to restart too often if the websocket cannot be opened in the first place.

@tripleee
Copy link
Member Author

tripleee commented Jun 6, 2018

When I shut down Halflife for an update yesterday, there was a log message.

2018-06-05 12:24:34,136:WebsocketListener:A websocket error occurred on websocket 'ws://ec2-52-208-37-129.eu-west-1.compute.amazonaws.com:8888/':
2018-06-05 12:24:34,136:WebsocketListener:Connection is already closed.

https://chat.stackexchange.com/transcript/message/44984344#44984344

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

No branches or pull requests

2 participants