在连接redis的时候,报错如下(使用redis desktop manager 可以正常连接,但是Idea运行时却报错如下)


org.springframework.data.redis.RedisConnectionFailureException: Unable to connect to Redis; nested exception is io.lettuce.core.RedisConnectionException: Unable to connect to redis-server:6380at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getNativeConnection(LettuceConnectionFactory.java:1199) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getConnection(LettuceConnectionFactory.java:1178) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getSharedReactiveConnection(LettuceConnectionFactory.java:952) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getReactiveConnection(LettuceConnectionFactory.java:429) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getReactiveConnection(LettuceConnectionFactory.java:94) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at reactor.core.publisher.MonoSupplier.call(MonoSupplier.java:85) ~[reactor-core-3.3.5.RELEASE.jar:3.3.5.RELEASE]at reactor.core.publisher.FluxSubscribeOnCallable$CallableSubscribeOnSubscription.run(FluxSubscribeOnCallable.java:225) ~[reactor-core-3.3.5.RELEASE.jar:3.3.5.RELEASE]at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68) ~[reactor-core-3.3.5.RELEASE.jar:3.3.5.RELEASE]at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28) ~[reactor-core-3.3.5.RELEASE.jar:3.3.5.RELEASE]at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_152]at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_152]at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[na:1.8.0_152]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_152]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_152]at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_152]
Caused by: io.lettuce.core.RedisConnectionException: Unable to connect to redis-server:6380at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:234) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.RedisClient.connect(RedisClient.java:207) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.lambda$getConnection$1(StandaloneConnectionProvider.java:115) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at java.util.Optional.orElseGet(Optional.java:267) ~[na:1.8.0_152]at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.getConnection(StandaloneConnectionProvider.java:115) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getNativeConnection(LettuceConnectionFactory.java:1197) ~[spring-data-redis-2.2.7.RELEASE.jar:2.2.7.RELEASE]... 14 common frames omitted
Caused by: io.lettuce.core.RedisCommandExecutionException: ERR AUTH <password> called without any password configured for the default user. Are you sure your configuration is correct?at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:135) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:108) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.AsyncCommand.completeResult(AsyncCommand.java:120) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.AsyncCommand.complete(AsyncCommand.java:111) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.CommandWrapper.complete(CommandWrapper.java:59) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.CommandHandler.complete(CommandHandler.java:654) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:614) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:565) ~[lettuce-core-5.2.2.RELEASE.jar:5.2.2.RELEASE]at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) ~[netty-transport-4.1.49.Final.jar:4.1.49.Final]at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) ~[netty-common-4.1.49.Final.jar:4.1.49.Final]at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.49.Final.jar:4.1.49.Final]at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.49.Final.jar:4.1.49.Final]... 1 common frames omitted

解决方案:

  1. redis连接报错
  2. 我的错误的原因在于
    这里把password改成Auth的配置就行了

redis连接出错 ERR AUTH <password> called without any password configured for the default user.相关推荐

  1. ERR AUTH<password> called without anypassword configured for the default user.Are you sure your conf

    如图: 目录切换到知识付费项目根目录,点击终端 打开终端后切到知识付费根目录 第一步:检查redis是否启动 命令:redis-cli 第二步:检查redis密码 命令:keys * 第三步:密码 这 ...

  2. Redis 连接命令介绍

    Redis 连接命令主要是用于连接 redis 服务. redis连接命令介绍 AUTH password 说明:AUTH命令用来检测给定的密码和配置文件中的密码是否相同 返回:如果密码匹配则返回OK ...

  3. 【redis】ERR AUTH <password> called without any password configured for the default user解决

    问题产生 在idea使用java连接redis出现以下错误,使用redis可视化工具可以正常连接 org.springframework.data.redis.RedisConnectionFailu ...

  4. 解决问题redis问题:ERR Client sent AUTH, but no password is set

    解决问题redis问题:ERR Client sent AUTH, but no password is set 参考文章: (1)解决问题redis问题:ERR Client sent AUTH, ...

  5. 解决Redis 连接池报错:ERR max number of clients reached

    前言 redis maxclients 是redis server的重要配置,它决定了客户端的最大连接数量,最大客户端连接数量.由于redis不区分连接是客户端连接还是内部打开文件或者和slave连接 ...

  6. Redis连接池Lettuce Jedis 区别

    Lettuce 和 Jedis 的定位都是Redis的client,所以他们当然可以直接连接redis server. pring boot框架中已经集成了redis,在1.x.x的版本时默认使用的j ...

  7. redis连接相关命令

    redis日常连接命令是用客户端时候用的比较多的命令,下面来介绍一下reids连接相关的命令. 命令 1.auth命令-验证密码是否正确. redis中auth命令用于检测给定的密码和配置文件中的密码 ...

  8. C++ 的redis 连接库:RedisPlusplus (redis ++)

    前言 之前给公司作网关,一直想找个牛逼点的C++ 的 或者 C的 redis连接库. 结果很多都不近人意. 常见的是:hiredis 和hirredisvip hiredis 和hirredisvip ...

  9. python数据库去重_python redis连接 有序集合去重的代码

    python redis连接 有序集合去重的代码如下所述: # -*- coding: utf-8 -*- import redis from constant import redis_ip, re ...

最新文章

  1. git branch用法总结
  2. ajax长轮询 java web_Ajax长轮询
  3. AMD全球产业链上的“中国环”会有多给力?
  4. 怎么把外部参照合并到图纸_做电气设计的,拿到建筑图,怎么下手呢?
  5. Configuration Extensions - 简化配置,让你配置支持变量
  6. python格式化转换_(转)python 格式化输出及%用法
  7. 夏至与北回归线的故事
  8. sata7p 定义_纯正良品SATA7PTOSATA7P90度L250mm; CABLE;SATA线
  9. x64伪装进程路径 过PCHunter xxx ARK
  10. 毕业设计任务书----基于Android的学生考勤管理系统设计与实现
  11. 坚持你的梦想,什么时候都不晚!
  12. 完美世界前三季营收57亿同比降15% 净利14.4亿同比增80%
  13. Python生成图文并茂PDF报告
  14. Krpano教程(一)简单使用
  15. 【AAD Connect】01:AAD Connect把本地AD账户同步到Office365(AD域账户迁移)
  16. 泰坦以太(以太流说) titan_ysl 2020.01.27
  17. 沐风:小程序固然好!凭什么能自动赚钱?
  18. 策略产品的进修之路—了解策略和策略产品
  19. lsdyna材料定义(1) lsprepost
  20. 这些开源项目,值得收藏深入研究

热门文章

  1. 证据积累聚类集成算法(Evidence Accumulation Clustering)代码复现与实验
  2. u盘上1T linux系统部署到4T硬盘,bios使用Legace启动(实践可用)
  3. 医院信息化的三种演进建设模式
  4. archpr速度几百_ElcomSoft产品目录2009 - ELCOMSOFT
  5. Shannon极限与Nyquist极限
  6. Unity零基础到入门 ☀️| 一起走进游戏引擎界大佬——Unity 的陈情往事,Unity故事背景介绍
  7. 动作游戏的战斗系统设计
  8. Ag-Grid React入门
  9. 关于麻球网关闭的感想
  10. centos离线配置yun源