<div dir="ltr">That was the issue. Found out yesterday that vdsm.log was somehow changed to root:root. Just now got a chance to put it back on the mailing list. How does the ownership of that file get cahnged. When the issue occurred I am certain there was no one on the system.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 11, 2013 at 2:15 PM, Joop <span dir="ltr"><<a href="mailto:jvdwege@xs4all.nl" target="_blank">jvdwege@xs4all.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">Dan Kenigsberg wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Apr 10, 2013 at 08:59:01AM -0500, Tony Feldmann wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am having a strange issue in my ovirt cluster. I have 2 hosts, 1 running<br>
engine and added as a host and one other system added as a host. Both<br>
systems are running gluster across local disks for shared storage.<br>
Everything was working fine until last night, where my system that is also<br>
running the engine when unresponsive in the admin page. All vms were still<br>
running that were on the host. I shut down the vms that were on the host<br>
from within the guest os as I was not able to do anything to the vm with<br>
the host in unresponsive state. After getting the vms off and rebooting<br>
the host, the vdsmd service says that it is running, but it continually<br>
restarts the vdsm process and dumps out these messages: detected unhandled<br>
Python exception in '/usr/share/vdsm/vdsm'. All services say they are up<br>
and running but the host stays in unresponsive state and the vdsm process<br>
keeps respawning. There is also no data in the vdsm.log. Can anyone shed<br>
any light on this for me?<br>
<br>
</blockquote>
<br>
<a href="mailto:vdsm-devel@fedorahosted.org" target="_blank">vdsm-devel@fedorahosted.org</a> may be a better place to ask vdsm-specific<br>
questions.<br>
<br>
Could you log into the non-operational host as root, and stop the vdsm<br>
service.<br>
<br>
Then become the vdsm user with<br>
<br>
su -s /bin/bash - vdsm<br>
<br>
and run /usr/share/vdsm/vdsm manually. Do you see anything in<br>
particular?<br>
<br>
<br>
</blockquote></div></div>
Please have a look at the permissions/owner of /var/log/vdsm/vdsm.log. Should be vdsm:kvm and not root:root<span class="HOEnZb"><font color="#888888"><br>
<br>
Joop<br>
<br>
</font></span></blockquote></div><br></div>