-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redis连接超时 #26
Comments
启动的是哪个环境?配置 redis 的 IP 能正常访问吗 |
可以确定启动了,我单独创建一个项目,安装egg-redis后是正常的,以下是我的代码 import { Controller, Get, Provide } from '@midwayjs/decorator'; @provide() @get('/test') |
默认是127.0.0.1,我改成localhost,或192.168.1.x。还是不行 |
可能需要你自行排查下哪个环节有问题。 |
我的也连不上Redis,都修改了也不行,不知道为啥 |
麻烦提供一下复现步骤 |
我别的项目也在使用,IP 和 端口啥的都是一样。另外一个项目没有问题。
…------------------ 原始邮件 ------------------
发件人: "fsd-nodejs/service-mw2" <notifications@github.com>;
发送时间: 2020年12月31日(星期四) 上午10:51
收件人: "fsd-nodejs/service-mw2"<service-mw2@noreply.github.com>;
抄送: "贾冰"<851080120@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [fsd-nodejs/service-mw2] redis连接超时 (#26)
麻烦提供一下复现步骤
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
麻烦帮忙看一下。
…------------------ 原始邮件 ------------------
发件人: "fsd-nodejs/service-mw2" <notifications@github.com>;
发送时间: 2020年12月31日(星期四) 上午10:51
收件人: "fsd-nodejs/service-mw2"<service-mw2@noreply.github.com>;
抄送: "贾冰"<851080120@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [fsd-nodejs/service-mw2] redis连接超时 (#26)
麻烦提供一下复现步骤
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
本地开发你需要修改config.local.ts这个文件 |
redis设置无密码和有密码都测试了,都提示连接超时
2020-12-24 12:23:49,281 ERROR 21990 nodejs.ETIMEDOUTError: connect ETIMEDOUT
at Socket. (/home/guo/development/javascript/midwayjs/project/service-mw2/node_modules/_ioredis@4.19.4@ioredis/built/redis/index.js:308:37)
at Object.onceWrapper (events.js:421:28)
at Socket.emit (events.js:315:20)
at Socket.EventEmitter.emit (domain.js:486:12)
at Socket._onTimeout (net.js:483:8)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
errorno: "ETIMEDOUT"
code: "ETIMEDOUT"
syscall: "connect"
name: "ETIMEDOUTError"
The text was updated successfully, but these errors were encountered: