codership / galera-manager-support

Galera Manager Support Repository
8 stars 2 forks source link

Installing on CentOS 7.9 to monitor existing cluster - issues with Telegraf and no monitoring #28

Open ronnybremer opened 2 years ago

ronnybremer commented 2 years ago

Just installed galera manager (version 1.8.0) on CentOS 7. After running into multiple issues during install, I managed to finish it. I can access the interface and tried to add my existing cluster. After adding the first node, and running into the documented issue of set_env failed, I deleted the node again and added it a second time. It worked, however, no data is showing up in the gui. Checking the logs I see tons of that:

 telegraf: 2022-03-04T12:53:52Z W! [outputs.influxdb] When writing to [http://monitor:8081]: database "gmd" creation failed: 401 Unauthorized

I checked the influxdb and it looks like the user "gmd" was not created as a v1 user, only as a v2 user. Now the telegraf config is based on v1:

[[outputs.influxdb]]
  urls = ["http://monitor:8081"]
  database = "gmd"
  username = "gmd"
  password = "xxxREMOVEDxxx"

but InfluxDB is already version 2.1.

So I changed the config to be v2 and added a "gmd" v2 user, with r/w access to the bucket "gmd".

[[outputs.influxdb_v2]]
  urls = ["http://monitor:8086"]
  token = "xxxREMOVEDxxx"
  organization = "gmd"
  bucket = "gmd"

Notice the port change from 8081 to 8086.

The errors went away but still the gui doesn't show any data. I have a feeling, that the entire setup is somehow broken.

What is the correct procedure to install GM on CentOS 7, which automatically pulls in InfluxDB v2?

ronnybremer commented 2 years ago

Same seems to go for filebeat:

filebeat[26217]: ERROR gmd/gmd.go:220 Unable to publish events to gmd: {"code":"not found","message":"no dbrp mapping found"}
denisgcm commented 2 years ago

@ronnybremer thank you for reporting this.

Port 8081 is actually a proper one because we open it in nginx and all the traffic goes to it, not to 8086. In your case it sounds like you have your own instance of InfluxDB, i.e. not installed by gm-installer. Is it true? Because if so, we do not currently support such a configuration.

ronnybremer commented 2 years ago

@denisgcm Ok, I will change the port back to 8081.

Regarding InfluxDB, no, I did not have it installed, it was automatically pulled by gm-installer.