Issues with the aggregator-output PI on fxa-content-server in Stage

RESOLVED FIXED

Status

Cloud Services
Operations
P3
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jbonacci, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

4 years ago
I am seeing this in the /media/ephemeral0/heka/hekad_err.log:


2014/01/29 19:24:05 Plugin 'aggregator-output': stopped
2014/01/29 19:24:05 Plugin 'aggregator-output' error: dial tcp 23.23.154.66:5671: connection refused
2014/01/29 19:24:06 Plugin 'aggregator-output': exited, now restarting.
2014/01/29 19:33:00 Plugin 'aggregator-output': stopped
2014/01/29 19:33:00 Plugin 'aggregator-output': exited, now restarting.
(Reporter)

Updated

4 years ago
Whiteboard: [qa+]
(Reporter)

Updated

4 years ago
Priority: -- → P3

Comment 1

4 years ago
I have a feeling this is no longer an issue. At any rate content server stacks should be respun in stage since they are probably using an old heka config and pointing at the shared aggregator.
(Reporter)

Comment 2

4 years ago
:jrgm or :pdehaan to confirm...

Comment 3

4 years ago
We've since moved completely off of AMQP so I think it's safe to close this. There's a separate issue causing logging problems at https://github.com/mozilla-services/puppet-config/issues/343 .
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.