Faidon pointed this out:
10:43 < paravoid> faidon@nitrogen:~$ sudo grep -c gmond /var/log/syslog
10:43 < paravoid> Jul 6 17:38:17 nitrogen gmond: Could not connect to database FATAL: password authentication failed for user "ganglia_stats" 10:43 < paravoid> Jul 6 17:38:17 nitrogen gmond: FATAL: password authentication failed for user "ganglia_stats"
I found that we have the same issue on both nitrogen and nihal. Their role is puppetmaster:;puppetdb.
puppetdb/database.pp sets up a postgresql database.
module postgresql has manifests/ganglia.pp with postgresql::ganglia which sets:
5 $pgstats_user, 6 $pgstats_pass, 7 $pgstats_db = 'template1', 8 $pgstats_host = '127.0.0.1', 9 $pgstats_port = '5432',
The template from the puppet class gets realized as /etc/ganglia/conf.d/postgresql.pyconf
There is a (random-looking) password in there that is the same on both servers, but using it doesn't give you access, as the error says:
psql --username ganglia_stats -W template1 Password for user ganglia_stats: psql: FATAL: Peer authentication failed for user "ganglia_stats"
I can see in syslog*.gz that this has been going on since June 30 or earlier (maybe always has been?).
Do we still need this Ganglia plugin or should we simply remove it since Ganglia is deprecated?
Do you know if it has worked before and somehow changed or if it was simply never finished?
Has it maybe been replaced by prometheus? Or should i change the password / try to fix the access to let it write stats?
1 # == Class postgresql::ganglia 2 # This installs a Ganglia plugin for postgresql