<div dir="ltr">There wasn't actually any info in syslog other than logging that there was a python exception. I actually had to track down the python abort file to find that it was getting permission errors on the log file.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 14, 2013 at 3:28 AM, Yaniv Bronheim <span dir="ltr"><<a href="mailto:ybronhei@redhat.com" target="_blank">ybronhei@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If only you would accept <a href="http://gerrit.ovirt.org/#/c/10313" target="_blank">http://gerrit.ovirt.org/#/c/10313</a>, Tony could manage to check the syslog for reports and fix it much faster.. :)<br>
Both patches should be backported IMHO<br>
<br>
Thanks,<br>
Yaniv.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
----- Original Message -----<br>
> From: "Dan Kenigsberg" <<a href="mailto:danken@redhat.com">danken@redhat.com</a>><br>
> To: "Tony Feldmann" <<a href="mailto:trfeldmann@gmail.com">trfeldmann@gmail.com</a>>, "Yaniv Bronheim" <<a href="mailto:ybronhei@redhat.com">ybronhei@redhat.com</a>><br>
> Cc: "Joop" <<a href="mailto:jvdwege@xs4all.nl">jvdwege@xs4all.nl</a>>, <a href="mailto:users@ovirt.org">users@ovirt.org</a>, <a href="mailto:vdsm-devel@fedorahosted.org">vdsm-devel@fedorahosted.org</a><br>
> Sent: Friday, April 12, 2013 12:33:07 AM<br>
> Subject: Re: [Users] vdsm unresponsive with python exception<br>
><br>
> On Thu, Apr 11, 2013 at 03:51:07PM -0500, Tony Feldmann wrote:<br>
> > That was the issue. Found out yesterday that vdsm.log was somehow changed<br>
> > to root:root. Just now got a chance to put it back on the mailing list.<br>
> > How does the ownership of that file get cahnged. When the issue occurred I<br>
> > am certain there was no one on the system.<br>
><br>
> <a href="http://gerrit.ovirt.org/#/c/12940/" target="_blank">http://gerrit.ovirt.org/#/c/12940/</a> (Separating supervdsm log to<br>
> supervdsm.log file) solves the issue. unfortunately, only on the master<br>
> branch of vdsm.<br>
><br>
> I think that this is a nasty issue that has to be backported to the<br>
> ovirt-3.2 branch as well, and merits to be part of ovirt-3.2.2.<br>
><br>
> Regards,<br>
> Dan.<br>
><br>
> ><br>
> ><br>
> > On Thu, Apr 11, 2013 at 2:15 PM, Joop <<a href="mailto:jvdwege@xs4all.nl">jvdwege@xs4all.nl</a>> wrote:<br>
> ><br>
> > > Dan Kenigsberg wrote:<br>
> > ><br>
> > >> On Wed, Apr 10, 2013 at 08:59:01AM -0500, Tony Feldmann wrote:<br>
> > >><br>
> > >><br>
> > >>> I am having a strange issue in my ovirt cluster. I have 2 hosts, 1<br>
> > >>> 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<br>
> > >>> also<br>
> > >>> running the engine when unresponsive in the admin page. All vms were<br>
> > >>> still<br>
> > >>> running that were on the host. I shut down the vms that were on the<br>
> > >>> host<br>
> > >>> from within the guest os as I was not able to do anything to the vm<br>
> > >>> with<br>
> > >>> the host in unresponsive state. After getting the vms off and<br>
> > >>> 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<br>
> > >>> unhandled<br>
> > >>> Python exception in '/usr/share/vdsm/vdsm'. All services say they are<br>
> > >>> up<br>
> > >>> and running but the host stays in unresponsive state and the vdsm<br>
> > >>> process<br>
> > >>> keeps respawning. There is also no data in the vdsm.log. Can anyone<br>
> > >>> shed<br>
> > >>> any light on this for me?<br>
> > >>><br>
> > >>><br>
> > >><br>
> > >> <a href="mailto:vdsm-devel@fedorahosted.org">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>
> > >><br>
> > > Please have a look at the permissions/owner of /var/log/vdsm/vdsm.log.<br>
> > > Should be vdsm:kvm and not root:root<br>
> > ><br>
> > > Joop<br>
> > ><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>
><br>
><br>
</div></div></blockquote></div><br></div>