What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Starting from last Friday, my local Docker env keeps throwing 502 Bad Gateway errors when trying to
Starting from last Friday, my local Docker env keeps throwing 502 Bad Gateway errors when trying to open Yves URLs. It might be related to the latest Docker update. Anybody else experiencing this issue?
Comments
-
Same here. Two different projects that show this issue.
0 -
Spryker updated PHP images 3 days ago
https://hub.docker.com/r/spryker/php/tags?name=7.4-alpine3.130 -
Same for Alpine 3.12
https://hub.docker.com/r/spryker/php/tags?name=7.4-alpine3.120 -
Might be related to that announcement:
https://sprykercommunity.slack.com/archives/CH2HA71C5/p16339410691320000 -
We can confirm. On our side, this seems to be related to an update of the spryker/php docker images, which got a new release on friday. Looks like we cannot easily roll back that update, as I cannot find old digest-ids of the images from before friday
0 -
Same here. Seems to be memory issues. This is what I get from the logs
[yves] [yves_eu] - zend_mm_heap corrupted [yves] [yves_eu] - [11-Oct-2021 09:05:26] WARNING: [pool worker] child 41 exited with code 1 after 58.771321 seconds from start [yves] [yves_eu] - [11-Oct-2021 09:05:26] NOTICE: [pool worker] child 45 started
0 -
Do you know if opcache is enabled for you? I found something weird earlier this year: https://github.com/phpstan/phpstan/issues/4881#issuecomment-824068414
0 -
It's the default Spryker configuration. OpCache is enabled but the
validate_timestampsandrevalidate_frequencyoptions are set to render the OpCache inactive0 -
Yup I get the same error:
zed-backoffice] [backoffice_eu] - zend_mm_heap corrupted [proxy] [frontend] - 2021/10/11 09:40:49 [error] 9#9: *37 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.25.0.20, server: backoffice.de.henry.local, request: "GET /security-gui/login HTTP/1.1", upstream: "<fastcgi://172.25.0.17:9001>", host: "backoffice.de.henry.local", referrer: "<http://backoffice.de.henry.local/security-gui/login>" [zed-backoffice] [backoffice_eu] - [11-Oct-2021 09:40:49] WARNING: [pool debugger] child 17 exited with code 1 after 7872.539548 seconds from start [proxy] [gateway] - 172.25.0.1 - - [11/Oct/2021:09:40:49 +0000] "GET /security-gui/login HTTP/1.1" 502 922 "<http://backoffice.de.henry.local/security-gui/login>" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.107 Safari/537.36" "-" [zed-backoffice] [backoffice_eu] - [11-Oct-2021 09:40:49] NOTICE: [pool debugger] child 19 started
0 -
Hi @U02H2U2LQ0L @U01T075RRHD we faced with similar problems on our project and according to latest changes for docker-images blackfire were affected. So in our case disabling of blackfire extension was helpful and solved the issue with zend_mm_heap.
0 -
Hey @U02BQJ7QDGS, thanks for the hint
0 -
Trying that one out currently
0 -
Appears to have alleviated the problem
0 -
-
Nice
0 -
Yes, gentlemen, it is confirmed that the problem is connected to recently upgraded blackfire extension. The issueβs nature is sporadical that could be a reason why it was not caught on the development stage before releasing.
The solution is already in place: the commit is reverted, the images are rebuilt with the previous state.
docker/sdk pull && docker/sdk upshould do the trick by updating the base image to the latest one.Please, also if you have docker caches in your CI/CD make sure your pipelines are using proper images.
0 -
Thank you for the fastest feedback that actually helped to solve issue in short terms.
0 -
Nice, thanks @ULYHPR789
0 -
Thank you!
0 -
Great, thanks a ton!
0 -
Please, update everybody here if the solution solves the problem, Thanks, gentlemen.
0 -
Works like a charm π
0 -
Yep.
0 -
Yes
0 -
Awesome! Keep be so communicative as you are today. Good job on catching this in time.
0 -
Fixed our CI pipeline, too
0 -
π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 84 Spryker News
- 977 Developer Corner
- 828 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 36 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 32 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random