Project

General

Profile

Actions

action #52961

closed

error messages from RabbitMQ "(in cleanup) Can't call method "_handle" on an undefined value" and more

Added by okurz over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
-
Start date:
2019-06-12
Due date:
% Done:

0%

Estimated time:

Description

Observation

From logs on o3:

Jun 12 15:21:01 ariel openqa[9911]: Mojo::Reactor::Poll: I/O watcher failed: Can't call method "_read" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 356.
Jun 12 15:21:02 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:03 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:04 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:05 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:05 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:06 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.
Jun 12 15:21:06 ariel openqa[9911]:         (in cleanup) Can't call method "_handle" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client.pm line 354.

so apparently AMQP works again ;)


Related issues 4 (0 open4 closed)

Related to openQA Project - action #52934: [o3] AMQP does not send any events Resolvedkraih2019-06-12

Actions
Related to openQA Project - action #40010: [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)Resolved2018-08-20

Actions
Related to openQA Project - action #46547: error from log on o3 openqa-webui "(in cleanup) Can't call method "reject" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client/Publisher.pm line 67"Resolvedokurz2019-01-23

Actions
Related to openQA Project - action #40652: AMQP on openqa.opensuse.org disfunctionalResolved2018-09-06

Actions
Actions #1

Updated by okurz over 5 years ago

  • Related to action #52934: [o3] AMQP does not send any events added
Actions #2

Updated by okurz over 5 years ago

  • Related to action #40010: [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) added
Actions #3

Updated by okurz over 5 years ago

  • Related to action #46547: error from log on o3 openqa-webui "(in cleanup) Can't call method "reject" on an undefined value at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/RabbitMQ/Client/Publisher.pm line 67" added
Actions #4

Updated by okurz over 5 years ago

  • Related to action #40652: AMQP on openqa.opensuse.org disfunctional added
Actions #5

Updated by okurz over 5 years ago

Actions #7

Updated by okurz over 5 years ago

  • Status changed from New to Feedback
  • Assignee set to okurz

created https://github.com/inway/mojo-rabbitmq-client/pull/36 for upstream and https://build.opensuse.org/request/show/722008 to fix in our package first. Hotpatched osd with good success. Still receiving AMQP events as verified with amqp_rx 'opensuse.openqa.#' so I guess this should be good enough for now. Let's see how the submissions will be taken.

Actions #8

Updated by okurz over 5 years ago

  • Status changed from Feedback to Resolved

the updated package is effective for us, what happens to the upstream contribution can be tracked outside the scope of the openQA specific ticket, it's still on my github PR list :)

Actions

Also available in: Atom PDF