Closed Bug 837925 Opened 12 years ago Closed 12 years ago

Need BrowserID and BigTent stage info for troubleshooting

Categories

(Cloud Services :: Operations: Miscellaneous, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ozten, Assigned: gene)

Details

Can we disable minified JavaScript in stage for a few hours? This would be a config change to browserid servers: "use_minified_resources": false, And a restart.
Hey, ozten. Looking at lib/configuration.js, I think we can also do this by setting 'export MINIFIED=' in the run script. Just noting the alternative.
Cool, whatever is best for you.
https://login.anosrep.org/common/js/templates.js is empty This gets created by scripts/create_templates.js. Would it be hard to run this on the static webheads with the appropriate CONFIG_FILES setting?
1) If that won't work, you can switch back to "use_minified_resources": true 2) Can you post sanitized configs for the following stage servers: * bigtent server config * browserid-certifier config which bigtent connects too * browserid server config
Assignee: nobody → gene
I've reverted back to : "use_minified_resources": true
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
For stage bigtent server, can you tell me: * what sha of browserid-certifier is deployed? This is the component that tbe bigtent server connects too, to create certs. * what version of jwcrypto is in browserid-certifier's package.json file?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I'm unable to determine the SHA from the RPM but I can tell you the RPM version : browserid-certifier-0.2012.05.25-1.el6.x86_64 and from that I suspect it's from this SHA : https://github.com/mozilla/browserid-certifier/commit/d81cd1de83e630a03ac0cb48662374b9d0fe25f1#scripts/browserid-certifier.spec [gene@bigtent-yahoo1.idweb.scl2.stage.svc ~]$ cat /opt/certifier/package.json | grep jwcrypto "jwcrypto": "0.2.2",
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.