Alena, Thank you for the suggestion. It actually seems to have started working after setting the usage.sanity.check.interval. I set it to 1 and at the next interval it began populating. Not sure if that should have been set initially, but I do not recall seeing anywhere in the docs that this was mandatory.
Thank you for your help. - Stanley -----Original Message----- From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com] Sent: Monday, May 13, 2013 2:40 PM To: users@cloudstack.apache.org Subject: Re: [cloudstack] usage server does not populate usage data in DB Stanley, this problem can happen when you have multiple management servers in cluster, and usage job runs on both of them. So when MS1 runs usage job, MS2 skips it and you see "Not owner of usage jobÅ ". But as in your case usage tables not getting populated at all, there might be some bug. Can you please check: In cloud_usage DB, usage_job, the last job record. Pid of the record should be the id of your usage process, host - name/IP of the host where usage process is running. If you have single management server setup, and host/pid info in the DB doesn't match usage host info, do the following: * save mysqldumps of both cloud/cloud_usage Dbs in case you will have to revert * stop usage server * remove the record from usage_job for the unprocessed job * start usage server again -Alena. On 5/13/13 11:16 AM, "Stanley Kaytovich" <stanl...@qwertyc.com> wrote: >Hello, > >I am having an interesting issue and not much docs out there on this >particular problem. Cloudstack has been up and running for several days >now and when we access the DB, the tables are empty. The usage log >contains the following: > >2013-05-13 18:13:00,002 INFO [cloud.usage.UsageManagerImpl] >(Usage-Job-1:null) starting usage job... >2013-05-13 18:13:00,007 DEBUG [cloud.usage.UsageManagerImpl] >(Usage-Job-1:null) Not owner of usage job, skipping... >2013-05-13 18:13:00,007 INFO [cloud.usage.UsageManagerImpl] >(Usage-Job-1:null) usage job complete > >Tried to remove and reinstall the cloud-usage package, but this still >persists. > >The user 'cloud' has access granted to the DB. > > >- Stanley >