redis_踩坑_Failed connecting to host

╰半夏微凉° 2022-01-06 02:15 444阅读 0赞

刚学习redis就踩个这么大的坑，也是醉了。

问题：

使用java连接Linux服务器上的redis失败

代码：

package com.redis.study.test;
    
    import org.junit.Test;
    import redis.clients.jedis.Jedis;
    
    public class RedisTest {
    
    
        @Test
        public void test() {
            Jedis jedis = new Jedis("192.168.80.128", 6379);
            System.out.println(jedis.get("username"));
        }
    }

错误日志：

redis.clients.jedis.exceptions.JedisConnectionException: Failed connecting to host 192.168.80.128:6379
    
        at redis.clients.jedis.Connection.connect(Connection.java:207)
        at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:93)
        at redis.clients.jedis.Connection.sendCommand(Connection.java:126)
        at redis.clients.jedis.Connection.sendCommand(Connection.java:117)
        at redis.clients.jedis.Jedis.get(Jedis.java:152)
        at com.redis.study.test.RedisTest.test(RedisTest.java:14)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
        at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
        at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
        at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
        at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
        at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
    Caused by: java.net.SocketTimeoutException: connect timed out
        at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at redis.clients.jedis.Connection.connect(Connection.java:184)
        ... 27 more

思考：

1、ip地址错误

（1）、　进入服务器查看Linux服务器地址

![1530035-20190619220636490-365878728.png][]

唉，好像有两个ip地址 试试另一个

![1530035-20190619220724093-1365427849.png][]

吐血。还是不行。

（2）、会不会是本机没法连接服务器，ping一下试试

![1530035-20190619220924344-714838850.png][]

能ping的通啊

（3）、试试telnet

![1530035-20190619221059940-410585168.png][]

看样子是端口没开放

进入服务器尝试开放该端口，但是发现我连Iptables都没有 只要一个iptabkeconfig

![1530035-20190619221358938-326622348.png][]

所以应该不是防火墙的问题

（3）、查到说是redis的还需要开放允许远程连接

进入redis的安装目录修改redis.conf

找到bind 将127.0,0.1注释

保存退出

![1530035-20190619234530636-1372961832.png][]

重启redis试试

![1530035-20190619234621484-1055378043.png][]

连接的问题到此解决但是又出现了新问题

![1530035-20190619234741061-1800372350.png][]

日志：

redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.
    
        at redis.clients.jedis.Protocol.processError(Protocol.java:130)
        at redis.clients.jedis.Protocol.process(Protocol.java:164)
        at redis.clients.jedis.Protocol.read(Protocol.java:218)
        at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:341)
        at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:260)
        at redis.clients.jedis.Connection.getBulkReply(Connection.java:249)
        at redis.clients.jedis.Jedis.get(Jedis.java:153)
        at com.redis.study.test.RedisTest.test(RedisTest.java:12)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
        at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
        at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
        at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
        at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
        at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
    
    
    Process finished with exit code -1

大概意思是说开启了protected mode 也就是保护模式？？

还是找到配置文件，打开，查看 发现真的有这么一个mode把它改成no试试

![1530035-20190619235245252-2006636020.png][]

重启redis再试试

![1530035-20190619235338315-487581597.png][]

终于出结果了

总结:

1、判断是否是服务器地址不对

2、判断端口是否能访问

3、关闭redis的只允许本机访问的限制

4、关闭保护模式

转载于:https://www.cnblogs.com/l48x4264l46/p/11055692.html

[1530035-20190619220636490-365878728.png]: /images/20211228/62230158d70e4a06af2da88f37283161.png
[1530035-20190619220724093-1365427849.png]: /images/20211228/63cb913ce0bf46edbf802440c0cdd936.png
[1530035-20190619220924344-714838850.png]: /images/20211228/ac5f907c26064413bf438a2bf40fd18f.png
[1530035-20190619221059940-410585168.png]: /images/20211228/2e7432a46667437ea0b6c228e8bbc6f7.png
[1530035-20190619221358938-326622348.png]: /images/20211228/fa77157bf93649158ecae9bd56a847cf.png
[1530035-20190619234530636-1372961832.png]: /images/20211228/5f079e3a5db74c429b396d22d8aeabd7.png
[1530035-20190619234621484-1055378043.png]: /images/20211228/c9db8d679bf948d29e335971b9a6bcfb.png
[1530035-20190619234741061-1800372350.png]: /images/20211228/dd0567be6589475991bf557b2b151218.png
[1530035-20190619235245252-2006636020.png]: /images/20211228/415266669ce0497c8e0be3853bd4d130.png
[1530035-20190619235338315-487581597.png]: /images/20211228/6587bfacc0d848ba8bdaf3d7eb319404.png