Actions
action #18048
closed[tools][openqa-monitoring] AMQP connection closed
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-03-27
Due date:
% Done:
0%
Estimated time:
Description
observation¶
[Mon Mar 27 10:11:24 2017] [25848:warn] AMQP connection closed
[Mon Mar 27 10:11:28 2017] [25898:warn] AMQP connection closed
[Mon Mar 27 10:11:45 2017] [24427:warn] AMQP connection closed
[Mon Mar 27 10:11:55 2017] [27069:warn] AMQP connection closed
[Mon Mar 27 10:12:03 2017] [25967:warn] AMQP connection closed
[Mon Mar 27 10:12:03 2017] [25704:warn] AMQP connection closed
[Mon Mar 27 10:12:03 2017] [22927:warn] AMQP connection closed
[Mon Mar 27 10:12:03 2017] [22869:warn] AMQP connection closed
[Mon Mar 27 10:12:29 2017] [25848:warn] AMQP connection closed
[Mon Mar 27 10:12:33 2017] [25711:warn] AMQP connection closed
[Mon Mar 27 10:12:33 2017] [25898:warn] AMQP connection closed
[Mon Mar 27 10:13:00 2017] [27069:warn] AMQP connection closed
[Mon Mar 27 10:13:08 2017] [22927:warn] AMQP connection closed
[Mon Mar 27 10:13:08 2017] [25967:warn] AMQP connection closed
[Mon Mar 27 10:13:08 2017] [25704:warn] AMQP connection closed
[and many more…]
suggestion¶
I guess the connection to the AMQP sockets get not closed after use and/or timeout after some time. Maybe a proper close of these sockets is required. Maybe the timeout for it is to low or maybe it's a whole other problem.
Since this is now a known issue, I'll provide a PR for the logwarn-script of okurz to ignore this warning.
Updated by okurz about 7 years ago
Updated by coolo over 6 years ago
- Status changed from New to Resolved
this happens if the server heartbeat it shorter than the client heartbeat. This can be fixed since PR#1479 - but I haven't seen it for a while on osd, and is fixed on o3
Updated by okurz over 6 years ago
- Copied to action #29481: [openqa-monitoring] DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127)," added
Actions