-
Notifications
You must be signed in to change notification settings - Fork 1
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
PHP 8 image - intermittent 502 #4
Comments
Interesting. Did you or @Tam happen to look inside I can see there's been a subsequent update to |
I don't think Tam did, and I didn't - sorry I know that would have been useful! Sounds like a plan 👍 |
They're updated now. I've rebuilt TOKA on staging. Could be an idea to rebuild any of the projects you were having issues with – you can either redeploy from Buddy or run Will then be worth us keeping an eye on them and looking inside the logs if/when they go down again. |
@jamesedmonston Okay cool - thanks! I'll give that a go now on the projects i know have updated. |
@alexjcollins I had the same issue on PK when I deployed a change. I'm wondering if there's some kind of cache that doesn't get cleared properly when updating from |
I feel like it has happened a couple of times on each project (at least the couple I've been making CMS changes on recently) - is it possible that lines up with what you're saying? |
That's interesting. Do you know if it only happens when there are project config changes, or does it happen on any deployment? |
Leaving a paper trail: there seems to be an issue with having JIT mode enabled in 8.1.x. Disabling it appears to fix the issue. Will keep an eye on patches to see if/when they fix it. |
During the week of the 20th December Tam and I noticed a few of the projects that were using the new image on staging would be going down and start returning a
502
error. It seemed related to deployments (i.e. it would go down shortly after a cms deployment), but that might just be a coincidence. I think TOKA went down on the Monday (20th) without a deploy.Restarting the project would then sort the problem.
I'll add uptime monitoring to the projects I know have been updated and let you know when they drop.
Becuase of this I've held back pushing anything Craft-based to production, in case it's not just something inherent to staging.
@Tam feel free to weigh in with anything you can remember from our conversation that week.
The text was updated successfully, but these errors were encountered: