RedisCommandExecutionException: MISCONF Redis

最新推荐文章于 2024-05-13 16:11:23 发布
最新推荐文章于 2024-05-13 16:11:23 发布
阅读量1.5k 收藏 1
点赞数
分类专栏： java redis 文章标签： redis java 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_34254090/article/details/125320884
版权
java 同时被 2 个专栏收录
35 篇文章 0 订阅
订阅专栏
redis
2 篇文章 0 订阅
订阅专栏

Redis未启动或启动失败导致RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

错误可能原因

redis未启动或启动失败
confi配置错误

报错信息

2022-06-09 22:29:08.308 ERROR [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [com.alibaba.nacos.naming.push.receiver] com.alibaba.nacos.client.naming          : [NA] error while receiving push data

java.net.SocketException: socket closed
	at java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native Method)
	at java.net.DualStackPlainDatagramSocketImpl.receive0(Unknown Source)
	at java.net.AbstractPlainDatagramSocketImpl.receive(Unknown Source)
	at java.net.DatagramSocket.receive(Unknown Source)
	at com.alibaba.nacos.client.naming.core.PushReceiver.run(PushReceiver.java:83)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

2022-06-09 22:29:08.309  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.backups.FailoverReactor do shutdown begin
2022-06-09 22:29:08.309  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.backups.FailoverReactor do shutdown stop
2022-06-09 22:29:08.310  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.core.HostReactor do shutdown stop
2022-06-09 22:29:08.310  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.net.NamingProxy do shutdown begin
2022-06-09 22:29:08.310  WARN [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : [NamingHttpClientManager] Start destroying NacosRestTemplate
2022-06-09 22:29:08.311  WARN [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : [NamingHttpClientManager] Destruction of the end
2022-06-09 22:29:08.311  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] com.alibaba.nacos.client.naming          : com.alibaba.nacos.client.naming.net.NamingProxy do shutdown stop
2022-06-09 22:29:09.470  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2022-06-09 22:29:09.505  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.e.c.c.s.ConnectionStartupListener    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60452MB, used:37802MB], JvmMemory: 39% [max:21835MB, total:2324MB, free:1398MB, used:925MB]
destory datasource resource.
2022-06-09 22:29:09.505  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.e.c.c.s.ConnectionStartupListener    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60452MB, used:37802MB], JvmMemory: 39% [max:21835MB, total:2324MB, free:1398MB, used:925MB]
destory c3p0 datasource.
2022-06-09 22:29:09.509  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.e.c.c.s.ConnectionStartupListener    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60452MB, used:37802MB], JvmMemory: 39% [max:21835MB, total:2324MB, free:1398MB, used:925MB]
destory c3p0 datasource.
2022-06-09 22:29:09.510  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.e.c.c.s.ConnectionStartupListener    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60452MB, used:37802MB], JvmMemory: 39% [max:21835MB, total:2324MB, free:1396MB, used:927MB]
destory c3p0 datasource.
2022-06-09 22:29:09.539  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.e.s.management.MBeanServerConnector    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
MBeanserverConnectorService [url=service:jmx:rmi://192.168.189.1:6530/jndi/rmi://192.168.189.1:6530/jmxDefault.jmx] stop!
2022-06-09 22:29:09.542  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.system.impl.service.DomainService    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
Begin to stop EOS system Domain service
2022-06-09 22:29:09.542  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.system.impl.service.DomainService    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
EOS system Domain service stoped
2022-06-09 22:29:09.542  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.s.impl.service.HotUpdateService      : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
Begin to stop HotUpdateService
2022-06-09 22:29:09.543  WARN [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [DomainStatusPerformance] c.p.system.impl.service.DomainService    : UserInfo: null, Thread: Thread[DomainStatusPerformance,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
DomainStatusPerformanceThread is interrupted.
2022-06-09 22:29:09.557  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.s.impl.service.HotUpdateService      : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
HotUpdateService stopped.
2022-06-09 22:29:09.559  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.ext.system.service.SystemService     : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
EOS system service stoped
[GE-CATALOG-LOCAL] stop in 0 s.
2022-06-09 22:29:09.560  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] c.p.e.s.a.EOS8SpringBootConfiguration    : UserInfo: null, Thread: Thread[main,5,main], CPU: 86%, SystemMemory: 38% [total:98254MB, free:60453MB, used:37801MB], JvmMemory: 40% [max:21835MB, total:2324MB, free:1393MB, used:930MB]
==== Destroyed EOS Runtime
2022-06-09 22:29:09.564  WARN [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [RxIoScheduler-1 (Evictor)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 java.lang.Thread.run(Unknown Source)
2022-06-09 22:29:09.595  INFO [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] ConditionEvaluationReportLoggingListener : 

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2022-06-09 22:29:09.639 ERROR [CATALOG,GE-CATALOG-LOCAL,default,DESKTOP-E3BKV6N:GE-CATALOG-LOCAL:28011,,,,] 33384 --- [main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OSSFileController' defined in file [H:\Dev_projects\catalog_0524\catalog_0524\source\catalog\org.gecom.data.catalog.common\target\classes\org\gecom\data\catalog\common\oss\OSSFileController.class]: Instantiation of bean failed; nested exception is java.lang.ExceptionInInitializerError
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1303)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1197)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:845)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:743)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:390)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:312)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1214)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1203)
	at org.gecom.data.catalog.Application.main(Application.java:21)
