redis--bugger分析

DENIED Redis is running in protected mode because protected mode is enabled, no bind address was ... 将文件位置切换为redis文件夹下的src中。进入redis数据库。 阅读详情

记录一下在开发中使用redis出现的错误和解决方法

redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

at redis.clients.util.Pool.getResource(Pool.java:50)

at redis.clients.jedis.JedisPool.getResource(JedisPool.java:86)

at com.taotao.rest.Test.testSpringJedisSingle(Test.java:23)

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:47)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)

at org.junit.runners.ParentRunner.run(ParentRunner.java:309)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

Caused by: java.util.NoSuchElementException: Unable to validate object

at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:506)

at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)

at redis.clients.util.Pool.getResource(Pool.java:48)

... 25 more

 

 

在spring整合redis时如果遇见这样的错误,解决方法是在连接池配置中把testOnBorrow设置成false

<!-- 在获取连接的时候检查有效性, 默认false -->

<property name="testOnBorrow" value="false" />

如果修改后测试还出现下面的错误,这时候需要修改redis配置文件redis.conf 

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:117)

at redis.clients.jedis.Protocol.process(Protocol.java:142)

at redis.clients.jedis.Protocol.read(Protocol.java:196)

at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:288)

at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:207)

at redis.clients.jedis.Connection.getBulkReply(Connection.java:196)

at redis.clients.jedis.Jedis.get(Jedis.java:98)

at com.taotao.rest.Test.testSpringJedisSingle(Test.java:24)

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:47)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)

at org.junit.runners.ParentRunner.run(ParentRunner.java:309)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

 

 

出现这样的错误是因为你启动redis服务时开启了保护模式

保护模式,默认开启。要是配置里没有指定bind和密码。开启该参数后,redis只会本地进行访问,拒绝外部访问。要是开启了密码和bind,可以开启。否则最好关闭,设置为no。

 

protected-mode no

 

 

 

 

 

 

 

redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

at redis.clients.util.Pool.getResource(Pool.java:50)

at redis.clients.jedis.JedisPool.getResource(JedisPool.java:86)

at com.taotao.rest.Test.testSpringJedisSingle(Test.java:23)

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:47)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)

at org.junit.runners.ParentRunner.run(ParentRunner.java:309)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

Caused by: redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Connection refused: connect

at redis.clients.jedis.Connection.connect(Connection.java:155)

at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:83)

at redis.clients.jedis.BinaryJedis.connect(BinaryJedis.java:1643)

at redis.clients.jedis.JedisFactory.makeObject(JedisFactory.java:85)

at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:861)

at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:458)

at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)

at redis.clients.util.Pool.getResource(Pool.java:48)

... 25 more

Caused by: java.net.ConnectException: Connection refused: connect

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:149)

... 32 more

 

redis拒绝我们的连接是因为redis.conf 文件中默认打开bind 127.0.0.1

打开这个设置后redis 只接收来自于该 IP 地址的请求,如果不进行设置,那么将处理所有请求

所有要把这个注释掉

以上配置改完全部要重启redis服务

以上部分为参考网上经验.

原文:https://blog.youkuaiyun.com/only1994/article/details/52785306

 

自己又遇到的问题

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.

译文:

由于启用了保护模式,没有指定绑定地址,也没有向客户机请求身份验证密码,所以拒绝Redis在保护模式下运行。在这种模式下,连接只能从环回接口接受。如果你想从外部计算机连接到复述,你可能采取的解决方案:

1)只是禁用保护模式发送命令的配置设置保护模式没有从loopback接口连接到复述同一主机服务器正在运行,然而确保复述,不是公开从互联网访问如果你这样做。使用配置重写使此更改永久。

2)或者,您可以通过编辑Redis配置文件来禁用受保护模式,并将受保护模式选项设置为“no”,然后重新启动服务器。

3)如果您只是为了测试而手动启动服务器,请使用“——保护模式no”选项重新启动服务器。

4)设置绑定地址或身份验证密码。注意:您只需要做上述其中一件事,服务器就可以开始接受来自外部的连接。

原因分析一:redis没有设置密码

设置密码方法:

127.0.0.1:6379> config get requirepass 1) "requirepass" 2) "" 127.0.0.1:6379> config set requirepass "admin" OK

 

设置密码后报错:

redis.clients.jedis.exceptions.JedisDataException: NOAUTH Authentication required.

//原因:在redis中设置了密码,我们在服务器中需要做密码配对

NOAUTH Authentication required.翻译过来就是:NOAUTH认证要求。

就是你没有给它权限,进行访问;

Jedis jedis = new Jedis("IP", 6379); jedis.auth("你给redis设置的密码");//加入这一段代码

 

第二天开启项目报错

java.net.SocketTimeoutException: connect timed out

分析:看到超时,第一个要想到防火墙没关

关闭防火墙,重启服务器错误变成昨天的安全设置问题,去redis中设置安全问题

这里还有考虑redis.properties中配置的问题,比如本地测试,局域网分发的ip每天都会变

 

之前项目是在一个简单的项目上做的测试,现在在项目整合中加入redis后报错

Caused by: java.lang.ClassNotFoundException: redis.clients.jedis.JedisPoolConfig

分析:在网上查了很多资料

一般原因如下:jar包冲突、jar版本低。我对jar包进行了多个版本尝试,最后还是不行

最终解决方案:删除tomcat中的项目在导入,正确。

在配置文件中点击<bean id="poolConfig" class="redis.clients.jedis.JedisPoolConfig">

发现能进入相应的包中。

最终原因:导入的jar包没有同步到tomcat中

 

在整合项目是发现缓存要在父容器中配置,当在父容器中配置结束,发现报错

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: ...

The prefix "cache" for element "cache:annotation-driven" is not bound.

分析:缓存没绑定,一看到没绑定就要想到,上面的xml文件没配

解决:

添加红色加粗内容

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:aop="http://www.springframework.org/schema/aop"

xmlns:tx="http://www.springframework.org/schema/tx" xmlns:jdbc="http://www.springframework.org/schema/jdbc"

xmlns:context="http://www.springframework.org/schema/context"

xmlns:mvc="http://www.springframework.org/schema/mvc"

xmlns:cache="http://www.springframework.org/schema/cache"

xsi:schemaLocation="

http://www.springframework.org/schema/cache

http://www.springframework.org/schema/cache/spring-cache.xsd

     http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd

     http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

     http://www.springframework.org/schema/jdbc http://www.springframework.org/schema/jdbc/spring-jdbc-3.0.xsd

     http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd

     http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd

     http://www.springframework.org/schema/mvc http://www.springframework.org/schema/mvc/spring-mvc.xsd">

 

[仿真实战]FDTD Solutions 8.0:从零搭建薄膜光谱分析模型 本文提供了一份基于FDTD Solutions 8.0的薄膜光谱分析模型从零搭建实战指南。通过详细步骤,手把手教你创建玻璃基底与硅薄膜的几何结构、设置仿真区域与边界条件、配置光源与监视器,并最终计算反射率与透射率光谱。内容涵盖参数扫描与优化,旨在帮助用户快速掌握FDTD仿真在纳米光子学与薄膜光学设计中的核心应用。 阅读详情

相关推荐

OpenClaw:深度学习驱动的智能编程工具实战解析

智能编程工具通过深度学习技术革新传统开发流程,其核心在于代码语义理解与实时协作能力。这类工具采用AI代码补全、错误预测等技术,显著降低开发者认知负荷,尤其适用于复杂业务逻辑开发和遗留系统维护场景。以OpenClaw为例,其智能填充和上下文感知功能可提升40%编码效率,减少65%调试时间。关键技术实现包含自然语言处理、代码静态分析等,在金融科技、电商系统等领域具有广泛应用前景。热词提示:代码理解引擎、智能工作流整合展现了当前AI辅助开发的最新趋势。

chubaisheng8627的博客 320

java集成redis集群_Redis集群与Spring启动集成

我有 redis cluster with master, slave and 3 sentinel servers . 主服务器和从服务器映射到dns名称为node1-redis-dev.com,node2-redis-dev.com . redis服务器版本是2.8我在application.properties文件中包含以下内容 .spring.redis.cluster.nodes=n...

weixin_35809056的博客 242

基于LendingClub数据的信贷分析和建模报告

一:课题分析 二:数据获取 三:数据探索 3.1主要特征含义理解 3.2特征分布 3.2.1目标特征分布 3.2.2分类变量的分布 3.2.3连续数值特征分布 3.2.4时序特征分布 3.2.5文字特征分布 3.2.6两两特征的协方差 四:数据预处理 4.1数据集划分 4.2特征缺失值识别与处理 4.2.1严重缺失值的处理 4.2.2缺失值填充 4.3同值性特...

棒子皮蹦蹦床 2万+

redis远程连接不上解决方案

安装好redis后,启动redis,很多时候会发现远程客户端连接不上redis服务,这是什么原因呢? 我们需要对安装好后的redis的配置文件redis.conf做一些修改。 1、关闭保护模式 protected-mode yes 修改为 protected-mode no 当没有为redis显示指定bind且没有设置密码时,此时redis就认为是不安全的,当开启保护模式后,保护模式的作用是只允许本地回环地址127.0.0.1和::1(ipv6回环地址的表示形式)访问。 如果此时远程客户端

学无止境! 3857

华为防火墙双ISP出口实战:如何用策略路由实现电信联通流量自动切换(附配置截图)

本文详细解析了华为防火墙在双ISP环境下的智能选路技术,通过策略路由与健康检测的深度应用,实现电信联通流量的自动切换。文章包含实战配置截图,帮助企业解决切换延迟、路径劣化等核心挑战,提升业务连续性。

backprop5master的博客 643

IPD的分析工具与模型(十六)CBB公用基础模块管理实现资源共享,缩短开发周期

CBB流程的开发环节,基于CBB规划中所识别和设计的CBB,进行CBB的详细设计(包括参数设计和接口设计),并最终实现CBB的落地开发。作为特殊类型的技术构件,CBB的开发流程,可沿用技术开发中的构件开发流程,具体包括概念、计划、开发和迁移等步骤,具体可参见前文的相关介绍。有了蓝图与架构设计,落地实施是关键攻坚。具体工作内容包括:具体工作内容包括:a. 以相似性、聚类、相对独行性、可组合、可扩展性、可维护性等原则为指导,按照产品的功能特征和业务类型,聚焦零散的功能点,形成功能模块,实现产品功能模块的划分;

corgi2020的博客 2001

a频繁连接不上redis_redis远程连接不上解决办法

问题描述:redis远程服务端运行在192.168.3.90计算机上,客户端计算机(ip:192.168.3.110)通过redsi-cli.exe客户端工具连接时,没有反应,连接不上。如图所示:解决步骤:步骤一:注释掉redis.window.conf文件中的bind属性设置。如图所示:步骤二:把protected-mode属性设置no重启redis即可远程连接。如图所示:确定启动成功,查看所有...

weixin_31318441的博客 921

Obsidian笔记同步实战:基于Git的私有化部署与自动化管理

本文详细介绍了如何利用Git为Obsidian笔记构建私有化、自动化且免费的同步方案。通过安装配置Git与Obsidian-git插件,结合Gitee等远程仓库,实现笔记的版本管理、多设备同步与自动备份,打造安全可靠的知识管理体系。

y7z8a的博客 272

Redis问题解决-DENIED Redis is running in protected mode because protected mode is enabled, no bind addre

今天在window系统下学习redis的时候,在cmd界面输入redis-cli.exe -h 127.0.0.1 -p 6379 是OK的,但是输入redis-cli.exe -h 192.168.2.107-p 6379出现以下错误 (error) DENIED Redis is running in protected mode because protected mode is en...

苏暮沉觞的博客 1万+

欧姆龙SYSMAC STUDIO如何与基恩士SR-1000进行EIP通信

简要介绍一下扫码枪和欧姆龙sysmac的配置

weixin_42031602的博客 4782

9、眼底图像智能分析:糖尿病视网膜病变的自动化识别与分级系统

本博客介绍了一种基于深度学习的糖尿病视网膜病变(DR)自动化识别与分级系统。该系统通过视网膜图像的预处理、数据增强、集成模型的构建与优化,实现了对DR的高效识别与分级。识别系统采用二分类任务,准确率达到97.67%,而分级系统通过四分类策略取得了95.2%的准确率。系统在基层社区和医院中具有广泛的应用前景,为DR的早期筛查和精准诊断提供了有效工具。

pea55的博客 144

linux虚拟机redis连接报错

今天测试了一下在本机(win10系统)远程连接 centos下的redis,结果报了以下错误: -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 fro

ZhaFi人 3033

CAPL编程规范与最佳实践

通过本文的学习,读者应该对CAPL编程规范与最佳实践有了初步的了解,并能够编写高质量的CAPL脚本。在实际项目中,CAPL的应用非常广泛,希望读者能够通过不断的学习和实践,掌握更多的CAPL技巧,提高自己的开发能力。

闲人编程的博客 1748

Redis保护模式配置引起的问题

新项目搭建了个新的测试服务器,但是项目发布上去以后Redis一直不好用,查看日志后发现在getResource时报错: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is...

dobecoder的博客 964

IEM模型,地表粗糙度模拟

利用微波反演土壤水分时候,利用IEM模型可以实现对随机地表的模拟

ET2012新版免狗免安装绿色软件

ET2012新版免狗免安祖昂绿色软件。,新界面,新视觉,

centOS搭建Redis集群时遇到的问题

1.Redis的保护模式针对之前Redis版本,默认无bind和密码设置存在很大安全风险;Redis3.2版本提出新特性protected mode(保护模式)。如果Redis在启动时,未开启bind和密码设置功能,只能通过回环地址本地访问,如果尝试远程访问redis,会提示以下错误:DENIED Redis is running protected mode because protected ...

Jhon1994的博客 371

廖雪峰Python教程[完整版]

廖雪峰的python教程整理的,已经排好版了,而且还是完整的,适合小白

Redis中常见的错误Unable to validate object

记录一次redis的报错 Unable to validate object

qq_32203083的博客 4272

SIMATIC S7-1200, S7-1500 PID 控制[手册]

SIMATIC S7-1200, S7-1500 PID 控制[手册]

Redis中protected-mode模式详解

报错情况 我搭建了一个Redis实例,并把protected-mode设置为了yes。 protected-modeyes; 我在其他机器连接这台Redis服务: redis-cli -h 1.1.1.1 -p 6379 结果报错如下: (error) DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authen.

zzhongcy的专栏 3万+

远程客户端无法登录Redis服务器报错问题解决

1,当远程访问redis时,报错如下: -DENIED Redis is running in protected modebecause protected mode is enabled, no bind address was specified, noauthentication password is requested to clients. In this mode conne...

qq_2300688967的博客 2493

redis连接问题

@TOC redis连接问题 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 o

endless_fighting的博客 445

Jedis运行异常

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 ...

qq_40199628的博客 800

Redis is running in protected mode because protected mode is enabled 问题处理

Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients 连接redis报错,根据错误信息,redis运行在受保护模式,需要修改redis配置

weixin_43989637的博客 2275

已解决:客户端无法登录Redis服务器报错,解除保护模式

一:问题如下 在192.168.56.57客户端登录192.168.56.56的redis服务器时,报错如下: [root@localhost src]# ./redis-cli -h 192.168.56.56 -p 6379 -a "aabbcc" 192.168.56.56:6379> ping Error: Connection reset by peer 再telne

翔之天空的专栏 5万+

解决redis desktop manager 链接redis服务器链接不上问题

解决redis desktop manager 链接redis服务器链接不上问题

qq_36348637的博客 4068

Redis客户端操作指令 报错(error) DENIED Redis is running in protected mode because protected mode is enabled

问题:Redis数据库客户端操作报错 (error) 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 inte..

纳兰青华的博客 831

redis报错,Could not get a resource from the pool,Unable to validate object找不到可用的连接池

报错如下: 追踪源码发现第一个错误信息redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool,是由Caused by: java.util.NoSuchElementException: Unable to validate object错误引起的,所以先解决第二个错误。 网上搜索Caused by: java.util.NoSuchElementException:

m0_37210775的博客 4208

redis异常Redis:java.util.NoSuchElementException: Unable to validate object at

前两天项目上线的时候遇到了redis的一个问题,在测试环境的时候项目运行正常,项目一上线redis便开始抛异常。 redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool at … Caused by: java.util.NoSuchElementExcep...

weixin_33912638的博客 1116
上一篇: redis缓存技术(搭建及项目整合)
下一篇: JAVA后端响应浏览器的三种方式(ajax)
jack_too
博客等级 码龄9年 17粉丝 32原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值