Haen, This is a problem on exit. When stopping the usage server doesn't always clean its job. It is a problem but a redesign of the usage server in general is needed, especially for large environments/DBs.
A workaround is after stopping the usage server, delete the unprocessed job with the old PID in the DB. You can then start the usage server and it should create its own record and process it. regards, On Fri, Jun 18, 2021 at 6:31 AM Hean Seng <[email protected]> wrote: > Hi > > I have mysql hang, and restarted mysql, restarted cloudstack mgmt, and > usage. > > After that facing issue of following: > > duration is 120 minutes) > > 2021-06-18 04:25:49,656 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-HB-1:null) (logid:) Scheduling Usage job... > > 2021-06-18 04:25:49,657 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) (logid:) starting usage job... > > 2021-06-18 04:25:49,669 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) (logid:) Not owner of usage job, skipping... > > 2021-06-18 04:25:49,669 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) (logid:) usage job complete > > > > Seems usage pid is not updated to db . > > Andybody know how to fix this ? > > -- > Regards, > Hean Seng > -- Daan
