On Wed, Dec 14, 2016 at 6:30 PM, Nate T. Llaneza <nllan...@citsnc.com>
wrote:

> Hey Simone,
>
>
>
> Here is the output you requested.
>
>
>
> [root@cits002 ~]# ls -l /rhev/data-center/mnt/backup.citsnc.com
> \:_export_Hosted-Engine/45aaa81e-4047-4209-ae4c-8504a243d16e/dom_md/ids
>
> -rwxr-xr-x 1 vdsm kvm 1048576 Dec 13 06:29 /rhev/data-center/mnt/backup.
> citsnc.com:_export_Hosted-Engine/45aaa81e-4047-4209-
> ae4c-8504a243d16e/dom_md/ids
>


Thanks, I think you have just to run
    sanlock client renewal
-s 
45aaa81e-4047-4209-ae4c-8504a243d16e:2:/rhev/data-center/mnt/backup.citsnc.com:
_export_Hosted-Engine/45aaa81e-4047-4209-ae4c-8504a243d16e/dom_md/ids:0
to manually force a renew of the sanlock lease


>
>
>
> *From: *Simone Tiraboschi <stira...@redhat.com>
> *Sent: *Wednesday, December 14, 2016 11:57 AM
> *To: *Nate T. Llaneza <nllan...@citsnc.com>
> *Cc: *users <users@ovirt.org>
> *Subject: *Re: Re[2]: [ovirt-users] Hosted-Engine Fails to Start
>
>
>
>
> On Wed, Dec 14, 2016 at 5:09 PM, Nate T. Llaneza <nllan...@citsnc.com>
> wrote:
>
>> Hey Simone,
>>
>> Thanks for looking at it! I am attaching the requested sanlock log file.
>> I see alot of errors in the past two days.
>>
>
> Could you please paste the output of:
> ls -l /rhev/data-center/mnt/backup.citsnc.com:_export_
> Hosted-Engine/45aaa81e-4047-4209-ae4c-8504a243d16e/dom_md/ids
>
>
>>
>> Regards,
>>
>> Nate
>>
>>
>> ------ Original Message ------
>> From: "Simone Tiraboschi" <stira...@redhat.com>
>> To: "Nate T. Llaneza" <nllan...@citsnc.com>
>> Cc: "users" <users@ovirt.org>
>> Sent: 12/14/2016 10:54:20 AM
>> Subject: Re: [ovirt-users] Hosted-Engine Fails to Start
>>
>> hi Nate,
>> your issue is here:
>> Thread-1300::ERROR::2016-12-14 
>> 08:35:43,818::vm::773::virt.vm::(_startUnderlyingVm)
>> vmId=`ef7b601b-1ae6-4adf-bde6-1455bdb03f52`::The vm start process failed
>> Traceback (most recent call last):
>>   File "/usr/share/vdsm/virt/vm.py", line 714, in _startUnderlyingVm
>>     self._run()
>>   File "/usr/share/vdsm/virt/vm.py", line 2026, in _run
>>     self._connection.createXML(domxml, flags),
>>   File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
>> line 123, in wrapper
>>     ret = f(*args, **kwargs)
>>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 917, in
>> wrapper
>>     return func(inst, *args, **kwargs)
>>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in
>> createXML
>>     if ret is None:raise libvirtError('virDomainCreateXML() failed',
>> conn=self)
>> libvirtError: Failed to acquire lock: No space left on device
>>
>> Could you please attach the output of
>>  sanlock client status
>>
>>
>>
>> On Wed, Dec 14, 2016 at 2:55 PM, Nate T. Llaneza <nllan...@citsnc.com>
>> wrote:
>>
>>> Hey Guys,
>>>
>>> I just performed the update to ovirt-4.0.6-pre on my hosted engine
>>> hypervisor (making sure to pull from the baseurl and not the mirrorlist).
>>> This cleaned up the Glib error message I sent earlier. Awesome! The
>>> downside is that the hosted-engine is still not starting. I'm not sure
>>> where to look, so I am attaching the vdsm log and Hosted-Engine log. Let me
>>> know if there is anything else you need. Thanks for y'alls help.
>>>
>>> Regards,
>>>
>>> Nathan
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.phx.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to