Access to Grafana monitoring is denied in a standalone environment, but the Dashboard can be accessed

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

Original topic: 单机环境下,访问Grafana 监控被拒绝,可以访问Dashboard

| username: 气死人的萌新

[TiDB Usage Environment] Single machine environment
[TiDB Version] v6.1.2
[Reproduction Path] Follow the official documentation for quick start to simulate deployment of a production environment cluster on a single machine
[Encountered Problem: After installation, access to Grafana monitoring is denied, firewall etc. have been turned off]

[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Log/Monitoring]
1689577082550



image

| username: tidb菜鸟一只 | Original post link

Has the port 3000 come up with netstat -anp | grep 3000?
Check if the Grafana node has come up with tiup cluster display <tidb-cluster-name>.

| username: cassblanca | Original post link

  1. You probably used the wrong port. The default port is 3000. If you have done port forwarding, ignore this.
  2. On the server, use lsof -i:[port] where port is the actual Grafana service port to see which service is occupying it.
  3. Use tiup cluster display [cluster_name] to check the cluster status and see if the services are running normally.
| username: redgame | Original post link

Port…

| username: 气死人的萌新 | Original post link

It should be up.

| username: 气死人的萌新 | Original post link

I tested it, and there was no return result. It should not be running.

| username: 啦啦啦啦啦 | Original post link

From your screenshot, there doesn’t seem to be any monitoring information. Could it be that monitoring hasn’t been deployed? Check if it’s included in your topology.

| username: 气死人的萌新 | Original post link

Stupid, it seems that monitoring was not deployed.

| username: cassblanca | Original post link

It looks like you haven’t deployed the alertServer and Grafana services.

| username: 气死人的萌新 | Original post link

Thank you for the guidance. I checked the official documentation, and it does not mention the need for manual deployment.

| username: 裤衩儿飞上天 | Original post link

No monitoring deployed.

| username: 气死人的萌新 | Original post link

Thank you for the guidance. I checked the official documentation, and there is no manual deployment. Now I know, thank you, thank you.

| username: zhanggame1 | Original post link

Obviously, it hasn’t started. tiup cluster display will show the status.

| username: 气死人的萌新 | Original post link

Got it, it was my mistake. I didn’t deploy it manually. I thought it was automatic deployment after reading the official documentation.

| username: zhanggame1 | Original post link

Follow these steps to install
Deploy a TiDB Cluster Using TiUP | PingCAP Docs

| username: 气死人的萌新 | Original post link

Correcting the mistake, I tried again today. I don’t know if it’s because I used
tiup cluster check ./topology.yaml --apply --user root -p
After reinstalling, the cluster status verification was successful.

| username: system | Original post link

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