[one-users] oneacct [VirtualMachinePoolAccounting] Internal Error
j.melis at gmail.com
Wed Feb 12 06:52:53 PST 2014
it was in fact a bug/typo, and it has been fixed in master, so it will work
fine in OpenNebula 4.6. Anyways, it really doesn't make much difference to
have the order by clause or not, so if you simply disable that mysql flag,
you'll probably see the results the correct way.
On Thu, Jan 30, 2014 at 5:50 PM, Carlos Martín Sánchez <
cmartin at opennebula.org> wrote:
> Hi Stefan,
> On Tue, Jan 28, 2014 at 5:57 PM, Stefan Kooman <stefan at bit.nl> wrote:
>> Hi list,
>> Running oneact as oneadmin user I get the following error:
>> [VirtualMachinePoolAccounting] Internal Error.
>> oned.log shows:
>> Tue Jan 28 17:21:19 2014 [ReM][D]: Req:6624 UID:0
>> VirtualMachinePoolAccounting invoked, -2, -1, -1
>> Tue Jan 28 17:21:19 2014 [ONE][E]: SQL command was: SELECT history.body
>> FROM history INNER JOIN vm_pool WHERE vid=oid GROUP BY vid,seq, error
>> 1055 : 'opennebula.history.body' isn't in GROUP BY
>> Tue Jan 28 17:21:19 2014 [ReM][E]: Req:6624 UID:0
>> VirtualMachinePoolAccounting result FAILURE
>> [VirtualMachinePoolAccounting] Internal Error
>> I don't know for sure it ever worked after I upgraded to onennebula-4.4.
>> It might have to do with our mysql server settings (sql-mode):
>> sql-mode =
>> But I'm not sure.
>> How to best debug this issue?
>> Gr. Stefan
> It definitely looks like a problem with the ONLY_FULL_GROUP_BY flag.
> Now that I think about it, we don't really need the group by, and it may
> probably be a bug and we meant to use ORDER BY .
>  http://dev.opennebula.org/issues/2700
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org
> | @OpenNebula <http://twitter.com/opennebula>
> Users mailing list
> Users at lists.opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users