Caused by: java.lang.ExceptionInInitializerError: null
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at java.lang.reflect.Constructor.newInstance(Unknown Source)
	at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:172)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1295)
	... 17 common frames omitted
Caused by: 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. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
	at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:54)
	at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:52)
	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:268)
	at org.springframework.data.redis.connection.lettuce.LettuceKeyCommands.convertLettuceAccessException(LettuceKeyCommands.java:817)
	at org.springframework.data.redis.connection.lettuce.LettuceKeyCommands.del(LettuceKeyCommands.java:131)
	at org.springframework.data.redis.connection.DefaultedRedisConnection.del(DefaultedRedisConnection.java:69)
	at org.springframework.data.redis.connection.DefaultStringRedisConnection.del(DefaultStringRedisConnection.java:254)
	at org.springframework.data.redis.core.RedisTemplate.lambda$delete$2(RedisTemplate.java:709)
	at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:224)
	at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:184)
	at org.springframework.data.redis.core.RedisTemplate.delete(RedisTemplate.java:709)
	at com.primeton.eos.springboot.cache.EOS8RedisCache.removeValue(EOS8RedisCache.java:167)
	at com.primeton.common.cache.impl.DelegateCache.removeValue(DelegateCache.java:82)
	at com.primeton.ext.common.cache.AbstractCache.remove(AbstractCache.java:322)
	at org.gecom.data.catalog.common.cache.RedisUtil.remove(RedisUtil.java:54)
	at org.gecom.data.catalog.common.cache.BasicRedisOperator.destroy(BasicRedisOperator.java:75)
	at org.gecom.data.catalog.common.cache.ext.ConfigCacheUtil.init(ConfigCacheUtil.java:25)
	at org.gecom.data.catalog.common.cache.ext.ConfigCacheUtil.<init>(ConfigCacheUtil.java:20)
	at org.gecom.data.catalog.common.cache.ext.ConfigCacheUtil.getInstance(ConfigCacheUtil.java:55)
	at org.gecom.data.catalog.common.util.SystemConfig.getConfig(SystemConfig.java:17)
	at org.gecom.data.catalog.common.util.SystemConfig.getSysConfig(SystemConfig.java:40)
	at org.gecom.data.catalog.common.oss.OSSFileController.<clinit>(OSSFileController.java:51)
	... 24 common frames omitted
Caused by: io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
	at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:135)
	at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:108)
	at io.lettuce.core.protocol.AsyncCommand.completeResult(AsyncCommand.java:120)
	at io.lettuce.core.protocol.AsyncCommand.complete(AsyncCommand.java:111)
	at io.lettuce.core.protocol.CommandWrapper.complete(CommandWrapper.java:59)
	at io.lettuce.core.protocol.CommandHandler.complete(CommandHandler.java:646)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:604)
	at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:556)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1421)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:930)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:697)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:632)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:549)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:511)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:918)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Unknown Source)
