Sep 01 00:39:19 aio.example.com systemd-vdsmd[1587]: Starting iscsid... Sep 01 00:40:48 aio.example.com systemd[1]: vdsmd.service operation timed out. Terminating.

From:Frank Wall <fw(a)moov.de&gt; Sent: Sunday 1st September 2013 16:40 To: users(a)ovirt.org Subject: Re: [Users] Host stuck in unresponsive state On 01.09.2013 01:28, Frank Wall wrote: > OK, for some reason it got stuck trying to start "iscsid" and > "multipathd". I was able to solve the issues with these services and > now the real error message is visible: Did some more fiddling... I removed my /etc/multipath.conf and started with the new file. Apparently there is a syntax error in this auto-generated config: [root@aio ~]# multipath -ll Sep 01 00:32:27 | multipath.conf +5, invalid keyword: getuid_callout Sep 01 00:32:27 | multipath.conf +18, invalid keyword: getuid_callout OK, I removed lines 5 and 18 and now multipathd is working again. This time it was possible to successfully start vdsmd afterwards: [root@aio ~]# systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: active (running) since So 2013-09-01 16:25:45 CEST; 1min 30s ago Process: 3138 ExecStart=/lib/systemd/systemd-vdsmd start (code=exited, status=0/SUCCESS) Main PID: 3285 (respawn) CGroup: name=systemd:/system/vdsmd.service ├─3285 /bin/bash -e /usr/share/vdsm/respawn --minlifetime 10 --daemon --masterpid /var/run/vdsm/respawn.pid /us... └─3288 /usr/bin/python /usr/share/vdsm/vdsm Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 client step 2 Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 parse_server_challenge() Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 ask_user_info() Sep 01 16:25:45 aio.exmaple.com vdsm[3288]: vdsm vds WARNING Unable to load the json rpc server module. Please make su...alled. Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 client step 2 Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 ask_user_info() Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 make_client_response() Sep 01 16:25:45 aio.exmaple.com python[3288]: DIGEST-MD5 client step 3 Sep 01 16:25:54 aio.exmaple.com vdsm[3288]: vdsm TaskManager.Task ERROR Task=`7fc3840c-1518-4260-9f27-ee20434b5a7a`::U... error Sep 01 16:25:54 aio.exmaple.com vdsm[3288]: vdsm TaskManager.Task ERROR Task=`82f757b5-a669-40fa-b09d-9cad90c971e1`::U... error Still, this doesn't feel right. I think vdsmd is just too unstable and vulnerable. Why did vdsmd core dump with another multipathd config in place? Why does it even have this strict dependency on multipathd? There have been severel similar reports in the last months and I wonder if there is a way to make vdsmd just more stable. It would be better to have vdsmd started and report an error to ovirt-engine, instead of failing to start the vdsmd service all the time. The current behaviour makes it hard to debug. Thanks - Frank _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

From: "Frank Wall" <fw(a)moov.de&gt; To: users(a)ovirt.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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users