Hi,
I believe it is the same issue that already described here.
Try to check if you have mysql-connector-java.jar at you usage lib. If
you don't then create symlink:
ln -s /usr/share/java/mysql-connector-java.jar
/usr/share/cloudstack-usage/lib/mysql-connector-java.jar
Restart usage server after that.
Regarards,
Vadim.
-----Original Message-----
From: Tom Baine [mailto:[email protected]]
Sent: Thursday, November 06, 2014 7:28 PM
To: [email protected]
Subject: Usage Server not processing
Hello,
I'm having trouble getting the ACS usage server to process. The server appears
to be running, but it passes the processing interval without taking any action.
The only record it creates in cloud_usage is in usage_jobs, and the record
looks like a null record. I am running Ubuntu 14.04 with ACS 4.4 installed
from the package repository mentioned in the ACS documentation.
root@cmaster1:~# service cloudstack-usage status
* cloudstack-usage is running
root@cmaster1:~# dpkg --list |grep cloudstack
ii cloudstack-common 4.4.0 all
ii cloudstack-management 4.4.0 all
ii cloudstack-usage 4.4.0 all
root@cmaster1:~#
Last few lines of usage.log:
2014-11-04 20:05:06,604 INFO [cloud.usage.UsageManagerImpl] (main:null)
Implementation Version is 4.4.0
2014-11-04 20:05:06,623 DEBUG [factory.support.DefaultListableBeanFactory]
(main:null) Returning cached instance of singleton bean 'usageManagerImpl'
2014-11-04 20:05:06,623 INFO [cloud.usage.UsageServer] (main:null) UsageServer
ready...
I’ve set all of the logging settings in
/etc/cloudstack/usage/log4j-cloud.xml to DEBUG. I’ve also checked
db.properties (which is a symlink to /etc/cloudstack/management/db.properties
and it seems to have correct DB values.
In ACS Management server Global Settings:
enable.usage.server: true
usage.aggrevation.timezone: America/Chicago
usage.execution.timezone: America/Chicago
usage.sanity.check.interval: 1
usage.stats.job.aggregation.range: 60
usage.stats.job.exec.time: 00:15
cloudstack-management and cloudstack-usage have been restarted several times,
in the order specified in the documentation if that matters.
It looks like the management server doesn’t recognize the usage server as
running, though it appears to make this determination from looking at the last
run time in usage_jobs.
management-server.log:2014-11-06 17:21:40,959 INFO
[c.c.h.HighAvailabilityManagerImpl] (HA-5:ctx-4efe7be4) checking health of
usage server
management-server.log:2014-11-06 17:21:40,961 DEBUG
[c.c.h.HighAvailabilityManagerImpl] (HA-5:ctx-4efe7be4) usage server running?
false, heartbeat: Tue Nov 04 18:00:00 UTC 2014
management-server.log:2014-11-06 17:21:40,962 WARN [o.a.c.alerts]
(HA-5:ctx-4efe7be4) alertType:: 13 // dataCenterId:: 0 // podId:: 0 //
clusterId:: null // message:: No usage server process running
I’m not sure if I’m missing something simple, but I’m out of ideas as to how to
proceed. Any thoughts? Thanks.
