Does TiUniManager need to be deployed on a node that is not part of the TiDB cluster? Encountering SSH connection issues

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiUniManager部署需要在一台非TiDB集群的节点吗 出现ssh连接不上的问题

| username: magic

[Test Environment for TiDB]
[TiDB Version] v6.1.2
[Encountered Issue: Problem Description and Impact]

As stated in the title, during the startup process of TiUniManager on a cluster composed of TiDB, TiKV, and PD deployed using TIUP on 3 servers, there is an issue with SSH connectivity.
The tidb user has been configured with tidb ALL=(ALL) NOPASSWD: ALL
SSH passwordless login is possible from the command line on the local machine.

| username: magic | Original post link

Additionally, there is another question. In the configuration, you can add an existing external ES cluster using the parameter external_elasticsearch_url. Do other components, such as monitoring_servers and grafana_servers, have similar parameters? Because there is already another complete set of Grafana, Prometheus, Alertmanager, and Node Exporter.

| username: onlyacat | Original post link

It doesn’t seem to be an SSH issue; the command execution failed.

Try logging in manually and restarting nginx to see if it helps.

| username: Minorli-PingCAP | Original post link

It is recommended to manually test whether the command can be executed before checking SSH connectivity.

| username: tidb狂热爱好者 | Original post link

No need, you can reuse the machine.

| username: magic | Original post link

nginx: [emerg] no host in upstream “/” in /em-deploy/nginx-4180/conf/nginx.conf:73

There is indeed a problem.

| username: magic | Original post link

The issue has been resolved. Previously, the Grafana configuration was commented out.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.