On Mon, Aug 26, 2019 at 12:44 PM Ales Musil <amusil@redhat.com> wrote:
On Mon, Aug 26, 2019 at 12:30 PM Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
On Mon, Aug 26, 2019 at 11:58 AM Ales Musil <amusil@redhat.com> wrote:
I can see that MOM is failing to start because some of the MOM dependencies is not starting. Can you please post output from 'systemctl status momd'?
● momd.service - Memory Overcommitment Manager Daemon Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor preset: disabled) Active: inactive (dead)
perhaps any other daemon status? Or any momd related log file generated?
BTW: I see on a running oVirt 4.3.5 node from another environment that the status of momd is the same inactive (dead)
What happens if you try to start the momd?
[root@ovirt01 ~]# systemctl status momd ● momd.service - Memory Overcommitment Manager Daemon Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor preset: disabled) Active: inactive (dead) [root@ovirt01 ~]# systemctl start momd [root@ovirt01 ~]# [root@ovirt01 ~]# systemctl status momd -l ● momd.service - Memory Overcommitment Manager Daemon Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2019-08-26 18:10:20 CEST; 6s ago Process: 18417 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file /var/run/momd.pid (code=exited, status=0/SUCCESS) Main PID: 18419 (code=exited, status=0/SUCCESS) Aug 26 18:10:20 ovirt01.mydomain systemd[1]: Starting Memory Overcommitment Manager Daemon... Aug 26 18:10:20 ovirt01.mydomain systemd[1]: momd.service: Supervising process 18419 which is not our child. We'll most likely not notice when it exits. Aug 26 18:10:20 ovirt01.mydomain systemd[1]: Started Memory Overcommitment Manager Daemon. Aug 26 18:10:20 ovirt01.mydomain python[18419]: No worthy mechs found [root@ovirt01 ~]# [root@ovirt01 ~]# ps -fp 18419 UID PID PPID C STIME TTY TIME CMD [root@ovirt01 ~]# [root@ovirt01 vdsm]# ps -fp 18417 UID PID PPID C STIME TTY TIME CMD [root@ovirt01 vdsm]# No log file update under /var/log/vdsm [root@ovirt01 vdsm]# ls -lt | head -5 total 118972 -rw-r--r--. 1 root root 3406465 Aug 23 00:25 supervdsm.log -rw-r--r--. 1 root root 73621 Aug 23 00:25 upgrade.log -rw-r--r--. 1 vdsm kvm 0 Aug 23 00:01 vdsm.log -rw-r--r--. 1 vdsm kvm 538480 Aug 22 23:46 vdsm.log.1.xz [root@ovirt01 vdsm]# Gianluca