-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Frequent errors from Predis saying "Error while reading line from the server" #366
Comments
I'm having the same issue |
I've had this since horizon was released. I just ignore it. Would be nice to know why it is happening. EDIT: I also have the timeouts set to -1 |
Same issue here. Did not manage to solve it yet. Would be awesome if somebody has a solution. |
I was able to solve this issue by changing the redis client from 'predis' to 'phpredis'. This can be done in the /config/database.php file:
After this change the error never appeared again. |
Thanks iShotFT - good feedback. I would have preferred not to have to install phpredis but it sounds like it's the only fix available for now. |
I don't want to change entire package for this but I guess I need to eventually. Annoying. |
Hey everyone. Thanks for reporting this. I believe this might be related to laravel/framework#25039 so I don't think it's Horizon specific. Let's continue the discussion on the that issue. Feel free to reply back if you want to provide some additional feedback. |
Yeah, I pulled Horizon from my project because of the errors, but it turns out they're still showing up. |
Given that laravel/framework#25039 was just closed, can you please reopen this. |
@eithed like Taylor says: you'd need a cache failover system which is a feature request and should be implemented in Laravel itself. |
Since moving from using the basic Laravel queue worker to Horizon I've started seeing frequent error messages in my log files when processing queued jobs. The error happens more frequently the more jobs are processed and appears to be Horizon related.
Any thoughts?
The text was updated successfully, but these errors were encountered: