Edit report at https://bugs.php.net/bug.php?id=71880&edit=1
ID: 71880
Updated by: nikic@php.net
Reported by: haertl dot mike at gmail dot com
Summary: Optionally disable warnings when writing to STDOUT
-Status: Open
+Status: Closed
Type: Feature/Change Request
Package: FPM related
Operating System: Linux
PHP Version: 5.6.19
-Assigned To:
+Assigned To: nikic
Block user comment: N
Private report: N
Previous Comments:
------------------------------------------------------------------------
[2019-09-13 06:06:21] haertl dot mike at gmail dot com
I confirm: Since 7.3 you can set 'decorate_workers_output = no' in your php.ini wich fixes
the problem.
The issue can be closed.
------------------------------------------------------------------------
[2019-09-12 19:54:21] nikic@php.net
Unless I'm misunderstanding something, isn't this what the decorate_workers_output option
added in 7.3 does? Possibly this issue can be closed now?
------------------------------------------------------------------------
[2019-09-12 19:44:57] davi87 at protonmail dot com
How come we are in 2019 and this warning message problem can't be turned off?
If 'catch_workers_output' is used to aggregate logs, isn't there a way to add
'workers_output_are_fine_and_totally_intended'?
Just saying, paradigm shifts... Containers were invented, PHP doing well and lots of people would
benefit from keeping their logs as simples as possible...
------------------------------------------------------------------------
[2017-03-08 09:23:47] haertl dot mike at gmail dot com
There's now also this PR which should solve the issue:
https://github.com/php/php-src/pull/1076
Related PHP bug:
https://bugs.php.net/bug.php?id=69031
------------------------------------------------------------------------
[2017-03-07 17:10:38] bugs dot php dot net at mog dot se
As all commenters have concluded php://stdout is broken in php-fpm and I will work around by writing
files outside the container directly using volume mounts
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=71880
--
Edit this bug report at https://bugs.php.net/bug.php?id=71880&edit=1