You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@answer.apache.org by "aaro-n (via GitHub)" <gi...@apache.org> on 2024/02/19 03:36:50 UTC
[I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
aaro-n opened a new issue, #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69
# system introduction
Answer version: 2.2.5
Answer plug-in: the latest version of the plug-in repository
Running method: Build Docker image by yourself, with plug-in
Redis plug-in display version: 0.0.1
# Problem Description
Using the latest Redis plug-in, when the Redis address is filled in with password authentication, redis cannot be connected correctly. The Redis address is: `redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`,
## Test 1
Enable the Redis plug-in, fill in the address `redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`, log:
```
2024-02-19T02:40:34.677 app[9185d61a426038] nrt [info] 2024-02-19 10:40:34.675 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:34.831 app[9185d61a426038] nrt [info] 2024-02-19 10:40:34.830 ERROR question/question_repo.go:341 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:34.831 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3
2024-02-19T02:40:49.513 app[9185d61a426038] nrt [info] 2024-02-19 10:40:49.512 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:50.288 app[9185d61a426038] nrt [info] 2024-02-19 10:40:50.288 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.084 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.084 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.130 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.129 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.290 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.289 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.492 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.492 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.656 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.656 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.816 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.816 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:51.998 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.997 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:52.180 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.179 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:52.305 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.305 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:52.506 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.506 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:53.277 app[9185d61a426038] nrt [info] 2024-02-19 10:40:53.277 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:54.025 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.024 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:54.051 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.050 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:54.090 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.089 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:54.235 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.235 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:54.967 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.967 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:58.436 app[9185d61a426038] nrt [info] 2024-02-19 10:40:58.435 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:58.565 app[9185d61a426038] nrt [info] 2024-02-19 10:40:58.564 ERROR action/captcha_strategy.go:36 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:59.318 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.317 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:59.391 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.390 ERROR action/captcha_strategy.go:36 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.472 ERROR handler/handler.go:53 code: 500, reason: base.database_error, message: , error: dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/repo/captcha/captcha.go:94 github.com/apache/incubator-answer/internal/repo/captcha.(*captchaRepo).SetCaptcha
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:175 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).GenerateCaptcha
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:87 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).ActionRecord
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/controller/user_controller.go:502 github.com/apache/incubator-answer/internal/controller.(*UserController).ActionRecord
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/base/middleware/auth.go:64 github.com/apache/incubator-answer/internal/router.(*AnswerAPIRouter).RegisterMustUnAuthAnswerAPIRouter.(*AuthUserMiddleware).Auth.func1
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:620 github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:576 github.com/gin-gonic/gin.(*Engine).ServeHTTP
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2938 net/http.serverHandler.ServeHTTP
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2009 net/http.(*conn).serve
2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/runtime/asm_amd64.s:1650 runtime.goexit
```
At the same time, when you visit the project again and log in, you will be prompted to enter a verification code, but the verification code has not been set yet.
## Test 2
Test the connection `default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`, reset the Answer, and fill in the Redis connection `default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379` again. The log is as follows:
```
2024-02-19T02:49:48.570 app[9185d61a426038] nrt [info] start cron
2024-02-19T02:49:48.731 app[9185d61a426038] nrt [info] 2024-02-19 10:49:48.730 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:49:48.887 app[9185d61a426038] nrt [info] 2024-02-19 10:49:48.886 ERROR question/question_repo.go:341 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:49:48.888 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3
2024-02-19T02:50:11.946 app[9185d61a426038] nrt [info] 2024-02-19 10:50:11.944 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.670 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.669 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.678 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.677 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.700 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.699 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.912 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.912 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.928 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.928 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:12.943 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.942 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:13.134 app[9185d61a426038] nrt [info] 2024-02-19 10:50:13.133 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:13.251 app[9185d61a426038] nrt [info] 2024-02-19 10:50:13.250 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.047 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.046 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.113 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.112 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.138 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.137 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.296 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.295 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.428 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.428 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.718 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.717 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:14.863 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.863 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:15.169 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.168 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:15.410 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.409 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:15.603 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.602 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:16.375 app[9185d61a426038] nrt [info] 2024-02-19 10:50:16.374 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:17.158 app[9185d61a426038] nrt [info] 2024-02-19 10:50:17.158 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:17.330 app[9185d61a426038] nrt [info] 2024-02-19 10:50:17.330 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:23.782 app[9185d61a426038] nrt [info] 2024-02-19 10:50:23.781 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:23.897 app[9185d61a426038] nrt [info] 2024-02-19 10:50:23.895 ERROR action/captcha_strategy.go:36 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:24.598 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.597 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:24.674 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.673 ERROR action/captcha_strategy.go:36 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.819 ERROR handler/handler.go:53 code: 500, reason: base.database_error, message: , error: dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/repo/captcha/captcha.go:94 github.com/apache/incubator-answer/internal/repo/captcha.(*captchaRepo).SetCaptcha
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:175 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).GenerateCaptcha
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:87 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).ActionRecord
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/controller/user_controller.go:502 github.com/apache/incubator-answer/internal/controller.(*UserController).ActionRecord
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/base/middleware/auth.go:64 github.com/apache/incubator-answer/internal/router.(*AnswerAPIRouter).RegisterMustUnAuthAnswerAPIRouter.(*AuthUserMiddleware).Auth.func1
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:620 github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:576 github.com/gin-gonic/gin.(*Engine).ServeHTTP
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2938 net/http.serverHandler.ServeHTTP
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2009 net/http.(*conn).serve
2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/runtime/asm_amd64.s:1650 runtime.goexit
```
When logging in, the same problem occurs as in test 1.
## Test 3
Test the Redis connection `ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`, the log is as follows:
```
nrt [info] 2024-02-19 10:56:52.641 ERROR site_info/siteinfo_repo.go:101 dial tcp: lookup ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io: no such host
2024-02-19T02:56:52.956 app[9185d61a426038] nrt [info] 2024-02-19 10:56:52.950 ERROR question/question_repo.go:341 dial tcp: lookup ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io: no such host
2024-02-19T02:56:52.963 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3
```
Test connection `redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`, log:
```
[info] 2024-02-19 11:25:33.298 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:33.456 app[9185d61a426038] nrt [info] 2024-02-19 11:25:33.455 ERROR question/question_repo.go:341 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:33.458 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3
2024-02-19T03:25:34.563 app[9185d61a426038] nrt [info] 2024-02-19 11:25:34.562 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:36.709 app[9185d61a426038] nrt [info] 2024-02-19 11:25:36.708 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:36.751 app[9185d61a426038] nrt [info] 2024-02-19 11:25:36.751 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:39.425 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.424 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:39.562 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.561 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:39.764 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.764 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
2024-02-19T03:25:40.011 app[9185d61a426038] nrt [info] 2024-02-19 11:25:40.010 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address
```
# Build Dockerfile
```
FROM apache/answer as answer-builder
RUN apk --no-cache add \
build-base git bash nodejs npm go && \
npm install -g pnpm
RUN answer build \
--with github.com/apache/incubator-answer-plugins/search-meilisearch \
--with github.com/apache/incubator-answer-plugins/cache-redis \
--with github.com/apache/incubator-answer-plugins/storage-s3 \
--output /usr/bin/new_answer
FROM apache/answer
COPY --from=answer-builder /usr/bin/new_answer /usr/bin/answer
RUN chmod 755 /entrypoint.sh
VOLUME /data
EXPOSE 80
ENTRYPOINT ["/entrypoint.sh"]
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "lincolnzhou (via GitHub)" <gi...@apache.org>.
lincolnzhou commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1953449486
#71 Please review this pr
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "LinkinStars (via GitHub)" <gi...@apache.org>.
LinkinStars commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1951818734
@aaro-n I get it. The current configuration doesn't support configuring redis username yet. We only add the password config in #57
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "LinkinStars (via GitHub)" <gi...@apache.org>.
LinkinStars commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1953563285
@aaro-n Now you can try to configure the username and password for redis using `github.com/apache/incubator-answer-plugins/cache-redis@v1.2.6`
<img width="899" alt="image" src="https://github.com/apache/incubator-answer-plugins/assets/19712692/30bff3b2-77ec-4050-b629-b8558b170abe">
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "LinkinStars (via GitHub)" <gi...@apache.org>.
LinkinStars commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1951825826
@lincolnzhou Just a small follow-up, do you want to continue contributing features about configuring redis usernames? Because you did the feature of the password before. Of course, if there is no time, I can assign it to someone else. Just asking out of courtesy.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "lincolnzhou (via GitHub)" <gi...@apache.org>.
lincolnzhou commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1953405440
> @lincolnzhou Just a small follow-up, do you want to continue contributing features about configuring redis usernames? Because you did the feature of the password before. Of course, if there is no time, I can assign it to someone else. Just asking out of courtesy.
Okay, I'll try to fix it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "aaro-n (via GitHub)" <gi...@apache.org>.
aaro-n commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1951712904
@LinkinStars My Redis is provided by upstash.com. The link provided is in the form of `redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379`. The specific explanation is: `Protocol name://username:user password@ Host domain name or IP:port`, only use `123.upstash.io:6379`, unable to provide access password to upstash.com.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "aaro-n (via GitHub)" <gi...@apache.org>.
aaro-n closed issue #69: The redis cache plug-in cannot access the redis server with password authentication
URL: https://github.com/apache/incubator-answer-plugins/issues/69
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "aaro-n (via GitHub)" <gi...@apache.org>.
aaro-n commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1953585329
@lincolnzhou @LinkinStars I have tested the redis plug-in version 1.2.6. After entering the address, username, and password, redis is enabled normally and this problem is closed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "LinkinStars (via GitHub)" <gi...@apache.org>.
LinkinStars commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1951658076
@aaro-n It seems that you are unable to access the address "ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io" from within your Docker container. You can use the `ping` command in docker container to test if the `ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io` is accessible.
BTW, I think the `ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379` url is correct. I'm not sure how your Redis is deployed, so I can't provide any further advice.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The redis cache plug-in cannot access the redis server with password authentication [incubator-answer-plugins]
Posted by "LinkinStars (via GitHub)" <gi...@apache.org>.
LinkinStars commented on issue #69:
URL: https://github.com/apache/incubator-answer-plugins/issues/69#issuecomment-1953407970
> > @lincolnzhou Just a small follow-up, do you want to continue contributing features about configuring redis usernames? Because you did the feature of the password before. Of course, if there is no time, I can assign it to someone else. Just asking out of courtesy.
>
> Okay, I'll try to fix it
@lincolnzhou Thank you very much.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org