Closed Bug 965635 Opened 10 years ago Closed 10 years ago

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

Categories

(Cloud Services :: Operations: Miscellaneous, task, P3)

Product:
Cloud Services
Component:
Operations: Miscellaneous
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jbonacci, Unassigned)

Details

(Whiteboard: [qa+]) 

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.
Whiteboard: [qa+]
Priority: -- → P3
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.
:jrgm or :pdehaan to confirm...
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
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.