All the deadlines are passed, all the sites are migrated...it's time to start shutting this thing down for real! Please deploy the "persona-end-of-life" branch of the service to persona.org: https://github.com/mozilla/persona/pull/4237 SHA: 3611594e1a0cfcbf181aae80aa87ca0d18218594 This will cause the service to gracefully error out when any remaining reliers attempt to use it. Per discussion in the above PR, the "dbwrite", "keysign", and "browserid" components of the service are not required with this version. With that in place, we can keep an eye out for any unexpected breakage before moving on to a more thorough shutdown of the underlying infra.
I tried to deploy this to stage, but the router and static processes exit 1 almost immediately after starting. if you use the cloudops stage us-east-1 bastion, you should be able to ssh to ip-172-31-32-88 investigate. I've looked around, but I haven't been able to figure out why it wouldn't be working. There are no log files being created by those processes, and the only output on stdout before exiting is "path.existsSync is now called `fs.existsSync`.", but that's there on working systems. Verifier starts without issues.
I tried to debug these a little. Attempting to start the static process like this: NODE_ENV=production CONFIG_FILES=/var/persona/config/production.json,/opt/persona/config/l10n-prod.json sudo -E -u persona ./bin/static ; echo $? It errors out trying to load `/var/persona/root.cert`, which is a zero-length file. In the github repo there's a similar file `./var/root.cert` that is not zero-length. Could this be part of the issue, or is it a red herring?
Thank you! that was my problem. anosrep.org is as expected now, deploying to persona.org.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.