Actions
action #40010
closed[openqa-monitoring] (in cleanup) Can't call method "stream" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 544 during global destruction (#1)
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
-
Start date:
2018-08-20
Due date:
% Done:
0%
Estimated time:
Description
observation¶
From logs of o3
Aug 20 13:55:53 ariel openqa[3277]: (in cleanup) Can't call method "stream" on an undefined value at
Aug 20 13:55:53 ariel openqa[3277]: /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 544 during global destruction (#1)
Aug 20 13:55:53 ariel openqa[3277]: (W misc) This prefix usually indicates that a DESTROY() method raised
Aug 20 13:55:53 ariel openqa[3277]: the indicated exception. Since destructors are usually called by the
Aug 20 13:55:53 ariel openqa[3277]: system at arbitrary points during execution, and often a vast number of
Aug 20 13:55:53 ariel openqa[3277]: times, the warning is issued only once for any number of failures that
Aug 20 13:55:53 ariel openqa[3277]: would otherwise result in the same message being repeated.
Aug 20 13:55:53 ariel openqa[3277]:
Aug 20 13:55:53 ariel openqa[3277]: Failure of user callbacks dispatched using the G_KEEPERR flag could
Aug 20 13:55:53 ariel openqa[3277]: also result in this warning. See "G_KEEPERR" in perlcall.
Aug 20 13:55:53 ariel openqa[3277]:
Updated by okurz over 5 years ago
- Copied from action #40007: [openqa-monitoring] [warn] A message received from unknown worker connection added
Updated by coolo over 5 years ago
- Status changed from New to Resolved
de46d5684c253531ab0d04bf3a1bf9bce03423bb should make this less relevant - if it happens at all with this.
Updated by okurz almost 5 years ago
- Related to action #52961: error messages from RabbitMQ "(in cleanup) Can't call method "_handle" on an undefined value" and more added
Actions