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

[BUG] WebSocket not in appropriate state for liveness check... #18

Open
emirhnkoc opened this issue Mar 23, 2024 · 1 comment
Open

[BUG] WebSocket not in appropriate state for liveness check... #18

emirhnkoc opened this issue Mar 23, 2024 · 1 comment

Comments

@emirhnkoc
Copy link

better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection... 
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
@FungY911
Copy link
Owner

Duplaticate of #13 (comment)

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

No branches or pull requests

2 participants