Closed Bug 675773 Opened 14 years ago Closed 14 years ago

Add KNOWN_PROXIES to SUMO stage servers

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Assigned: nmaul)

Details

support.allizom.org (dm-app-sumo01) and support-release.allizom.org (mrapp-stage04) both need the KNOWN_PROXIES list (or an appropriate one for wherever they are). Since they're behind Zeus, we always see REMOTE_ADDR = 10.2.whatever.something in stack traces. Thanks!
Completed. Please let us know if you see any more of this on those 2 sites. Note that they're actually served by different Zeus clusters, but I used the same KNOWN_PROXIES setting for both, which includes all the nodes from both clusters. It's remotely possible that prod would be yet another cluster, I'm not entirely sure.
Assignee: server-ops → nmaul
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Thanks! (In reply to comment #1) > It's remotely possible that prod would be yet another cluster, I'm > not entirely sure. Prod is almost certainly a different cluster, since it's in PHX.
Was Apache restarted? I'm still seeing these IPs and shouldn't be.
It was... I've just removed all *.pyc files and restarted it again, for both sites. Let me know if this helps any.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.