Potential Issue with PHP-FPM 8.3.16: "WARNING: scoreboard: writer detected a potential crashed reader, decrementing reader count."
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Description:
After upgrading to PHP-FPM 8.3.16, we have encountered an issue that appears to occur only on certain services. Despite our efforts to adjust configurations and increase resources, the problem persists. We have not been able to identify any specific pattern or correlation during the PHP process that could be causing this issue. It seems to happen randomly. Although the number of errors is not large, they do appear consistently.
Error Message:
WARNING: scoreboard: writer detected a potential crashed reader, decrementing reader count.
Environment:
PHP Version: 8.3.16
Operating System (Docker image): php:8.3.16-fpm-alpine
Server Type:
Configuration:
pm = dynamic
pm.max_children = 50
pm.start_servers = 5
pm.min_spare_servers = 5
pm.max_spare_servers = 35
memory_limit=512M
max_execution_time=90
post_max_size=20M
upload_max_filesize=20M
max_file_uploads=20
Additional Information:
We have tried the following without success:
- Adjusting various configuration settings.
- Increasing system resources.
Any insights or suggestions on how to resolve this issue would be greatly appreciated. Thank you!
PHP Version
PHP-FPM 8.3.16
Operating System
php:8.3.16-fpm-alpine
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PHP-FPM 8.3.16 warning in the php:8.3.16-fpm-alpine environment and compare the listed process-manager and PHP settings with a reproducible occurrence. Done means identifying a repeatable trigger and a confirmed resolution or regression; the issue names no source file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100