Hi Cyrille,
This is a known bug for 3.6
http://dev.opennebula.org/issues/1400
It is solved in 3.8, the patch should apply in 3.6, though if you are
interested
On Wed, Nov 14, 2012 at 4:14 PM, Duverne, Cyrille
cyrille.duve...@euranova.eu wrote:
Hello,
I had to restart one and after I get
Hello Ruben,
Thanks a lot for this !
I actually upgraded to 3.8 since I now have a permission issue.
But the VMs history are still looking the same, but the migration
fails because of a permission issue explained in the thread : Upgrade
3.8.1
Thanks in advance to have a look to this :)
Cheers
This is why i haven' upgraded yet. I am afraid get these issues as well and
certainly will take some time to figure.
Cheers
On Thu, Nov 22, 2012 at 7:56 AM, Duverne, Cyrille
cyrille.duve...@euranova.eu wrote:
Hello Ruben,
Thanks a lot for this !
I actually upgraded to 3.8 since I now have
For the records, I had this issues because I changed the property of
my user oneadmin and set back the permissions of the directory etc
to this new UID, in order to get an homogeneous situation in all the
servers.
This wasn't caused by the upgrade..
Cheers
CyD Imagination is more important
Hi,
To fix the history table, you can try the workaround described here [1]
Regards
http://lists.opennebula.org/pipermail/users-opennebula.org/2012-September/020362.html
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
Is there any chance to upgrade DB with special characters containing in the
name?
I am getting: Database schema does not look to be created by OpenNebula:
table user_pool is missing or empty.
Cheers
On Thu, Nov 22, 2012 at 8:16 AM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
Yes that is it Carlos, i managed to recreate a more conventional db name
and username as well and that fixed.
Thanks in advance!
On Thu, Nov 22, 2012 at 3:44 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
Do you mean the database name? It could be related to sequel having
Hello,
I had to restart one and after I get the following history for several
VM for which a live migrate failed :
SEQ HOST REASON
START TIME PROLOG_TIME
0 inferno.local user 11/09 10:52:06 5d
04h01m00s 0d 00h01m21s
1 orthanc.local none
Hello,
Here is the last records of vm-214 :
Wed Nov 14 15:22:01 2012 [LCM][I]: New VM state is MIGRATE
Wed Nov 14 15:22:01 2012 [VMM][I]: ExitCode: 0
Wed Nov 14 15:22:01 2012 [VMM][I]: Successfully execute network driver
operation: pre.
Wed Nov 14 15:22:04 2012 [VMM][I]: Command execution fail:
