Issues with ngmonitoring Configuration Files

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

Original topic: ngmonitoring配置文件问题

| username: 啦啦啦啦啦

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] v6.1.6
[Reproduction Path]
[Encountered Problem: Problem Phenomenon and Impact]
During monitoring expansion, it was found that PD reported Necessary component NgMonitoring not started in the cluster.
Manually executing the startup script on the machine resulted in an error:
Failed to initialize config, err: Near line 16 (last key parsed ‘pd.endpoints’): expected a comma or array terminator ‘]’, but got ‘"’ instead.

Checking the configuration file ngmonitoring.toml revealed:
endpoints = [“xx.xx.xx.xx:2379” “xx.xx.xx.xx:2379” “xx.xx.xx.xx:2379”]
It should normally be endpoints = [“xx.xx.xx.xx:2379”,“xx.xx.xx.xx:2379”,“xx.xx.xx.xx:2379”]
After manually correcting it, the startup was successful. Not sure if this is a bug.

| username: xfworld | Original post link

Probably a bug :face_with_spiral_eyes:

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

:joy: It seems like it should be

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

Is the automatically generated configuration file missing a comma?

| username: ouyangqing | Original post link

This should be reported to the official team for fixing.

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


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

It seems that I’m not the only one who has encountered this issue. According to the chat group, version 6.5.1 has also experienced it. Could the official team please confirm this?

| username: Billmay表妹 | Original post link

I’ll provide my feedback.

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

Got it!

| username: 扬仔_tidb | Original post link

This issue still exists in multiple versions of 6.5.x and is a bug.

| username: caiyfc | Original post link

Just upgrade tiup, my article is about the fix for this bug: Column - Step-by-Step Guide to Becoming a TiDB Contributor | TiDB Community

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

:+1: The new version of tiup indeed did not reproduce the issue.

| username: coderv | Original post link

Waiting for the official team to follow up!

| username: 扬仔_tidb | Original post link

I’m still experiencing this issue with version 6.5.3. I wonder if it has been fixed in version 7.

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

Fixed it, upgrading the tiup version and tiup-cluster will do.

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

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