Skip to content
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

Open
alexjcollins opened this issue Jan 4, 2022 · 9 comments
Open

PHP 8 image - intermittent 502 #4

alexjcollins opened this issue Jan 4, 2022 · 9 comments
Assignees

Comments

@alexjcollins
Copy link
Member

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.

Screenshot 2022-01-03 at 16 08 08

@jamesedmonston
Copy link
Member

Interesting. Did you or @Tam happen to look inside docker-compose logs when it happened?

I can see there's been a subsequent update to 8.1.1 (we're running 8.1.0). I'll update the images to that, and then do some further eyeballs.

@alexjcollins
Copy link
Member Author

I don't think Tam did, and I didn't - sorry I know that would have been useful!

Sounds like a plan 👍

@jamesedmonston
Copy link
Member

jamesedmonston commented Jan 4, 2022

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 make deploy in the directory.

Will then be worth us keeping an eye on them and looking inside the logs if/when they go down again.

@alexjcollins
Copy link
Member Author

@jamesedmonston Okay cool - thanks! I'll give that a go now on the projects i know have updated.

@jamesedmonston
Copy link
Member

jamesedmonston commented Jan 4, 2022

@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 8.0 to 8.1, and it's only resolved once rebooting the containers. PK has been completely fine since.

@alexjcollins
Copy link
Member Author

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?

@jamesedmonston
Copy link
Member

That's interesting. Do you know if it only happens when there are project config changes, or does it happen on any deployment?

@alexjcollins
Copy link
Member Author

alexjcollins commented Jan 5, 2022

Good question. I couldn't say with certainty, as two changes (#1 & #2) were made not long after one another but I'm fairly sure it went down after the first one, which would have just been a composer change.

@jamesedmonston
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants