Zitat von users-h...@cloudstack.apache.org:
Hi! This is the ezmlm program. I'm managing the
users@cloudstack.apache.org mailing list.
I'm working for my owner, who can be reached
at users-ow...@cloudstack.apache.org.
To confirm that you would like
norbert.kl...@infosecprojects.net
remove
Hi all,
if we delete a project, the name of the project is set to NULL in the
database and thus does not appear in the usage records.
But the display_text ist still available. This makes no sense imho.
We have no chance to display project names of deleted projects in a
monthly report for example.
should surface the DB
>> calls. They'll contain the job ID as well so mapping shouldn't be an
>> issue. Logs could grow quicker on trace, so if space is an issue, you
>> wont want it running on trace for long.
>>
>>> On Sep 21, 2015, at 11:45 PM, Norber
Hello everybody,
is there a possibility to issolate certain mysql queries for error analysis?
I am unable to delete a storage pool, I see the exeception in the log file
and I looked in the code. But for me it is difficult to find out what
mysql query
is created inside the code. I would like to se
gland:
> Good point Norbert, I don't think there is. would be a great addition
> though. You want to take this on or at least create a ticket for it in
> jira? https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK
>
> On Mon, Aug 10, 2015 at 1:48 PM, Nor
Hi all,
what is the best way to check the cloudstack database consistency?
Is there any tool or script available which we could use to make sure
the database structure and content
is in a valid state? (for example after manual changes).
Thx
Norbert
6:49:25
zone_id: 2
resource_id: *747*
resource_name: bts014-data01
offering_id: 6
template_id: NULL
size: 214748364800
resource_type: NULL
processed: 1
virtual_size: NULL
1 row in set (0.01 sec)
If some knows where and how to debug this, any ideas are very welcome.
thx
Norbert
Hi Praveen,
we have come a little bit further with our research.
To answer your questions, I have investigated this case for data volumes
so far.
The usage records which don't have the usageid point to (old) volume
table records of migrated volumes (via the volume id in the description
field).
Th
