Project

General

Profile

Actions

action #18052

closed

[tools][openqa-monitoring] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1

Added by nicksinger about 7 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-03-27
Due date:
% Done:

0%

Estimated time:

Description

observation

[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[Mon Mar 27 12:11:02 2017] [1401:warn] Error on AMQP channel received: Failed closing channel: Unknown channel id received: 1
[and many moreā€¦]

suggestion

Someone seems to use the channel 1 which is obviously not known to AMQP. Further investigation is needed to find the root cause of the problem.
Since this is now a known issue, I'll provide a PR for the logwarn-script of okurz to ignore this warning.

Actions #2

Updated by coolo over 6 years ago

  • Status changed from New to Rejected

this is deep within the used library - no way we're going to hack AMQP protocol

Actions #3

Updated by okurz over 6 years ago

  • Status changed from Rejected to New

No one said that we need to hack the AMQP protocol. This report is about an error that is presented by openQA. If openQA handles this internally, e.g. retry up to 7 times, die with a real helpful error otherwise

Actions #4

Updated by coolo over 6 years ago

  • Status changed from New to Rejected

dude - what's the point in retrying closing unknown channels?

Actions #5

Updated by okurz over 6 years ago

What's the point in having an error message about closing a channel when no one should care about it?

Please teach us how to not waste time with looking at error messages and creating useless progress tickets which are then just rejected :)

https://github.com/os-autoinst/openqa-logwarn/pull/8 for removing the blacklist entry from os-autoinst/openqa-logwarn

Actions #6

Updated by coolo over 6 years ago

you can't know if the AMQP error is fixable or not - so reporting it is fine, but rejecting unfixables is too. Especially if they are sporadic

Actions

Also available in: Atom PDF