Status

RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: tarek, Unassigned)

Tracking

2013-07-11
x86
Mac OS X
Points:
---

Details

(Reporter)

Description

6 years ago
URL: /statistics/mmo_user_count_total/

SOURCE: TBD
(Reporter)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 1

6 years ago
houston we have a problem on this one, see bug 860201
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 2

6 years ago
We got data for two days, but then it stopped working again :(
Do you know the dates exactly where we got some data in and when it stopped?
After a quick check on the monolith-aggregator host, it seems that we have problems regarding the authentication. I see a bunch of messages like that:

2013-05-13 01:00:04 [10593] [ERROR] API 4xx Error: Error with OAuth headers

There is one for each call to the zamboni monolith's APIs. I think the OAuth implementation changed, so it may only be a problem with the access token which needs to be refreshed.
Might be related to the work Allen did on https://github.com/mozilla/zamboni/commit/5fd17b43f241 which introduces the new way to handle OAuth.

Allen, do you think the old 2-legged access tokens are still usable, or should we clear them and create new ones to consume our API?
Flags: needinfo?(ashort)

Comment 6

6 years ago
Assuming its -dev, it wasn't Allens work, but other changes broke OAuth on the server. It has been fixed since then, so you might need to re-run those days. 

Note that since then we've also had a db refresh which cleaned out the -dev db API tokens.
Thanks Andy.

Then that's the db refresh, I think (I've tried to run it locally and still got these 403s). We just need to recreate the monolith users, probably.

ccing jason and jeremy. Can any of you run the "create_monolith_user" command on stage, dev and prod?
Flags: needinfo?(ashort)

Comment 8

6 years ago
Run on -dev, shouldn't need running on prod or stage, those weren't affected by the refresh.
I think that fixed the issue, at least I don't have any 403s anymore when running it locally.

I'm waiting for tomorrow stats to check if everything propagates cleanly and if we get the right numbers.
https://marketplace.firefox.com/statistics/mmo_user_count_total is working (aside from a week of 0)
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-07-11
You need to log in before you can comment on or make changes to this bug.