Req #71880 [Com]: Optionally disable warnings when writing to STDOUT

Edit report at https://bugs.php.net/bug.php?id=71880&edit=1 ID: 71880 Comment by: davi87 at protonmail dot com Reported by: haertl dot mike at gmail dot com Summary: Optionally disable warnings when writing to STDOUT Status: Open Type: Feature/Change Request Package: FPM related Operating System: Linux PHP Version: 5.6.19 Block user comment: N Private report: N New Comment: 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... Previous Comments: ------------------------------------------------------------------------ [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 ------------------------------------------------------------------------ [2017-03-07 16:59:08] bugs dot php dot net at mog dot se Hello. Neither named pipes or files are good alternatives to stdout when using Docker. Why is PHP mangling and truncating my log data!?!?!?!?!? ------------------------------------------------------------------------ [2016-11-22 21:27:45] dvalentiate at gmail dot com To makes the php-fpm error logging not crappy I ended up putting mkfifo /tmp/stdout && chmod 777 /tmp/stdout in my a run statement in my Dockerfile, and also setting error_log = /tmp/stdout access.log = /tmp/stdout in a php config .ini file and php-fpm | tail -f /tmp/stdout in my docker-compose command call. The result is clean PHP error logging. ------------------------------------------------------------------------ [2016-08-26 08:05:20] mark dot sagikazar at gmail dot com Okay, I still think there is a misunderstanding. I KNOW that we should log to stdout. BUT because of this bug it is not really developer friendly, SO there is a quick dirty hack: > CMD service start && tail -f /tmp/stdout This hack suggested using named pipes and I asked why not use a file instead, which might be the default for applications. Of course, when this bug is resolved or someone doesn't care about it, we should use stdout. ------------------------------------------------------------------------ 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