stderr #855

New issue

Closed

opened 2026-03-04 03:01:33 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 03:01:33 +03:00

Owner

Originally created by @jdwx on GitHub (Sep 17, 2025).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1989

Monolog version 1|2|3? 3.9.0

Recently we've started getting this

File: .../vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php
Line: 186

Message: Writing to the log file failed: Write of 8748 bytes failed with errno=32 Broken pipe

From this handler:

$format = new LineFormatter( allowInlineLineBreaks: true );
$log = new StreamHandler( 'php://stderr', Level::Info );
$log->setFormatter( $format );

I'm a little baffled as to how that could happen. The stderr output is not closed; I have this information because our emergency backup exception handler is logging it there after this happens.

The environment is php-fpm.

Since I don't understand how this could happen, I'm not sure how to try to debug this. I'm not sure if this is a Monolog bug, or how it could be, but since stderr remains available in the process, just not to Monolog, I would really appreciate any possible insight into what might be going on.

This started happening rather suddenly about a week ago without any changes to the environment, and, worst of all, it is intermittent.

Originally created by @jdwx on GitHub (Sep 17, 2025). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1989 Monolog version 1|2|3? 3.9.0 Recently we've started getting this ```php File: .../vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php Line: 186 Message: Writing to the log file failed: Write of 8748 bytes failed with errno=32 Broken pipe ``` From this handler: ```php $format = new LineFormatter( allowInlineLineBreaks: true ); $log = new StreamHandler( 'php://stderr', Level::Info ); $log->setFormatter( $format ); ``` I'm a little baffled as to how that could happen. The stderr output is not closed; I have this information because our emergency backup exception handler is logging it there after this happens. The environment is php-fpm. Since I don't understand how this could happen, I'm not sure how to try to debug this. I'm not sure if this is a Monolog bug, or how it could be, but since stderr remains available in the process, just not to Monolog, I would really appreciate any possible insight into what might be going on. This started happening rather suddenly about a week ago without any changes to the environment, and, worst of all, it is intermittent.

kerem

2026-03-04 03:01:33 +03:00

closed this issue
added the
Bug
label

kerem commented

2026-03-04 03:01:35 +03:00

Author

Owner

@IanAtOcucom commented on GitHub (Oct 23, 2025):

I am also seeing this error from time to time using apache mod_fcgid and PHP 8.3.

It seems to be related to stale PHP Sessions[?]

@IanAtOcucom commented on GitHub (Oct 23, 2025): I am also seeing this error from time to time using apache mod_fcgid and PHP 8.3. It seems to be related to stale PHP Sessions[?]

kerem commented

2026-03-04 03:01:35 +03:00

Author

Owner

@Seldaek commented on GitHub (Oct 23, 2025):

See #1860 and #1634 - this happens sometimes and there are many theories as to why but nobody has come up with anything conclusive yet sorry

@Seldaek commented on GitHub (Oct 23, 2025): See #1860 and #1634 - this happens *sometimes* and there are many theories as to why but nobody has come up with anything conclusive yet sorry

kerem referenced this issue

2026-03-04 03:11:27 +03:00

[PR #855] [CLOSED] Up latest master branch from Seldaek/monolog #1382