Latest "FEMS-Backports" issues after Update

1

Hello ! :slight_smile:

After Updating to develop i now get this Issue:

May 25 19:42:20 java[3884251]: 2025-05-25T19:42:20,624 [thread-1] ERROR [cket.impl.UiWebsocketValidator] ### UiWebsocketValidator
May 25 19:42:20 java[3884251]: 2025-05-25T19:42:20,624 [thread-1] ERROR [cket.impl.UiWebsocketValidator] ### NO UI CONNECTIONS SINCE 120 SECONDS
May 25 19:42:20 java[3884251]: 2025-05-25T19:42:20,624 [thread-1] ERROR [cket.impl.UiWebsocketValidator] ### SYSTEM EXIT!
May 25 19:42:20 java[3884251]: 2025-05-25T19:42:20,624 [thread-1] ERROR [cket.impl.UiWebsocketValidator] ### UiWebsocketValidator
May 25 19:42:21 systemd[1]: openems-backend.service: Main process exited, code=exited, status=1/FAILURE
May 25 19:42:21 systemd[1]: openems-backend.service: Failed with result 'exit-code'.
May 25 19:42:21 systemd[1]: openems-backend.service: Consumed 10.992s CPU time.

What needs to be done to resolve this?

Greetings!

2

Okay, nevermind - found out:

public class UiWebsocketValidator implements Runnable {

	private static final int FAULT_LIMIT = -1;

solves this Issue.

3

Ah, thanks… I meant to leave this out of the Backport, but it’s in fact a “feature” we needed in production, because sometimes the WebSocketServer would suddenly loose all connections and won’t allow reconnects before restarting OpenEMS Backend.

This needs documentation, though… :expressionless:

1 Like