-
Notifications
You must be signed in to change notification settings - Fork 21
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
Connect to localhost fails on 0.35 #141
Comments
set the |
Connection string that does not work:
Connection string that works:
|
Hmm, I cannot reproduce it. |
Ok, so I figured it out by running everything through Perhaps it would be useful if the output from the module listed what it actually tried to connect to (ie. what was resolved)? Something like the following output would have me see the issue immediately:
or
What do you think? That additional bit of information would definitly have saved me (and you) quite some time debugging. |
It needs to apply some patches to hiredis. redis/hiredis#1096 would be related, but we do not know why. |
Thank you for taking the time to followin up on this, and for linking to the other issue. I'll go ahead and close this one now. |
We also ran into this when upgrading to 0.35. For us it is happening on Ubuntu 20.04 and 22.10 with Perl 5.36.0. The underlying reason appears to be that we were connecting to |
Based on the comment by @oschwald perhaps this issue is better reopened. |
After the version bump and update of hiredis in 0.35 there is an issue where
Redis::Fast
is unable to connect tolocalhost:6379
. On the other hand127.0.0.1:6379
works without fail. This behaviour isn't seen on all hosts though. Example I used to reproduce this on one of the problematic hosts:On hosts where this is a problem version 0.34 works without failing, but version 0.35 fails on connect to
localhost
every time.I don't quite know how to proceed in debugging this. What I have checked is that the system can resolve
localhost
just fine, andredis-cli
also connects to the server just fine on bothlocalhost
and127.0.0.1
.The text was updated successfully, but these errors were encountered: