Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 15 Apr 2013 11:46:16 +0000 (UTC)
From: "sadhu suresh (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12642522.1366026287820.167074.1366026376264@arcas>
In-Reply-To: <JIRA.12642522.1366026287820@arcas>
References: <JIRA.12642522.1366026287820@arcas>
Subject: [jira] [Created] (CLOUDSTACK-2033) cloudstack usage stats are not
 triggered
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

sadhu suresh created CLOUDSTACK-2033:
----------------------------------------

             Summary: cloudstack usage stats are not triggered
                 Key: CLOUDSTACK-2033
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2033
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Usage
    Affects Versions: 4.2.0
            Reporter: sadhu suresh
            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 db.properties 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:10.147.59.110


--
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: http://www.atlassian.com/software/jira