Skip to content

Conversation

@bukka
Copy link
Member

@bukka bukka commented Oct 29, 2022

SaltStack uses Python subprocess and redirects stderr to stdout which is then piped to the returned output. If php-fpm starts in daemonized mode, it should close stderr. However a fix introduced in GH-8913 keeps stderr around so it can be later restored. That causes the issue reported in GH-9754. The solution is to keep stderr around only when php-fpm runs in foreground as the issue is most likely visible only there. Basically there is no need to restore stderr when php-fpm is daemonized.

@bukka bukka force-pushed the fpm_daemon_stderr branch from 9afd16b to 98bf52c Compare October 29, 2022 19:23
@bukka bukka changed the base branch from master to PHP-8.0 October 29, 2022 19:23
SaltStack uses Python subprocess and redirects stderr to stdout which is
then piped to the returned output. If php-fpm starts in daemonized mode,
it should close stderr. However a fix introduced in phpGH-8913 keeps stderr
around so it can be later restored. That causes the issue reported in
phpGH-9754. The solution is to keep stderr around only when php-fpm runs in
foreground as the issue is most likely visible only there. Basically
there is no need to restore stderr when php-fpm is daemonized.
@bukka
Copy link
Member Author

bukka commented Oct 30, 2022

Merged via 1c5844a

@bukka bukka closed this Oct 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants