Closed szymontrocha closed 4 months ago
After some investigation seems this command changed synatx between 5.0.8 and 5.1:
in 5.0.8 it is psconfig pscheduler-stats:
$ psconfig --help
Usage: psconfig command [ arguments ]
Commands: (Use 'command --help' for further help.)
agentctl pscheduler-migrat pscheduler-transl remote
agents pscheduler-stats publish translate
lookup pscheduler-tasks published validate
$
while in 5.1 it is psconfig stats pscheduler:
$ psconfig --help
Usage: psconfig command [ arguments ]
Commands: (Use 'command --help' for further help.)
agentctl pscheduler-tasks published stats
agents publish remote validate
$
Yes, this CLI change was not documented well enough in the release notes.
But your empty Grafana graphs are still a worry.
I think this is not just docs as the CRON command is not invoked properly acording to the log. 5.1 tries to invoke "old" command
here is more info. it seems that cron file contains wrong definition:
# pwd
/etc/cron.d
# cat psconfig-pscheduler-stats
#Ansible: Run psconfig pscheduler-stats for Prometheus
* * * * * prometheus psconfig pscheduler-stats --format prometheus | sponge /var/lib/prometheus/node-exporter/perfsonar-psconfig-pscheduler-stats.prom
I change it in this file to "psconfig stats pscheduler" and it started to work i.e. no error in log and perfsonar-psconfig-pscheduler-stats.prom is filled with data
Seems like upgrade from 5.0.8 didn't properly update the cron file
Hello @szymontrocha I think this cronjob entry is not from perfSONAR itself but from the PMP Ansible playbooks. That's where it needs to be changed.
If I'm not mistaken, the only perfSONAR-related action is to properly document the new behaviour, which will be followed up in https://github.com/perfsonar/docs/issues/258 I think this ticket can be closed. Feel free to open again if there is something I've missed.
A system after 5.1.1 upgrade with Ubuntu 20 toolkit. This results in Grafana empty graphs: