Actions
action #41222
closedA lot of occurences of 'websocket connection closed'
Start date:
2018-09-19
Due date:
% Done:
0%
Estimated time:
Description
Apparently we are killing worker connections somehow, in just two days there is a huge amount of connection closed.
On osd:
grep -r 'websocket connection closed' /var/log/openqa
[2018-09-18T02:50:06.0830 CEST] [info] Worker 251 websocket connection closed - 1005
[2018-09-18T02:53:48.0273 CEST] [info] Worker 896 websocket connection closed - 1005
[2018-09-18T02:59:53.0594 CEST] [info] Worker 968 websocket connection closed - 1005
[2018-09-18T03:13:19.0889 CEST] [info] Worker 969 websocket connection closed - 1006
[2018-09-18T04:27:33.0469 CEST] [info] Worker 895 websocket connection closed - 1006
[2018-09-18T04:29:24.0790 CEST] [info] Worker 959 websocket connection closed - 1006
[2018-09-18T04:29:45.0718 CEST] [info] Worker 649 websocket connection closed - 1006
[2018-09-18T04:30:11.0060 CEST] [info] Worker 969 websocket connection closed - 1006
[2018-09-18T04:30:11.0898 CEST] [info] Worker 1119 websocket connection closed - 1006
[2018-09-18T04:30:15.0991 CEST] [info] Worker 406 websocket connection closed - 1006
grep -r 'websocket connection closed' /var/log/openqa | wc -l
708
To note, it's not when we are closing the connection when worker is thought dead (that should give 1008 as code) https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebSockets/Server.pm#L202
Actions