Description of problem: mom can not be started on RHEV-H 3.6.0: [ 21.275662] localhost systemd[1]: [/usr/lib/systemd/system/momd.service:11] Unknown lvalue 'Timeout' in section 'Service' Version-Release number of selected component (if applicable): RHEV-H 3.6 build How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Maybe TimeoutSec should be used for the lvalue?
Martin, can you take point on this one please?
I will take care of that, but have this ever worked on any other systemd based system? Because I just saw a system where this was fine.
Ah... you are using a wrong service. It should be vdsm-mom.service as momd.service is the standalone mode.
Re-opening, just saw it on my lago setup: Jan 26 05:49:19 lago_basic_suite_3_6_host0 systemd: [/usr/lib/systemd/system/momd.service:11] Unknown lvalue 'Timeout' in section 'Service' [root@lago_basic_suite_3_6_host0 ~]# rpm -qa |grep mom mom-0.5.1-2.el7.noarch [root@lago_basic_suite_3_6_host0 ~]# cat /usr/lib/systemd/system/momd.service [Unit] Description=Memory Overcommitment Manager Daemon After=libvirtd.service [Service] Type=forking PIDFile=/var/run/momd.pid User=root Group=root ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file /var/run/momd.pid Timeout=60 Restart=on-abort [root@lago_basic_suite_3_6_host0 ~]# rpm -qa |grep vdsm vdsm-python-4.17.18-0.el7.centos.noarch vdsm-yajsonrpc-4.17.18-0.el7.centos.noarch vdsm-4.17.18-0.el7.centos.noarch vdsm-infra-4.17.18-0.el7.centos.noarch vdsm-hook-vmfex-dev-4.17.18-0.el7.centos.noarch vdsm-xmlrpc-4.17.18-0.el7.centos.noarch vdsm-jsonrpc-4.17.18-0.el7.centos.noarch vdsm-cli-4.17.18-0.el7.centos.noarch
Yaniv, which mom version are you using?
Yaniv, you are using a wrong service. Please disable mom.service and use mom-vdsm.service.
If mom.service is wrong, why is it enabled?
No idea really, vdsm uses mom-vdsm and that one conflicts with plain momd.
(In reply to Martin Sivák from comment #8) > Yaniv, you are using a wrong service. Please disable mom.service and use > mom-vdsm.service. This is what I've got when using Lago. I believe Lago hosts have 7.1 installed - I certainly did not install anything manually. If the base image has something wrong, we need to fix it - but I'd certainly expect VDSM installation to disable or warn or something on whatever is bothering it.
This is not related to ovirt specifically as we have mom-vdsm.service and we should hit that unless you started intentionally momd.service (this is used by some upstream users, not using ovirt) Martin/Andrej just needs to make sure the syntax of momd.service file is valid in this systemd version.
Martin I don't see any mom build in 3.6.6, can you check the status of this bug?
Take the one from 3.6.5...
Should this be on qa?
Moving to ovirt-3.6.6 for verification as 3.6.5 is already out.
please add verification steps
Check the systemd log for errors during unit loading and try to start momd service.
verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.6.2-0.1.el6 verification steps: service vdsmd stop service mom-vdsm stop service momd start systemctl daemon-reload journalctl -u momd.service ->> check that there are no errors about the Timeout.