fwrite infinite loop on broken pipe

[khughitt]

In an application I have where tasks may take up to 5-6 minutes the workers end up going in infinite loops with an error message to the effect of:

PHP Notice: fwrite(): send of 898 bytes failed with errno=32 Broken pipe in /var/www/lib/Redisent/Redisent.php on line 74

It looks like the same issue was reported upstream and a pull request submitted (jdp/redisent#10).

[ghost]

Hi,

We are facing the same issue.
PHP Notice: fwrite(): send of 898 bytes failed with errno=32 Broken pipe in /var/www/lib/Redisent/Redisent.php on line 74
It stuck in infinite loop. What should be the proper fix for this bug. is this issue already fixed in any of the branch. Please let us know. Thanks

[khughitt]

I applied the upstream fix manually and that did the trick.

[ghost]

Thanks for your reply.

Question for developers/maintainers - any idea when this fix will be officially available or should we go ahead and apply the fix ourselves.

Thanks,
Nitin

[chrisboulton]

Hi,

The fix was actually pulled in a few days ago (sorry about the delay), but as of a few minutes ago, Redisent has actually been replaced by Credis which also correctly handles this.

[jadjoubran]

Can we get details on how to apply the upstream fix? or which files were changed and on which branch to fix this issue.
Thank you

[danhunsaker]

Use a more recent version of Resque which relies on Credis instead of Redisent.

[3nr1c]

Hi, I know this should be fixed from a long time now, but I'm getting the exact same notice. I had to change my composer.json version to "dev-master".

Please consider tagging a new version with the most recent code, as using the dev-master can be a bit insecure if somebody wants to use this in production.

[danhunsaker]

At this point, your best bet might be to use my fork instead... Registered on Packagist under danhunsaker/php-resque.