-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.1.1 misses psconfig pscheduler-stats under Ubuntu 20 #131
Comments
After some investigation seems this command changed synatx between 5.0.8 and 5.1: in 5.0.8 it is psconfig pscheduler-stats:
while in 5.1 it is psconfig stats pscheduler:
|
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:
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 perfsonar/docs#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:
The text was updated successfully, but these errors were encountered: