RCT功能出现noauth报错，在集群配置中已经加入密码
Gssflyaway opened this issue · comments
在import cluster时已经配置过cluster的密码
@Gssflyaway 提供一下后台log
@Gssflyaway 提供一下后台log
2020-07-28 05:16:00.002 - INFO [task-39] Start to check alert rules...
2020-07-28 05:16:00.003 - INFO [task-38] Start collecting node info (minute), cluster number = 6
2020-07-28 05:16:30.003 - INFO [task-40] Start update node status and cluster status...
2020-07-28 05:17:00.002 - INFO [task-42] Start to check alert rules...
2020-07-28 05:17:00.002 - INFO [task-41] Start collecting node info (minute), cluster number = 6
2020-07-28 05:17:30.003 - INFO [task-43] Start update node status and cluster status...
2020-07-28 05:18:00.003 - INFO [task-45] Start collecting node info (minute), cluster number = 6
2020-07-28 05:18:00.003 - INFO [task-44] Start to check alert rules...
2020-07-28 05:18:30.003 - INFO [task-46] Start update node status and cluster status...
2020-07-28 05:19:00.003 - INFO [task-48] Start to check alert rules...
2020-07-28 05:19:00.004 - INFO [task-47] Start collecting node info (minute), cluster number = 6
2020-07-28 05:19:30.002 - INFO [task-49] Start update node status and cluster status...
2020-07-28 05:20:00.003 - INFO [task-51] Start collecting node info (minute), cluster number = 6
2020-07-28 05:20:00.005 - INFO [task-50] Start to check alert rules...
2020-07-28 05:20:30.003 - INFO [task-52] Start update node status and cluster status...
2020-07-28 05:21:00.006 - INFO [task-53] Start collecting node info (minute), cluster number = 6
2020-07-28 05:21:00.013 - INFO [task-54] Start to check alert rules...
2020-07-28 05:21:30.003 - INFO [task-55] Start update node status and cluster status...
2020-07-28 05:22:00.002 - INFO [task-56] Start to check alert rules...
2020-07-28 05:22:00.002 - INFO [task-57] Start collecting node info (minute), cluster number = 6
2020-07-28 05:22:30.002 - INFO [task-58] Start update node status and cluster status...
2020-07-28 05:23:00.004 - INFO [task-60] Start to check alert rules...
2020-07-28 05:23:00.004 - INFO [task-59] Start collecting node info (minute), cluster number = 6
2020-07-28 05:23:30.003 - INFO [task-61] Start update node status and cluster status...
2020-07-28 05:24:00.002 - INFO [task-63] Start to check alert rules...
2020-07-28 05:24:00.002 - INFO [task-62] Start collecting node info (minute), cluster number = 6
2020-07-28 05:24:30.002 - INFO [task-64] Start update node status and cluster status...
2020-07-28 05:25:00.002 - INFO [task-66] Start to check alert rules...
2020-07-28 05:25:00.003 - INFO [task-65] Start collecting node info (minute), cluster number = 6
2020-07-28 05:25:30.004 - INFO [task-67] Start update node status and cluster status...
想问下RCT的功能是不是需要在redis机器上安装rct的组件才可以呢
@Gssflyaway 是的，需要部署分析器
@Gssflyaway 是的，需要部署分析器
希望官方还是能出一个详细的教程，看wiki似乎没有这方面的介绍。
@Gssflyaway 好的，我们后面继续完善 https://github.com/ngbdf/redis-manager/wiki/2.x-RCT(%E6%95%B0%E6%8D%AE%E5%88%86%E6%9E%90)
docker run -d -e "JAVA_OPTIONS=-Xmx1024m -Xms300m" -v /opt/app/rct/rct-analyze/config:/opt/app/rct/rct-analyze/config -v /data/redis/redis_cluster:/data/redis/redis_cluster --net=host xaecbd/rct-analyze:latest
这几个wiki我之前参考过，但是有点问题。
- analyze.jar启动成功，但是dashboard.jar 启动失败，log如下：
2020-07-28 06:05:41,659 INFO [main] HikariDataSource: HikariPool-1 - Starting...
Failed to load native library:sqlite-3.21.0.1-a0f93293-a9d7-4e1a-a46f-52c04bdb411f-libsqlitejdbc.so. osinfo: Linux/x86_64
java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.21.0.1-a0f93293-a9d7-4e1a-a46f-52c04bdb411f-libsqlitejdbc.so: /tmp/sqlite-3.21.0.1-a0f93293-a9d7-4e1a-a46f-52c04bdb411f-libsqlitejdbc.so: failed to map segment from shared object: Operation not permitted
2020-07-28 06:05:41,750 WARN [main] AnnotationConfigServletWebServerApplicationContext: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'initServer': Unsatisfied dependency expressed through field 'scheduleTaskService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'scheduleTaskService': Unsatisfied dependency expressed through field 'schedulerFactoryBean'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzDataSourceInitializer': Invocation of init method failed; nested exception is java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open_utf8([BI)V
2020-07-28 06:05:41,752 WARN [main] DisposableBeanAdapter: Invocation of destroy method 'close' failed on bean with name 'eurekaRegistration': org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'org.springframework.cloud.netflix.eureka.EurekaClientAutoConfiguration$RefreshableEurekaClientConfiguration': Singleton bean creation not allowed while singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)
2020-07-28 06:05:41,757 INFO [main] StandardService: Stopping service [Tomcat]
2020-07-28 06:05:41,779 INFO [main] ConditionEvaluationReportLoggingListener:
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-07-28 06:05:41,785 ERROR [main] SpringApplication: Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'initServer': Unsatisfied dependency expressed through field 'scheduleTaskService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'scheduleTaskService': Unsatisfied dependency expressed through field 'schedulerFactoryBean'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzDataSourceInitializer': Invocation of init method failed; nested exception is java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open_utf8([BI)V
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:587)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:91)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:373)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1348)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:578)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:501)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:317)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:315)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:760)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:869)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243)
at org.nesc.ecbd.StartApp.main(StartApp.java:27)
2. 我在一台机器上安装analyze.jar成功了之后用redis-manager页面去做job（这两台机器之间不存在网络隔离，之前配置import cluster监控已经成功），但是出现了error，截图和log如下：
2020-07-28 06:13:33.143 - ERROR [qtp708233766-157] analyzeInstance inactive. ip:10.224.251.123
@Gssflyaway 使用redis-manager不需要启动dashboard.jar 。分析器需要部署在你需要分析的节点上
需要
这台机器就是redis的节点，并且analyze.jar已经启动成功了
请问这个问题有没有解决
等待修复
在dashboard里面发请求的地方因为没有做判断，全部按照无密码方式创建的连接，所以会报错，只要判断下就欧克了