The necessary component `NgMonitoring` is not started in the cluster, some functions will be unavailable and cannot start normally

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

Original topic: 集群中未启动必要组件 NgMonitoring,部分功能将不可用 无法正常启动

| username: daihu

【TiDB Usage Environment】Testing
【TiDB Version】
【Reproduction Path】
The ng.log shows
[2023/03/10 18:53:09.034 +08:00] [FATAL] [document.go:40] [“failed to open a document database”] [path=/data/xxx-data/prometheus-8249/docdb] [error=“store not found”] [stack=“github.com/pingcap/ng-monitoring/database/document.Init\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/database/document/document.go:40\ngithub.com/pingcap/ng-monitoring/database.Init\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/database/database.go:14\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/main.go:68\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250”]
Restart
tiup cluster restart xxdb -R prometheus
Still doesn’t work
【Encountered Problem: Problem Phenomenon and Impact】
The ng.log shows
[2023/03/10 18:53:09.034 +08:00] [FATAL] [document.go:40] [“failed to open a document database”] [path=/data/xxx-data/prometheus-8249/docdb] [error=“store not found”] [stack=“github.com/pingcap/ng-monitoring/database/document.Init\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/database/document/document.go:40\ngithub.com/pingcap/ng-monitoring/database.Init\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/database/database.go:14\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/ng-monitoring/main.go:68\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250”]
Restart
tiup cluster restart xxdb -R prometheus
Still doesn’t work

【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】

| username: srstack | Original post link

Try redeploying Prometheus and see if it works.

scale-in scale-out

| username: daihu | Original post link

The main thing is to find the cause and see exactly where the problem is.

| username: daihu | Original post link

Currently, my solution is

cd /data/tidb-data/prometheus-8249/docdb/

rm -rf *

Problem solved.

| username: system | Original post link

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