-
Notifications
You must be signed in to change notification settings - Fork 665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RedisException "NOAUTH Authentication required." after a while (password protected redis + tls) #708
Comments
We have further information regarding this matter. It seems that we were experiencing a false positive with this 'options' configuration. It did not solve or prevent the issue. We have seen a correlation with short network interruptions and laravel horizon going into error flooding mode. We will observe this further today, and can still not explain why short network interruptions should cause this kind of behaviour. I'll update with more information as soon as we have more test results. |
It seems your Also: since this is the first time we've heard of an issue with this with the phpredis driver I suspect there is probably indeed a hiccup somewhere on your end. Feel free to add any more thoughts to the issue but I'm gonna close this one for now. |
We just hit this issue too. All 3 servers on DigitalOcean, perfect timing, began in unison. We use a hosted Redis 5 instance from DigitalOcean. See here: https://i.imgur.com/LufPjnt.png I can still run cache()->set() and see the data on other servers with ->get(). I just can't get Horizon:work, to work. We get errors like: On the command
Full trace sample:
There have been NO code changes, NO Deploys, NO config changes. I even checked out bash_history for other admins, login logs and other related stuff. Last deploy was 7 days ago. Last reboot 20 days. Uptime for Horizon master according to supervisor 7 days. Scheduled Redis maintenance by DO, saturday. We are running horizon using Supervisor on Ubuntu 16.04 / PHP 7.4.5
|
just FYI, it's phpredis 5.2.2 |
thank you! fixed. |
Description:
We currently are running horizon connected to redis via tls & AUTH password.
Until now we were using predis, and now switched to phpredis pecl package.
After doing the simple switch in database.php config driver to 'phpredis' (and leaving everything else as it was before) deploying worked, and queue processes started correctly.
After approximately 5 Minutes, we got a flood of errors all looking like this:
Before this error a few hundred jobs were processed correctly, and after this error, nothing was being processed anymore.
After a little of researching we came across a post noting that the password should additionally be set in the 'options' section of the config. And indeed this works, but we were not able to explain why, and where the issue is happening.
We are currently unsure if this is a horizon issue or generally a illuminate redis issue.
Hoping that somebody can share their experiences to see the common denominator and explain this mystery.
Steps To Reproduce:
The text was updated successfully, but these errors were encountered: