Created attachment 1222224 [details] messages Description of problem: Restart of vdsmd service kills the MOM service(mom-vdsm) Under message log I can see: Nov 20 15:41:22 master-vds10 systemd: Reloading. Nov 20 15:41:22 master-vds10 systemd: Unit virtlockd.service cannot be reloaded because it is inactive. Nov 20 15:41:22 master-vds10 systemd: Unit virtlogd.service cannot be reloaded because it is inactive. Nov 20 15:41:22 master-vds10 systemd: Stopping MOM instance configured for VDSM purposes... Nov 20 15:41:32 master-vds10 systemd: mom-vdsm.service stop-sigterm timed out. Killing. Nov 20 15:41:33 master-vds10 journal: vdsm MOM WARNING MOM not available. Nov 20 15:41:33 master-vds10 journal: vdsm MOM WARNING MOM not available, KSM stats will be missing. Version-Release number of selected component (if applicable): vdsm-4.18.16-1.el7ev.x86_64 How reproducible: Always Steps to Reproduce: 1. Check that mom-vdsm service is running(# systemctl status mom-vdsm) 2. Restart vdsmd service (# systemctl restart vdsmd) 3. Actual results: After vdsmd service restart mom-vdsm service is dead # systemctl status mom-vdsm ● mom-vdsm.service - MOM instance configured for VDSM purposes Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service; enabled; vendor preset: enabled) Active: inactive (dead) since Sun 2016-11-20 17:45:00 IST; 14min ago Process: 10947 ExecStart=/usr/sbin/momd -c /etc/vdsm/mom.conf (code=exited, status=0/SUCCESS) Main PID: 10947 (code=exited, status=0/SUCCESS) Expected results: After vdsmd restart mom-vdsm service must be alive. Additional info: It happens also when I upgrade vdsm or install it from scratch
Since when? it was like that for few versions. any change in mom that now allows it to stay up when vdsmd is restarted? systemd takes care of restarting mom-vdsm. You can test such change to see if it really works by removing mom-vdsm from /usr/lib/systemd/system/vdsmd.service . But then vdsm also won't start mom when it gets up. I need to understand what is the expected behavior and why
Just restart MOM once more after the VDSM restarts. *** This bug has been marked as a duplicate of bug 1393012 ***
I believe the expected behavior that after vdsm restart, vdsm must restart mom also to be sure that all services that he needs are up. But I believe it better to talk to Martin about it. Also, it is really strange that I did not encounter such behavior before vdsm-4.18.16-1.el7ev.x86_64 I can see in the bug https://bugzilla.redhat.com/show_bug.cgi?id=1393012 that Shira encountered it on master, so maybe it the same change that exists under both packages.