Hi Frank, Can you attach vdsm+engine+messages logs so to better understand the issue?
The multipath and iscsi daemons shouldn't be causing you any trouble. Also the warnings you saw from multipathd about lines 5 and 18, are just warnings, multipath knows to ignore these lines (they are there for BC). Thanks, Yeela ----- Original Message ----- > From: "Frank Wall" <f...@moov.de> > To: firstname.lastname@example.org > Sent: Monday, September 2, 2013 12:41:27 PM > Subject: Re: [Users] Host stuck in unresponsive state > > Hi René, > > On 01.09.2013 19:55, René Koch wrote: > > I sometimes have (had) the same issues with all-in-one-setups, so I > > don't use local storage in all-in-one-setup anymore. > > thanks for the hint, I'll definitely give this a try if the problem > persists. As of yet I found that completely disabling all blocking > services helps stabilizing vdsmd-startup: > > [root@aio ~]# systemctl disable iscsid.service > [root@aio ~]# systemctl disable multipathd.service > > So far vdsmd starts and runs without any issues. > > > Thanks > - Frank > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users