Closed
Bug 1066274
Opened 10 years ago
Closed 10 years ago
Open netflows from builder1.ateam.phx1 to pulse.mozilla.org:5672
Categories
(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)
Infrastructure & Operations Graveyard
NetOps: DC ACL Request
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ahal, Assigned: dcurado)
References
Details
I'm trying to stand up a new service for monitoring test manifests, but I can't seem to connect to pulse from builder1.ateam.phx1.
$ nmap -p 5672 pulse.mozilla.org
PORT STATE SERVICE
5672/tcp filtered amqp
Is this something you guys could help me out with? Thanks!
Updated•10 years ago
|
Component: NetOps → NetOps: DC ACL Request
Assignee | ||
Updated•10 years ago
|
Assignee: network-operations → dcurado
Assignee | ||
Comment 1•10 years ago
|
||
OK, I think I found the issue, and have updated the firewall configuration.
Can you give it a try when you can, and if it still does not work, re-open this bug?
Thanks very much.
Here's what the policy is on the firewall -- not the most friendly looking output,
but you can see the IP addresses and port numbers...
From zone: ateam, To zone: untrust
Source addresses:
builder1: 10.8.120.26/32
pulsetranslator: 10.8.120.28/32
Destination addresses:
pulse.mozilla.org: 63.245.217.87/32
Application: amqp
IP protocol: tcp, ALG: 0, Inactivity timeout: 43200
Source port range: [0-0]
Destination port range: [5672-5672]
Application: amqps
IP protocol: tcp, ALG: 0, Inactivity timeout: 1800
Source port range: [0-0]
Destination port range: [5671-5671]
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•10 years ago
|
||
Yep, it's fixed now. Thanks a lot!
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•