-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Upgrade Ubuntu] ie_prod #958
Comments
FYI @cillian , I am going to run the I also note that it is set up to send Bugsnag reports to project that we don't have access to. |
@dacook Okay thanks, let me know if you need me to do anything. Sending BugSnag reports to your shared project should be fine, although can we still have access too, for debugging? |
Thanks Cillian. Actually I'm going to backtrack; we seem to be hitting limits on our Bugsnag account, and I haven't resolved yet about providing broader access to the shared project (I think it's probable that it contains personal data from other instances). |
I've run the provision script, with an excerpt of changes below for your info. Very large log ensues...
(BTW There was an issue with updating node-build with git, which I manually corrected with git on the server) Sorry that we don't have more transparency around the 🚨 But server is now down... investigating... |
✅ fixed. The provision script had updated the database password, but didn't restart the puma process. I've manually restarted puma and sidekiq and it looks mostly good. However I notice the logo at top-left of the page (desktop only) is not loading, as it has the temporary URL (ubuntu-20). I'm not sure if there will be other assets having that URL, so I've solved it with an nginx redirect with https cert for the temporary domain. All looks ok to me now, but let me know if you spot anything else. |
@dacook No problem about |
Thanks Cillian, I've sent an invite for NR. |
I've run the |
The upgrade has already been performed by Cillian (see #951), but I noticed it is missing some config (eg New Relic) so we should run
provision.yml
to ensure all details are set.Maybe double-check the details in ofn-secrets first to check they match.
The text was updated successfully, but these errors were encountered: