VDSM fails after a while
Hi, We recently upgraded vdsm on a host using the webadmin. After activating it, it kept failing so we tried to activate it back via 'systemctl start vdsmd'. # systemctl start vdsmd Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details. Having a look at the status of the process I see: # systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since vie 2017-05-26 11:02:41 WEST; 14s ago Process: 25018 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE) may 26 11:02:40 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:40 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:40 systemd[1]: vdsmd.service failed. may 26 11:02:41 systemd[1]: vdsmd.service holdoff time over, scheduling restart. may 26 11:02:41 systemd[1]: start request repeated too quickly for vdsmd.service may 26 11:02:41 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:41 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:41 systemd[1]: vdsmd.service failed. To check what happened I run the vdsm_init_common.sh script by myself and saw: # /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_coredump vdsm: Running configure_vdsm_logs vdsm: Running wait_for_network vdsm: Running run_init_hooks vdsm: Running upgraded_version_check vdsm: Running check_is_configured Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is not configured for vdsm yet Modules sebool, passwd, libvirt are not configured Error: One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'. If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.) vdsm: stopped during execute check_is_configured task (task returned with error code 1). ----- I run the 'vdsm-tool configure --force' command, it ends successfully and after that I can start the vdsmd process. But... after a while it fails again and I need to re-run the same command all the time. Is this a known bug? any temporary workaround? Versions: vdsm-4.19.15-1.el7.centos.x86_64 libvirt-2.0.0-10.el7_3.5.x86_64 Thanks. Regards.
On 26 May 2017, at 12:07, nicolas@devels.es wrote:
Hi,
We recently upgraded vdsm on a host using the webadmin. After activating it, it kept failing so we tried to activate it back via 'systemctl start vdsmd'.
# systemctl start vdsmd Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details.
Having a look at the status of the process I see:
# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since vie 2017-05-26 11:02:41 WEST; 14s ago Process: 25018 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)
may 26 11:02:40 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:40 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:40 systemd[1]: vdsmd.service failed. may 26 11:02:41 systemd[1]: vdsmd.service holdoff time over, scheduling restart. may 26 11:02:41 systemd[1]: start request repeated too quickly for vdsmd.service may 26 11:02:41 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:41 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:41 systemd[1]: vdsmd.service failed.
To check what happened I run the vdsm_init_common.sh script by myself and saw:
# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_coredump vdsm: Running configure_vdsm_logs vdsm: Running wait_for_network vdsm: Running run_init_hooks vdsm: Running upgraded_version_check vdsm: Running check_is_configured Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is not configured for vdsm yet Modules sebool, passwd, libvirt are not configured
so when that happens, can you check the content of e.g. /etc/libvirt/libvirtd.conf if it contains the vdsm config at the end? Is it replaced by something you may run in your environment? Are there other packages pending upgrade? Thanks, michal
Error:
One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'.
If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.)
vdsm: stopped during execute check_is_configured task (task returned with error code 1).
-----
I run the 'vdsm-tool configure --force' command, it ends successfully and after that I can start the vdsmd process. But... after a while it fails again and I need to re-run the same command all the time.
Is this a known bug? any temporary workaround?
Versions:
vdsm-4.19.15-1.el7.centos.x86_64 libvirt-2.0.0-10.el7_3.5.x86_64
Thanks.
Regards.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
El 2017-05-26 11:24, Michal Skrivanek escribió:
On 26 May 2017, at 12:07, nicolas@devels.es wrote:
Hi,
We recently upgraded vdsm on a host using the webadmin. After activating it, it kept failing so we tried to activate it back via 'systemctl start vdsmd'.
# systemctl start vdsmd Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details.
Having a look at the status of the process I see:
# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since vie 2017-05-26 11:02:41 WEST; 14s ago Process: 25018 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)
may 26 11:02:40 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:40 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:40 systemd[1]: vdsmd.service failed. may 26 11:02:41 systemd[1]: vdsmd.service holdoff time over, scheduling restart. may 26 11:02:41 systemd[1]: start request repeated too quickly for vdsmd.service may 26 11:02:41 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:41 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:41 systemd[1]: vdsmd.service failed.
To check what happened I run the vdsm_init_common.sh script by myself and saw:
# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_coredump vdsm: Running configure_vdsm_logs vdsm: Running wait_for_network vdsm: Running run_init_hooks vdsm: Running upgraded_version_check vdsm: Running check_is_configured Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is not configured for vdsm yet Modules sebool, passwd, libvirt are not configured
so when that happens, can you check the content of e.g. /etc/libvirt/libvirtd.conf if it contains the vdsm config at the end? Is it replaced by something you may run in your environment? Are there other packages pending upgrade?
Ok, indeed Chef is doing weird things as even if the package is installed, it's reinstalling it everytime it runs. Thanks!
Thanks, michal
Error:
One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'.
If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.)
vdsm: stopped during execute check_is_configured task (task returned with error code 1).
-----
I run the 'vdsm-tool configure --force' command, it ends successfully and after that I can start the vdsmd process. But... after a while it fails again and I need to re-run the same command all the time.
Is this a known bug? any temporary workaround?
Versions:
vdsm-4.19.15-1.el7.centos.x86_64 libvirt-2.0.0-10.el7_3.5.x86_64
Thanks.
Regards.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
El 2017-05-26 12:00, nicolas@devels.es escribió:
El 2017-05-26 11:24, Michal Skrivanek escribió:
On 26 May 2017, at 12:07, nicolas@devels.es wrote:
Hi,
We recently upgraded vdsm on a host using the webadmin. After activating it, it kept failing so we tried to activate it back via 'systemctl start vdsmd'.
# systemctl start vdsmd Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details.
Having a look at the status of the process I see:
# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since vie 2017-05-26 11:02:41 WEST; 14s ago Process: 25018 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)
may 26 11:02:40 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:40 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:40 systemd[1]: vdsmd.service failed. may 26 11:02:41 systemd[1]: vdsmd.service holdoff time over, scheduling restart. may 26 11:02:41 systemd[1]: start request repeated too quickly for vdsmd.service may 26 11:02:41 systemd[1]: Failed to start Virtual Desktop Server Manager. may 26 11:02:41 systemd[1]: Unit vdsmd.service entered failed state. may 26 11:02:41 systemd[1]: vdsmd.service failed.
To check what happened I run the vdsm_init_common.sh script by myself and saw:
# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start vdsm: Running mkdirs vdsm: Running configure_coredump vdsm: Running configure_vdsm_logs vdsm: Running wait_for_network vdsm: Running run_init_hooks vdsm: Running upgraded_version_check vdsm: Running check_is_configured Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is not configured for vdsm yet Modules sebool, passwd, libvirt are not configured
so when that happens, can you check the content of e.g. /etc/libvirt/libvirtd.conf if it contains the vdsm config at the end? Is it replaced by something you may run in your environment? Are there other packages pending upgrade?
Ok, indeed Chef is doing weird things as even if the package is installed, it's reinstalling it everytime it runs.
To be more specific, all our configuration is managed with Chef. Up until this vdsm version (4.19.15-1.el7.centos.x86_64), vdsm had a dependency to 'ntp'. As of now, the dependency was changed to chrony (a logical change BTW). So our chef configuration was forcing installing ntp, which uninstalled vdsm for dependencies and then it reinstalled vdsm, but unconfigured. Thanks. Regards.
Thanks!
Thanks, michal
Error:
One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [--module module-name]'.
If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.)
vdsm: stopped during execute check_is_configured task (task returned with error code 1).
-----
I run the 'vdsm-tool configure --force' command, it ends successfully and after that I can start the vdsmd process. But... after a while it fails again and I need to re-run the same command all the time.
Is this a known bug? any temporary workaround?
Versions:
vdsm-4.19.15-1.el7.centos.x86_64 libvirt-2.0.0-10.el7_3.5.x86_64
Thanks.
Regards.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Michal Skrivanek -
nicolas＠devels.es