11:28 p.m.
This is a multi-part message in MIME format.
--------------030500060604080107050603
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On 14-3-2016 10:43, Allon Mureinik wrote:
I have noticed the same behaviour but not on server hardware
but on my
workstations which I use as a ovirt test setup.
One would expect that a shutdown on a host would shut it down cleanly
but the only way to get that is to run a small script that will take
care of:
- service ovirt-ha-agent/broker stop
- shutting down engine if it runs on this host
- service vdsmd stop
- service sanlock stop (takes quite a bit of time (~2min?))
- umount whatever is needed
- service nfs stop
- shutdown
This will poweroff my host which normally runs my hosted-engine
everytime. Sanlock seems to be indirectly the problem. wdmd(?) (watchdog
daemon) seems able to keep the host from powering off, most of the time
it will result in a reboot, or hanging at 'powering off'
I spend quite a bit of time looking into logs but have not been able to
find anything conclusive, could be my problem not knowing which log to
look at or to dig up enough info to find the root cause.
Joop
--------------030500060604080107050603
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html <head <meta content="text/html;
charset=windows-1252"
http-equiv="Content-Type"
</head <body
bgcolor="#FFFFFF" text="#000000"
<div class="moz-cite-prefix">On 14-3-2016 10:43, Allon Mureinik
wrote:<br </div <blockquote
cite="mid:CADgXf3ynGobo4eBzAXGN2tQDa-Z1NG6cL4xz7oe8_7khgy=VBw@mail.gmail.com"
type="cite" <div
dir="ltr" <div
class="gmail_default"
style="font-family:monospace,monospace">Odd. Never seen such
behavior in any of our set ups.</div
<div class="gmail_default"
style="font-family:monospace,monospace">Can you please include
vdsm's logs, sanlock's logs and /var/log/messages?</div <div class="gmail_default"
style="font-family:monospace,monospace"><br </div
</div </blockquote I have noticed the same behaviour but not on server
hardware but on
my workstations which I use as a ovirt test setup.<br One
would expect that a shutdown on a host would shut it down
cleanly but the only way to get that is to run a small script that
will take care of:<br - service ovirt-ha-agent/broker
stop<br - shutting down engine if it
runs on this host<br - service vdsmd stop<br - service sanlock stop (takes quite a bit of time
(~2min?))<br - umount whatever is
needed<br - service nfs stop<br - shutdown<br
<br This will poweroff my host which normally runs my
hosted-engine
everytime. Sanlock seems to be indirectly the problem. wdmd(?)
(watchdog daemon) seems able to keep the host from powering off,
most of the time it will result in a reboot, or hanging at 'powering
off'<br <br I spend quite a bit of time looking into logs but have not
been able
to find anything conclusive, could be my problem not knowing which
log to look at or to dig up enough info to find the root cause.<br <br
Joop<br <br </body
</html
--------------030500060604080107050603--
Odd. Never seen such behavior in any of our set ups.
Can you please include vdsm's logs, sanlock's logs and /var/log/message=
s?