Alan_刘志强
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
【异常】Spring Session存在Redis时报错“ERR config is disabled command“的解决方法
本本本添哥
02-06 811
RedisCommandExecutionException：ERR ‘config’ is disabled command 问题出在这个注解：@EnableRedisHttpSession 查看RedisHttpSessionConfiguration类源码（如下）， 发现配置开启keyspace notifications功能的入参：configureRedisAction。ConfigureRedisAction接受注入，默认的来自构造函数中的， 发现这个类用来配置“notify-keyspace
【报错日记】RedisCommandExecutionException：WRONGTYPE
weixin_44732635的博客
07-14 1678
首先应该明白报这个错误说明了你用的jedis方法与redis服务器中存储数据的类型存在冲突。 例如：数据库中有一个key的数据存储的是Hash类型的，但是你使用jedis执行数据操作的时候却使用了非Hash的操作方法。此时就会报 WRONGTYPE Operation against a key holding the wrong kind of value这个错误！ 问题解决： 直接通过RDM删除缓存数据 或者 先执行一条如下命令： redis 127.0.0.1:6379>typ
io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, b
aaaaaaaaattt的博客
05-29 999
表示redis 宕机了，重新启动redis-server.exe redis.windows.conf。
本地redis连接不上；org.springframework.data.redis.RedisConnectionFailureException: Unable to connect to Red
最新发布
qq_42239685的博客
05-13 271
开启进程守护 yes代表开启守护进程模式。在该模式下，redis会在后台运行，并将进程pid号写入至redis.conf选项pidfile设置的文件中，此时redis将一直运行，除非手动kill该进程。一、在redis.windows.conf配置文件中修改。
解决redis连接错误：MISCONF Redis is configured to save RDB snapshots, but it is currently not able to...
WGBLW的博客
11-05 1万+
一 、问题 查看日志，发现报错 Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is cu rrently not able to persist on disk. Commands that may modify the data set are disabled,
springboot连接redis 没有权限 io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication requir
热门推荐
sinat_35821285的博客
06-13 4万+
io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication required 解决方案： 1.检查一下你linux端口有没有开放 2.在确认开放了端口且工具能连得上redis（密码都正确）的情况下。检查一下密码是参数是不是password ,可能会习惯性写成pwd ...
Redis ‘MISCONF Redis is configured to save RDB snapshots, but is currently not able to …’持久化问题
01-09
Redis遇到了报错：MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for ...
flask-redis:使用Redis作为存储实现Flask会话接口
05-04
烧瓶-redis 使用Redis作为存储实现Flask会话接口。依存关系在运行flask run在同一文件夹flask run与redissesion.py一起运行之前，请使用pipenv安装这些依赖项pipenv --python 3.7pipenv shellpipenv installflask ...
没用的：【Redis开发】资源
05-06
没用的：【Redis开发】资源
redislock:使用Redis简化分布式锁实现
07-24
client := redis . NewClient ( & redis. Options { Network : "tcp" , Addr : "127.0.0.1:6379" , }) defer client . Close () // Create a new lock client. locker := redislock . New ( client ) ctx...
Linux安装redis及使用
01-19
第一步：下载 redis-4.0.6.tar.gz 并解压 第二步：进行解压后的目录后编译：make（如果报错，就执行apt-get install gcc） 如果还是不行就把redis解压文件删除，重新解压 第三步：进入redis下的src目录下安装redis ...
关于在宝塔服务器部署遇到的问题：nested exception is io.lettuce.core.RedisCommandExecutionException: NOAUTH Authe
qq_30637341的博客
06-07 501
但并不能解决我的问题，它说他是本地的redis版本过旧导致，我在服务器上，且redis都是最新的肯定就是不是版本问题。对啊，我是在服务器上，又去检查服务器的redis配置，显然我的服务器的redis并没有连接。这里只需要去重启下redis服务，如果本地配置了redis其他信息如，redis也要配置相同。今天对一台新服务器进行新的系统的部署，后面对系统功能测试，提交表单数据时，遇到。先是去检查yml的redis有无问题，显然没问题。说是redis的问题，noauth没有认证。我这里就没有做其他的配置！
io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication required.
De_Buffer的博客
08-25 3657
lettuce版本过高引发的血案
MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk.
DreamsArchitects的博客
02-18 640
Caused by: io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to repor.
spring链接redis报错 Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionExcept...
darling331的博客
07-20 1万+
记录一次生产环境的redis切换事故 生产环境redis切换，由原来的直连ip服务改为阿里的redis集群，出现了链接失败的错误org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionExcep...
nested exception is io.lettuce.core.RedisCommandExecutionException:MISCONF Redis
qq_28183291的博客
03-20 4879
Redis异常问题 org.springframework.data.redis.RedisSystemException: Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands
Spring Session java连接redis 失败解决方案
jaffreyen的博客
01-29 5767
日志提示连接拒绝, 是因为redis默认的protected-mode默认为yes 解决方案1: 进入redis-cli  输入命令 CONFIG SET protected-mode no 解决方案2. 在redis目录下的redis.conf配置文件中增加 protected-mode no 方案2需要重启redis 设置成功, 重启项目就没有这个错误了
AttributeError: module 'scipy.misc' has no attribute 'toimage'
08-16
这个错误是因为 `scipy.misc` 模块中的 `toimage` 函数已经在 SciPy 1.3.0 版本中被弃用，并在 1.4.0 版本中移除了。如果你使用的是较新的 SciPy 版本，请使用 `PIL`（Python Imaging Library）模块中的 `Image.fromarray` 函数来替代 `toimage`。下面是一个示例： ```python import numpy as np from PIL import Image # 假设你有一个名为 img 的 NumPy 数组 img = np.array([[255, 0, 0], [0, 255, 0], [0, 0, 255]]) # 使用 Image.fromarray 函数将 NumPy 数组转换为图像对象 image = Image.fromarray(img) # 可以对图像对象进行进一步的操作，如保存或显示 image.save('output.png') ``` 如果你想要使用类似于 `toimage` 函数的功能，你可以使用 `scipy.misc` 模块中的其他函数，如 `imsave` 或 `imresize`。是请注意，`scipy.misc` 模块已经在 SciPy 1.3.0 版本中被弃用，并且在将来的版本中可能会被移除。因此，建议使用其他替代方案来处理图像。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值