Project

General

Profile

Actions

action #40007

open

[openqa-monitoring] [warn] A message received from unknown worker connection

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

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2018-08-20
Due date:
% Done:

0%

Estimated time:

Description

observation

From logs of o3

[2018-08-20T11:15:38.0819 UTC] [warn] A message received from unknown worker connection
[2018-08-20T11:15:46.0419 UTC] [warn] A message received from unknown worker connection
[2018-08-20T11:15:56.0868 UTC] [warn] A message received from unknown worker connection
[2018-08-20T11:15:58.0421 UTC] [warn] A message received from unknown worker connection
[2018-08-20T11:15:59.0353 UTC] [warn] A message received from unknown worker connection

suggestion

Probably we need a bit more information in the log output to do something about it, e.g. what kind of worker, what the "unknown worker" identifies himself with, etc.


Related issues 2 (1 open1 closed)

Copied from openQA Project (public) - action #29481: [openqa-monitoring] DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127),"New

Actions
Copied to openQA Project (public) - 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
Actions #1

Updated by okurz over 6 years ago

  • Copied from action #29481: [openqa-monitoring] DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127)," added
Actions #2

Updated by okurz over 6 years ago

  • Copied 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 about 5 years ago

  • Category changed from Regressions/Crashes to Feature requests
  • Priority changed from Normal to Low
  • Target version set to future

I checked all logs on o3 and osd and could not see the error message recently however the string is still in openQA and not that help as is so at least this is a feature request still open.

Actions

Also available in: Atom PDF