Look into what Wei pointed out as well, check to see if the usage process
is even running. There seems to be a workaround noted in that bug if the
usage server is hitting it.
On Wed, Feb 5, 2014 at 7:09 AM, Ahmad Emneina wrote:
> its okay to use a large window, say a month or two back for the s
its okay to use a large window, say a month or two back for the start date
and end date as today.
On Wed, Feb 5, 2014 at 3:42 AM, Indra Pramana wrote:
> Hi Ahmad,
>
> Thanks for your reply. I will try to use CloudMonkey to call the API. What
> should I put the startdate and enddate? Shall I jus
Hi Ahmad,
Thanks for your reply. I will try to use CloudMonkey to call the API. What
should I put the startdate and enddate? Shall I just put today's date or is
it OK for me to generate for say the last one week or one month?
Looking forward to your reply, thank you.
Cheers.
On Wed, Feb 5, 20
I typically use the root admin api calls generateUsageRecords[0] and
listUsageRecords[1] to kickstart the process. When things refuse to
cooperate; I've found it useful to nuke the entries in the db table
cloud_usage.usage_job, restart the services (-management and -usage), and
make the genUsage/li
Hi,
When I installed CloudStack, I also installed the CloudStack usage server
and the service seems to be running fine, I can stop and start the service
and the status is running.
===
# service cloudstack-usage restart
* Stopping CloudStack Usage Monitor cloudstack-usage[
OK
