Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: clinic 无法本地诊断
|
username: Hacker_ojLJ8Ndr
[TiDB Usage Environment]
Production Environment
[TiDB Version]
tidb: 6.1.0
clinic: 0.8.2
[Encountered Issues]
Error when collecting with tiup diag collect SQ-cluster --include="config":
Error during diagnosis with tiup diag check /home/tidb/diag/diag-fVDFP7Ct67b:
If there was a format issue, it should have reported an error at startup. This configuration has been running normally all along.
Hello, could you please upload the diag file for us to take a look?
The deploy_dir of each node in this cluster is the same, and diag currently does not support this type of cluster.
There is no problem with collecting logs and metrics. The check logic is not supported because the deploy_dir of each node is the same, and our config collection file names are the same, which will cause overwriting and result in the check not working properly. The situation where the deploy_dir of each node is the same usually occurs in clusters imported by Ansible, while normally configured TiUP clusters generally have different deploy_dirs.
This setting is unreasonable, right? The deploy_dir can also be the same when configuring with tiup. If clinic cannot be used in this situation, can it be considered that there is a problem in this aspect?
This topic was automatically closed 60 days after the last reply. No new replies are allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: