Hi everyone,
I'm experiencing recurring WebSocket disconnection issues in an Ignition deployment using a Scale-Out architecture. The disconnections appear consistently in the Ignition logs on one of the back-end servers.
Has anyone encountered a similar issue? I'd appreciate any guidance on identifying the root cause and potential steps to resolve it.
Thanks in advance for your help!
This is an image showing the errors in the logs of the back-end server.
Those errors suggest the other end has a more detailed corresponding log message.
Hi Phill,
Thanks for the reply. I understand that the other end might have more detailed logs, but I'm not entirely sure where to look or what exactly I should be checking. Could you please clarify a bit more or point me in the right direction? Any additional guidance would be really helpful.
Best regards.
You received an HTTP 500 error from the other end. Those are typically accompanied by a log message on that end saying why the requested operation died. Match up by approximate timestamp. The error on the other end could be anything, but will include jetty in the backtrace.
Thank you for the information. I'm not entirely sure how to locate or interpret the relevant logs on our end. Could you please guide me on where to look or what specifically I should be searching for in relation to Jetty or the HTTP 500 error? Any pointers would be greatly appreciated.
Same place you found them on the front end. Log into the web interface on the backend. Go to Status => Logs. Scroll back to the approximate time of that error and look for suspicious entries. There's no magic.
If a lot of time has passed, it may be easier to download the logs in SQLite format and review with a SQLite browser. (Or use the "Kindling" app.)
