Yes it is running

/etc/init.d/cloudstack-usage status

cloudstack-usage (pid  3435) is running...

checking usage db, usage_job table it shows the following

it shows pid number (however its different from pid id 3435, which shows
when running status command), heartbeat info along with start and end_date

I have checked the logs, I keep seeing  "Not owner of usage job,
skipping... " when execution time occur.






On Wed, Oct 30, 2013 at 8:32 AM, Travis Graham <tgra...@tgraham.us> wrote:

> Is the usage agent actually running?
>
> # service cloudstack-usage status
>
> And do you have the cloudstack-usage init script in /etc/init.d/ ?
>
> Travis
>
> On Oct 30, 2013, at 8:20 AM, Dean Kamali <dean.kam...@gmail.com> wrote:
>
> > in my centos 6.4 , I find a  I see a symbolic link in
> /etc/cloudstack/usage
> > which points to /etc/cloudstack/management/db.properties
> >
> > I checked the content of the file and seems okay ( it contain db name,
> > username, password), I have deployed cloudstack management server on
> Ubuntu
> > with exact behavior.
> >
> > I think its a bug!
> >
> > Can someone help?
> >
> > Dean
> >
> >
> > On Wed, Oct 30, 2013 at 2:24 AM, Harikrishna Patnala <
> > harikrishna.patn...@citrix.com> wrote:
> >
> >> Hi,
> >> Can you check db.properties file for correct db connection
> configurations.
> >>
> >> Thanks
> >> Harikrishna
> >> On 30-Oct-2013, at 9:02 am, Dean Kamali <dean.kam...@gmail.com> wrote:
> >>
> >>> Hello everyone
> >>>
> >>> I never seen issue with 4.1.1 but with 4.2, I'm not able to get usage
> >>> database to work.
> >>>
> >>> it has been very frustrating day for me, and no sign of hope!
> >>>
> >>> cloud_usage database is empty
> >>>
> >>> checking the logs I always get UsageServer ready... and no errors or
> >>> exceptions.
> >>>
> >>> I have restarted usage server many times, with no luck.
> >>>
> >>> usage_job table which suppose to show host and pid number for usuage
> >> server
> >>> is always Null.
> >>>
> >>> Any ideas on what I need to check.
> >>>
> >>> Please help!
> >>>
> >>> Thank you
> >>
> >>
>
>

Reply via email to