<p dir="ltr">Thanks Andrew, I'll try this workaround tomorrow for sure. But reading though that bug report (closed not a bug) it states that the problem should only arise if something is not releasing a sanlock lease. So if we've entered Global Maintenance and shut down Engine, the question is what's holding the lease?</p>
<p dir="ltr">How can that be debugged?</p>
<p dir="ltr">-Bob</p>
<div class="gmail_quote">On Jun 5, 2014 10:56 PM, "Andrew Lau" <<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, May 26, 2014 at 5:10 AM, Bob Doolittle <<a href="mailto:bob@doolittle.us.com">bob@doolittle.us.com</a>> wrote:<br>
><br>
> On 05/25/2014 02:51 PM, Joop wrote:<br>
>><br>
>> On 25-5-2014 19:38, Bob Doolittle wrote:<br>
>>><br>
>>><br>
>>> Also curious is that when I say "poweroff" it actually reboots and comes<br>
>>> up again. Could that be due to the timeouts on the way down?<br>
>>><br>
>> Ah, that's something my F19 host does too. Some more info: if engine<br>
>> hasn't been started on the host then I can shutdown it and it will poweroff.<br>
>> IF engine has been run on it then it will reboot.<br>
>> Its not vdsm (I think) because my shutdown sequence is (on my f19 host):<br>
>> service ovirt-agent-ha stop<br>
>> service ovirt-agent-broker stop<br>
>> service vdsmd stop<br>
>> ssh root@engine01 "init 0"<br>
>> init 0<br>
>><br>
>> I don't use maintenance mode because when I poweron my host (= my desktop)<br>
>> I want engine to power on automatically which it does most of the time<br>
>> within 10 min.<br>
><br>
><br>
> For comparison, I see this issue and I *do* use maintenance mode (because<br>
> presumably that's the 'blessed' way to shut things down and I'm scared to<br>
> mess this complex system up by straying off the beaten path ;). My process<br>
> is:<br>
><br>
> ssh root@engine "init 0"<br>
> (wait for "vdsClient -s 0 list | grep Status:" to show the vm as down)<br>
> hosted-engine --set-maintenance --mode=global<br>
> poweroff<br>
><br>
> And then on startup:<br>
> hosted-engine --set-maintenance --mode=none<br>
> hosted-engine --vm-start<br>
><br>
> There are two issues here. I am not sure if they are related or not.<br>
> 1. The NFS timeout during shutdown (Joop do you see this also? Or just #2?)<br>
> 2. The system reboot instead of poweroff (which messes up remote machine<br>
> management)<br>
><br>
> Thanks,<br>
> Bob<br>
><br>
><br>
>> I think wdmd or sanlock are causing the reboot instead of poweroff<br>
<br>
While searching for my issue of wdmd/sanlock not shutting down, I<br>
found this which may interest you both:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=888197" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=888197</a><br>
<br>
Specifically:<br>
"To shut down sanlock without causing a wdmd reboot, you can run the<br>
following command: "sanlock client shutdown -f 1"<br>
<br>
This will cause sanlock to kill any pid's that are holding leases,<br>
release those leases, and then exit.<br>
"<br>
<br>
>><br>
>> Joop<br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
>> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div>