Hi Dean,

Turns out I didn't have the cloudstack-usage package installed. Strange
that I was seeing those errors.
I will leave it running throughout the day and see if the table is
populated.

While the folder /var/log/cloudstack/usage is created, no files are inside
it. This isn't very surprising as Cloudstack has some very random log
directories, for example /var/log/cloudstack-management is made, but I have
never seen anything in it.

Let me know how you get on,
Marty


On Fri, Aug 30, 2013 at 12:19 AM, Marty Sweet <msweet....@gmail.com> wrote:

> Hi Dean,
>
> I will be able to check for you in a few hours. How many VMs do you
> currently have running?
> Are there any networking statistics on the cloudstack UI or are they blank?
>
> Marty
>
>
> On Friday, August 30, 2013, Dean Kamali wrote:
>
>> I didn't see any exceptions / messages in regards to usage server in
>> management logs,  which made me think that it could be a bug.
>> I'm running out of options here, I guess I will deploy CS again on another
>> machine, and see if I can re-create the issue.
>>
>> could you check if you have cloudstack-usage package installed? if so, do
>> you see any log files created in /var/log/cloudstack/usage
>>
>> Thanks
>>
>>
>> On Thu, Aug 29, 2013 at 6:51 PM, Marty Sweet <msweet....@gmail.com>
>> wrote:
>>
>> > Can you see if there are any errors in your management logs?
>> > I remember seeing usage errors in our logs (running on 4.1.1) but
>> haven't
>> > yet got round to looking at it.
>> >
>> > Marty
>> >
>> > On Thursday, August 29, 2013, Dean Kamali wrote:
>> >
>> > > Hello everyone
>> > >
>> > > there seems to be a bug with 4.1.1 in regards to usage server, I can
>> > start
>> > > the service, but I don't see any logs, running "service
>> cloudstack-usage
>> > > status" reveals that its running.
>> > >
>> > > cloud-usage database tables are empty, I have triggered usage run to
>> > > execute by changing the schedule from global settings menu in
>> cloudstack.
>> > >
>> > > Dose anyone else have the same issue?  or just me!
>> > >
>> > > Thanks
>> > >
>> >
>>
>

Reply via email to