This is a multi-part message in MIME format. --------------030607080205030709080601 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 26-03-2015 19:24, Christopher Pereira wrote:
Is it normal that 1) the engine stops VDSM during activation and 2) that VDSM stops or restarts the storage during shutdown?
Well, no wonder that the engine-storage disappears since the gluster process is a child-process of the vdsmd.service CGroup: /system.slice/vdsmd.service ├─14895 /usr/bin/python /usr/share/vdsm/vdsm ├─14964 /usr/libexec/ioprocess --read-pipe-fd 43 --write-pipe-fd 42 --max-threads 10 --ma ├─15836 /usr/libexec/ioprocess --read-pipe-fd 49 --write-pipe-fd 48 --max-threads 10 --ma * ├─15911 /usr/sbin/glusterfs --volfile-server=h2.imatronix.com --volfile-id=engine /rhev/d* └─15922 /usr/libexec/ioprocess --read-pipe-fd 61 --write-pipe-fd 60 --max-threads 10 --ma A workarround is to mount the engine-storage manually, so that restarting vdsmd on the host doesn't kill the engine VM. --------------030607080205030709080601 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 26-03-2015 19:24, Christopher Pereira wrote:<br> <blockquote cite="mid:55148720.3060607@imatronix.cl" type="cite"> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> Is it normal that 1) the engine stops VDSM during activation and 2) that VDSM stops or restarts the storage during shutdown?<br> </blockquote> <br> Well, no wonder that the engine-storage disappears since the gluster process is a child-process of the vdsmd.service<br> <br> CGroup: /system.slice/vdsmd.service<br> ├─14895 /usr/bin/python /usr/share/vdsm/vdsm<br> ├─14964 /usr/libexec/ioprocess --read-pipe-fd 43 --write-pipe-fd 42 --max-threads 10 --ma<br> ├─15836 /usr/libexec/ioprocess --read-pipe-fd 49 --write-pipe-fd 48 --max-threads 10 --ma<br> <b> ├─15911 /usr/sbin/glusterfs --volfile-server=h2.imatronix.com --volfile-id=engine /rhev/d</b><br> └─15922 /usr/libexec/ioprocess --read-pipe-fd 61 --write-pipe-fd 60 --max-threads 10 --ma<br> <br> A workarround is to mount the engine-storage manually, so that restarting vdsmd on the host doesn't kill the engine VM.<br> <br> </body> </html> --------------030607080205030709080601--