Many errors in logs- "websocket.NextReader: closing websocket"

We face many entries in logs with errors:
{"timestamp":"2022-10-26 14:04:59.515 +05:00","level":"error","msg":"websocket.NextReader: closing websocket","caller":"app/web_conn.go:830","user_id":"grfze6dkeb8bige7737ibojecr","error":"read tcp> i/o timeout"}
Overwise, Mattermost works normally at this time. Maybe, you knows what errors or bugs can triggers such entries in system log?

Hi. I reported this problem a long time ago to support. The feedback was unsatisfactory: It is nor really a bug as long as everything is working fine. For me it should than be flagged as INFO and not as ERROR.

Hey all, from 7.4 onwards, the log level has been changed to DEBUG again. Revert "Use error log level for websocket timeouts (#19609)" by agnivade · Pull Request #20929 · mattermost/mattermost-server · GitHub

Please ignore the error for the time being. This can normally happen in a healthy system.

Awesome, that’s great to hear, thanks @agnivade for this info :slight_smile: