springboot整合redis报错解决

最新推荐文章于 2025-03-17 09:43:14 发布
原创 最新推荐文章于 2025-03-17 09:43:14 发布 · 7k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#java #spring boot #linux #redis

在SpringBoot应用中整合Redis时，可能会遇到'protected mode'导致的连接异常。此问题通常由于Redis配置的保护模式启用且未指定绑定地址或认证密码引起。解决方法包括：禁用保护模式、编辑配置文件或设置绑定地址和认证密码。确保在更改后重启Redis服务器，并检查防火墙设置，确保其不影响Redis服务。此外，还提到了Redis的其他常见错误，如防火墙限制，可通过关闭防火墙或修改Redis配置文件中的bind选项来解决。

springboot整合redis常见的报错解决

org.springframework.data.redis.RedisSystemException: Redis exception; nested exception is io.lettuce.core.RedisException: io.lettuce.core.RedisConnectionException: 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 org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:74)
	at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:41)
	at org.springframework.data.redis.PassThroughExceptionTranslationStrategy.translate(PassThroughExceptionTranslationStrategy.java:44)
	at org.springframework.data.redis.FallbackExceptionTranslationStrategy.translate(FallbackExceptionTranslationStrategy.java:42)
	at org.springframework.data.redis.connection.lettuce.LettuceConnection.convertLettuceAccessException(LettuceConnection.java:269)
	at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.convertLettuceAccessException(LettuceStringCommands.java:799)
	at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.get(LettuceStringCommands.java:68)
	at org.springframework.data.redis.connection.DefaultedRedisConnection.get(DefaultedRedisConnection.java:260)
	at org.springframework.data.redis.cache.DefaultRedisCacheWriter.lambda$get$1(DefaultRedisCacheWriter.java:109)
	at org.springframework.data.redis.cache.DefaultRedisCacheWriter.execute(DefaultRedisCacheWriter.java:242)
	at org.springframework.data.redis.cache.DefaultRedisCacheWriter.get(DefaultRedisCacheWriter.java:109)
	at org.springframework.data.redis.cache.RedisCache.lookup(RedisCache.java:88)
	at org.springframework.cache.support.AbstractValueAdaptingCache.get(AbstractValueAdaptingCache.java:58)
	at org.springframework.cache.interceptor.AbstractCacheInvoker.doGet(AbstractCacheInvoker.java:73)
	at org.springframework.cache.interceptor.CacheAspectSupport.findInCaches(CacheAspectSupport.java:554)
	at org.springframework.cache.interceptor.CacheAspectSupport.findCachedItem(CacheAspectSupport.java:519)
	at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:401)
	at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:345)
	at org.springframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:61)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689)
	at com.zql.educms.service.impl.CrmBannerServiceImpl$$EnhancerBySpringCGLIB$$9a538bbb.selectAllBanner(<generated>)
	at com.zql.educms.controller.BannerFrontController.getAllBanner(BannerFrontController.java:36)
	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.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:106)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:888)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:793)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:526)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1579)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)
Caused by: io.lettuce.core.RedisException: io.lettuce.core.RedisConnectionException: 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 io.lettuce.core.LettuceFutures.awaitOrCancel(LettuceFutures.java:129)
	at io.lettuce.core.FutureSyncInvocationHandler.handleInvocation(FutureSyncInvocationHandler.java:69)
	at io.lettuce.core.internal.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:80)
	at com.sun.proxy.$Proxy119.get(Unknown Source)
	at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.get(LettuceStringCommands.java:66)
	... 67 more
Caused by: io.lettuce.core.RedisConnectionException: 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.

遇到上面的问题只要修改配置文件就好了，将

配置文件中的**’protected-mode yes‘** 改为***’protected-mode no‘*** 然后重新用配置文件启动就好了

[root@localhost bin]# redis-server  /usr/local/bin/kconfig/redis.conf
[root@localhost bin]# redis-cli
127.0.0.1:6379> ping
PONG
127.0.0.1:6379> keys *
1) "je"
2) "banner::selectIndexList"
127.0.0.1:6379>

还有常见的redis报错如下：

（1）关闭liunx防火墙
重启、关闭、开启firewalld.service服务
service firewalld restart 重启
service firewalld start 开启
service firewalld stop 关闭
查看防火墙状态
systemctl status firewalld.service
启动和关闭防火墙的命令:
重启后生效
开启： chkconfig iptables on
关闭： chkconfig iptables off
即时生效，重启后失效
开启： service iptables start
关闭： service iptables stop

（2）找到redis配置文件， 注释下面那行
~~~bash
# bind  127.0.0.1
org.springframework.data.redis.RedisSystemException: Error in execution； nested exception is io.lett
知识改变命运，ヾ(◍°∇°◍)ﾉﾞ【求关注】
04-21 4289
最近使用springboot+ Redis
Unknown redis exception； event execu tor terminated；解决
qyhua的专栏
04-03 2760
执行器终止，说起执行器很容易让人联想到线程池，再仔细查看了一下错误代码，发现event execu tor terminated后4行是在线程池报出，再结合报错的代码只是获取get key的值 部分是个循环，这就不难分析出很可以配置的线程太小。未知redis错误,先看看redis的服务是正常，看redis数据库日记（默认位置：/var/log/redis/redis.log）也没有发现有错误，与redis服务无关。经过一段时间观察，一切恢复正常。
生产环境 java.util.concurrent.RejectedExecutionException: event executor terminated 错误分析
zhaorongxi的博客
05-30 9248
今天运维在执行线上功能时发现服务异常,跟进之后发现Redis出现问题,如下: [ERROR] [2022-05-26 00:05:01.518] [c.q.d.utils.DataAccessSampleRedisUtil:326][Thread-154] 服务名称:ivdg-data-access-service--> 查询缓存数据出错:Unknown redis exception; nested exception is java.util.concurrent.RejectedExecu.
解决Redis报错 org.springframework.data.redis.redissystemexception: error in execution
2301_77200169的博客
03-02 2754
vim打开redis-server配置的redis.conf文件，然后使用快捷匹配模式：/stop-writes-on-bgsave-error定位到stop-writes-on-bgsave-error字符串，接着把后面的yes改为no。解决：通过ps -ef|grep redis命令获取redis服务器进程号，使用kill -9 进程号杀死服务器进程，后重启，再启动springboot项目成功运行。初学redis，小小记录一下解决过程。
springboot 整合redis报错
ggFinish的博客
12-15 525
sringboot整合redis时报错
Spring Cloud项目后台报错：org.springframework.data.redis.RedisSystemException（Redis-6.2.6 CentOS 7）
weixin_50799264的博客
02-14 3390
org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk.
springboot整合redis报错org.springframework.beans.factory.UnsatisfiedDependencyException
weixin_46071647的博客
06-15 2141
我的问题出在Cache的实现类中getId()没设置返回值。 Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled. 2021-06-15 00:13:52.942 ERROR 7820 — [ restartedMain] o.s.boot.SpringApplication : Application r
SpringBoot整合redis
qi341500的博客
01-03 1692
SpringBoot整合redis 1、集成jedis 2、集成lettuce 3、集成RedisTemplate
【SpringBoot整合Redis测试Redis集群案例】
awd15771131554的博客
09-25 1462
如图，创建项目遇到的第一个问题就是，当type选择maven，jdk选择1.8时，java部分没办法选择1.8的版本，这怎么办呢？原因：搜了一下，原来是官网的3.xx版本出来后，不再支持jdk1.8了，最低版本要求是jdk17解决办法：如果是个人练习的话，jdk可以安装jdk1.8，也可以再安装一个jdk17，跟上主流版本。
springBoot整合Redis（四、整合redis 实现分布式锁）
kkkkatoq的博客
03-16 1134
在单机环境，我们使用最多的是juc包里的单机锁，但是随着微服务分布式项目的普及，juc里的锁是不能控制分布锁环境的线程安全的，因为单机锁只能控制同个进程里的线程安全，不能控制多节点的线程安全，所以就需要使用分布式锁分布式锁的原理就不说太多了，主要讲讲基于redis的分布式锁的用法。
springboot 整合redis
lqbz的总结
11-04 416
实现步骤 搭建SpringBoot工程。 引入redis起步依赖。 配置redis相关属性。 注入RedisTemplate模板。 编写测试方法。 搭建SpringBoot工程 起步依赖 pom文件中默认就添加了 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-redis</artifactId> &
org.springframework.data.redis.RedisSystemException: Redis exception; nested exception is io.lettuce...
HH_KELE的专栏
06-08 3943
springBoot + redis. 程序隔一段时间会莫名其妙的报Redis的错误. 报错如下: org.springframework.data.redis.RedisSystemException: Redis exception; nested exception is io.lettuce.core.RedisException: java.io.IOException: Connec...
org.springframework.data.redis.RedisSystemException: Error in execution报错
weixin_44296701的博客
12-20 4014
RedisSystemException重启服务器在连接redis数据库时报错
org.springframework.data.redis.RedisSystemException: Error in execution； nes遇到springboot连接Redis报错
热门推荐
不忘初心，砥砺前行
01-16 1万+
org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication required. 这个前提是要检查一下Redis服务是否启动 在使用springboot的2.2.6.RELEASE版本连接Redis的时候，启动报错 配置文件是如下 spring
redis之org.springframework.data.redis.RedisSystemException: Error in execution
不忘的博客
11-13 3565
vim打开redis-server配置的redis.conf文件，然后使用快捷匹配模式：/stop-writes-on-bgsave-error定位到stop-writes-on-bgsave-error字符串所在位置，接着把后面的yes设置为no即可。因为强制把redis快照关闭了导致不能持久化的问题，通过stop-writes-on-bgsave-error值设置为no即可避免这种问题。在运行某系统时，在测试类向redis中存入某值，然后取出。方法2：修改redis.conf文件。
redis报错：org.springframework.data.redis.RedisSystemException
zheng2780071070的博客
02-05 6316
问题： "msg":"系统异常,请联系管理员\norg.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persi
springboot整合Redis时，org.springframework.data.redis.RedisSystemException: Error in execution；
qq_17732903的博客
01-06 1万+
org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: WRONGTYPE Operation against a key holding the wrong kind of value
SpringBoot连接Redis报错：org.springframework.data.redis.RedisSystemException: Error in execution
程序员阿皓的博客
04-15 801
使用springboot整合redis报错： org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication required.
redis长时间未请求，无法自动重连，报异常org.springframework.data.redis.RedisSystemException
chijiansong的博客
03-17 752
disconnectedBehavior(ClientOptions.DisconnectedBehavior.REJECT_COMMANDS) // 断开连接时拒绝命令。.pingBeforeActivateConnection(true) // 连接前PING测试。.shutdownTimeout(Duration.ofSeconds(2)) // 增加关闭超时时间。.commandTimeout(Duration.ofSeconds(5)) // 增加命令超时时间。
springboot整合redis监听器报错：Execution of message listener failed, and no ErrorHandler has been set
最新发布
06-21
在Spring Boot中整合Redis时，如果出现`Execution of message listener failed, and no ErrorHandler has been set`的错误，通常表明监听器在处理消息时抛出了未捕获的异常，而系统并未配置适当的错误处理器来处理...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值