cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2033) cloudstack usage stats are not triggered
Date Tue, 16 Apr 2013 18:35:17 GMT


ASF subversion and git services commented on CLOUDSTACK-2033:

Commit 574e716352290f9c34bfa7bd3134a13e0caa8da2 in branch refs/heads/internallb from Hugo
Trippaers <>
[;h=574e716 ]

CLOUDSTACK-2033 Fix usage server startup and logging

Properly implement the Daemon interface

Initialize logging when the usage server is started as a daemon

Fix a few minor startup and packaging items.
> cloudstack usage stats are not triggered
> ----------------------------------------
>                 Key: CLOUDSTACK-2033
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: sadhu suresh
>            Assignee: Hugo Trippaers
>            Priority: Critical
>         Attachments: exception_log.txt
> With the current build ,cloudstack usage job fail to start and after following work around
,cloudstack usage service is running but fail to trigger the usage stats job .
> Steps:
> 1.install the management server and usage service
> 2.configure the usage job stats daily  and job execution time to trigger after 10 min
> 3.restart the both cloudstack and cloud_usage services
> 4.check the db/logs for usage stats job details
> Actual result:
> cloudstack usage  service fail to start and throws an exception but after applying the
workaround by copying the and log4j.xml from /etc/cloudstack/management to /etc/cloudstack/usage.
> Cloudstack_usage serivce is up and running but fail to collect the usage stats
> No logs are generated for usage and cloudstack-usage.out  file is empty.
> MS Ip:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message