<p dir="ltr"><br>
Il giorno 14/lug/2013 17:35, "Joop" <<a href="mailto:jvdwege@xs4all.nl">jvdwege@xs4all.nl</a>> ha scritto:<br>
><br>
> Gianluca Cecchi wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> oVirt 3.2.1 on F18<br>
>> One mgmt server + one host.<br>
>><br>
>> At some point the host had some problem and was rebooted<br>
>> at reboot ther was a problem because I got<br>
>><br>
>> detected unhandled Python exception in '/usr/share/vdsm/vdsm'<br>
>><br>
>> watching at<br>
>> <a href="http://www.ovirt.org/Troubleshooting">http://www.ovirt.org/Troubleshooting</a><br>
>><br>
>> I verified that for some reason vdsmd.log was root.root.<br>
>> So I set correct permissions and restarted the node.<br>
>><br>
>> <br>
><br>
> OK, I have had this too and managed to get out of it uptil now, maybe my experience will help you, may you have already tried what I'm going to suggest.<br>
> Put the host in maintenance, login with ssh on the host and restart the vdsmd service, activate the host.<br>
><br>
> I think I amended vdsms logrotate.conf with a user statement so that it wouldn't make root owner of vdsmd.log. There is a race condition that has been fixed I think in 3.2.2 and onwards.<br>
><br>
> Hope this helps you,<br>
><br>
> Joop<br>
><br>
I'm going to check but it seems to me that I could only select "host has rebooted" that failed because "unassigned" is not a good starting point to set it. <br>
Not sure I could put in maintenance. ..<br>
Gianluca</p>