11:17 a.m.
You mean that : It's recommended to inst all VDSM and ovirt engine on separate server
?
Just like hosted engine ? In that way, the engine is installed on vm, and the vdsm is
installed on vm hosts.
But, my env not using hosted-engine, I use the standalone mode. Can I separate the VDSM
and engine on the standalone mode ?
-----Original Message-----
From: ybardavi(a)redhat.com <ybardavi(a)redhat.com> On Behalf Of Yedidyah Bar David
Sent: Wednesday, January 6, 2021 4:04 PM
To: tommy <sz_cuitao(a)163.com>
Cc: users <users(a)ovirt.org>
Subject: Re: [ovirt-users] Re: How to install and configure the monitoring portal ?
On Wed, Jan 6, 2021 at 9:32 AM tommy <sz_cuitao(a)163.com> wrote:
OK, I got it.
But ,after I reconfig, I found that is VDSM.service status is not right.
Is there any problem ?
Sorry, I have no idea.
You seem to run vdsm and engine on the same machine, right? This is called all-in-one, and
is not supported (used to be, until 3.6, several years ago).
Generally speaking, it's likely due to one of two things that engine-setup might have
done:
1. changed some configuration
2. updated some packages
You can check its log to see what it did.
[root@ooengh1 ~]# systemctl status vdsmd.service ● vdsmd.service -
Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset:
enabled)
Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; 2min 9s ago
Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop
(code=exited, status=0/SUCCESS)
Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
--pre-start (code=exited, status=1/FAILURE)
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop Server
Manager.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling
restart.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server Manager.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated
too quickly for vdsmd.service Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to
start Virtual Desktop Server Manager.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state.
Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
[root@ooengh1 ~]#
[root@ooengh1 ~]#
[root@ooengh1 ~]#
[root@ooengh1 ~]# systemctl start vdsmd.service Job for vdsmd.service
failed because the control process exited with error code. See "systemctl status
vdsmd.service" and "journalctl -xe" for details.
[root@ooengh1 ~]#
[root@ooengh1 ~]#
[root@ooengh1 ~]#
[root@ooengh1 ~]# journalctl -xe
--
-- The result is dependency.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start failed with
result 'dependency'.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job
for unit libvirtd.socket, ignoring: Invalid request descriptor
Perhaps this is the problem? Did libvirtd.socket work before?
Similarly for the others below.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency
job
for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan
06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for
unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06
15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for
unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06
15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit
libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com
systemd[1]: Cannot add dependency job for unit libvirtd-admin.socket, ignoring: Invalid
request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job
for unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56
ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling restart.
Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit
libvirtd.socket, ignoring: Unit is masked.
This is probably why it failed, but it's not clear what masked it. If it was also
masked before engine-setup, then perhaps this isn't the reason for vdsmd's
failure.
If you want, you can try 'systemctl unmask $UNIT' for one of more of these and see
if this helps.
If you suspect that this is due to updated packages, perhaps check 'dnf history'
and 'dnf history info $ID' to see what changed. To revert, you can try 'dnf
history undo $ID'.
Good luck and best regards,
--
Didi