Project

General

Profile

Actions

Support #5499

open

ERROR [celery.worker.consumer.consumer] consumer: Cannot connect

Added by Stephen Serafin over 6 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
10.09.2018
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:
Affected Version:

Description

rabbitmq-server seems to be complaining about the parameters sent to it (exception error bad argument).

Migrating to a RHEL7 platform from a RHEL6 platform
The RHEL 7 platform uses postgres the RHEL6 was mysql

Basic data:
rabbitmq-server.noarch 3.3.5-34.el7 @EPEL7
RHODECODE CONTROL VERSION: 1.19.1

  • NAME: enterprise-1
  • STATUS: RUNNING
  • VERSION: 4.13.1 Enterprise
  • NAME: vcsserver-1
  • STATUS: RUNNING
  • VERSION: 4.13.1 VCSServer

Logged errors:
enterprise-1/rhodecode_celery.log:
2018-09-10 16:14:19.470 ERROR [celery.worker.consumer.consumer] consumer: Cannot connect to amqp://rcuser:**@127.0.0.1:5672/rhodevhost: [Errno 104] Connection reset by peer.

rabbitmq-sasl.log:
=CRASH REPORT==== 10-Sep-2018::16:14:19 ===
crasher:
initial call: rabbit_reader:init/2
pid:
registered_name: []
exception error: bad argument
in function size/1
called as size([65,77,81,80,1,1,0,9])
in call from rabbit_reader:mainloop/4 (src/rabbit_reader.erl, line 318)
in call from rabbit_reader:run/1 (src/rabbit_reader.erl, line 281)
in call from rabbit_reader:start_connection/5 (src/rabbit_reader.erl, line 255)
ancestors: [,rabbit_tcp_client_sup,rabbit_sup,]
messages: [{'EXIT',#Port,normal}]
links: []
dictionary: [{process_name,
{rabbit_reader,
<<"127.0.0.1:60138 -> 127.0.0.1:5672">>}}]
trap_exit: true
status: running
heap_size: 610
stack_size: 27
reductions: 675
neighbours:

Any clues would be apprciated

Actions

Also available in: Atom PDF