Hello,
It's possible that due to an "unclean" shutdown there is probably a
usage server running that is not having the same pid as the last
scheduled job's (the linux pid is used in the job schedule table).
To correct this, shut down the usage server and delete the last job (the
one that hasn't run yet).
HTH
On 2023-03-13 11:50, cristian.c@istream.today wrote:
Hello,
I just found today that my cloud usage stopped to collect data from
2022,
for sure is related to some upgrade, but it is quite impossible to find
out
which one. my question is, how can I fix this? Can I reset the
cloudstack
usage db? And start collection from today?
"Usage-HB-1:null) (logid:) it's been 17573256046 ms since last usage
job and
71243955 ms until next job, scheduling an immediate job to catch up
(aggregation duration is 1440 minutes)
2023-03-13 05:27:36,045 DEBUG [cloud.usage.UsageManagerImpl]
(Usage-HB-1:null) (logid:) Scheduling Usage job...
2023-03-13 05:27:36,046 INFO [cloud.usage.UsageManagerImpl]
(Usage-Job-1:null) (logid:) starting usage job...
2023-03-13 05:27:36,048 DEBUG [cloud.usage.UsageManagerImpl]
(Usage-Job-1:null) (logid:) Not owner of usage job, skipping...
2023-03-13 05:27:36,048 INFO [cloud.usage.UsageManagerImpl]
(Usage-Job-1:null) (logid:) usage job complete"
Thank you,
Cristian
