Create public url for bm-l10n-dashboard01

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: Pike, Assigned: oremj)

Tracking

Details

(URL)

(Reporter)

Description

8 years ago
We're at the point where we'd like to have a public url for bm-l10n-dashboard01. It should be https:// for all requests, I recall that this was an option to set on the public cache.

I'd like to get this on l10n-stage-sj.mozilla.org, to map l10n-stage-ams.m.o for the AMS VMs (bug 526711).

Context, the follow-up step is to move the community server l10n.m.o out of the way and have the webapp on bm-l10n-dashboard01 serve as l10n.m.o proper, but we'll need to make sure that all things in that setup work.

Updated

8 years ago
Assignee: server-ops → mrz

Updated

8 years ago
Assignee: mrz → server-ops

Comment 1

8 years ago
MRZ, ping?  We'd love to wrap up this bug as the last step of an l10n-drivers project, which we missed in 2009Q4.  Thanks for the help.
(Assignee)

Updated

8 years ago
Assignee: server-ops → jeremy.orem+bugs
(Assignee)

Comment 2

8 years ago
https://l10n-stage-sj.mozilla.org/
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

8 years ago
Jeremy, this basically works, but something seems to be funky. I'm seeing tons of requests, multiple per second, from zlb01-5.nms. As the url isn't really public yet, I suspect that something's running in circles. 

10.2.10.102 - - [29/Jan/2010:20:59:12 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.100 - - [29/Jan/2010:20:59:13 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.101 - - [29/Jan/2010:20:59:13 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.103 - - [29/Jan/2010:20:59:13 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.104 - - [29/Jan/2010:20:59:16 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.102 - - [29/Jan/2010:20:59:17 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.100 - - [29/Jan/2010:20:59:18 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.101 - - [29/Jan/2010:20:59:18 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.103 - - [29/Jan/2010:20:59:19 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.104 - - [29/Jan/2010:20:59:21 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.102 - - [29/Jan/2010:20:59:22 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.100 - - [29/Jan/2010:20:59:23 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
10.2.10.101 - - [29/Jan/2010:20:59:23 +0000] "GET / HTTP/1.0" 200 2244 "-" "HTTP-Monitor/1.1"
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 4

8 years ago
HTTP-Monitor is a simple health check the load balancers do.
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago8 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.