On Sun, Mar 31, 2019 at 7:36 AM Eyal Shenitzky <eshen...@redhat.com> wrote: > > > > On Thu, Mar 28, 2019 at 4:04 PM Marcin Sobczyk <msobc...@redhat.com> wrote: >> >> Hi, >> >> are you sure it's because of 'kdump'? 'vdsmd' lists 'kdump' as a 'wants' >> dependency, not 'requires' one. >> Did you try running 'vdsm-tool configure' possibly with '--force'? >> >> Regards, Marcin > > Hi Marcin, > > Yes I tried to run vdsm-tool confiure --force but still the same status. > > If kdum is not requiered, is there a way to remove it from vdsm dependency > list? (localy)
Marcin says that it's already not listed as a hard requirement, only as a "soft" one, which should not stop vdsm. Apparently, something else causes vdsmd service to fail. You can drop kdump altogether if you edit your /usr/lib/systemd/system/vdsmd.service >> >> On 3/28/19 1:52 PM, Eyal Shenitzky wrote: >> >> Hi, >> >> Does someone ever encountered on failure to restart vdsmd due to the >> following issue: >> >> # journalctl -xe >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com kdumpctl[8926]: kexec: failed to >> load kdump kernel >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com kdumpctl[8926]: Starting kdump: >> [FAILED] >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com systemd[1]: kdump.service: Main >> process exited, code=exited, status=1/FAILURE >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com systemd[1]: kdump.service: Failed >> with result 'exit-code'. >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com systemd[1]: Failed to start Crash >> recovery kernel arming. >> -- Subject: Unit kdump.service has failed >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit kdump.service has failed. >> -- >> -- The result is failed. >> Mar 28 14:46:46 dhcp-0-221.tlv.redhat.com audit[1]: SERVICE_START pid=1 >> uid=0 auid=4294967295 ses=4294967295 msg='unit=kdump comm="systemd" >> exe="/usr/lib/systemd/systemd" > >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com sudo[9143]: root : problem >> with defaults entries ; TTY=pts/0 ; PWD=/root/git/qemu/build ; USER=root ; >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: USER_ACCT pid=9143 >> uid=0 auid=0 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_localuser >> acct="root" exe="/usr/b> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com sudo[9143]: root : TTY=pts/0 ; >> PWD=/root/git/qemu/build ; USER=root ; COMMAND=/usr/bin/chcon >> --reference=/usr/bin/qemu-xxx /u> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: USER_CMD pid=9143 >> uid=0 auid=0 ses=1 msg='cwd="/root/git/qemu/build" >> cmd=6368636F6E202D2D7265666572656E63653D2F75737> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: CRED_REFR pid=9143 >> uid=0 auid=0 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_fprintd >> acct="root" exe="/usr/bin/sud> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com sudo[9143]: >> pam_systemd(sudo:session): Cannot create session: Already running in a >> session >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com sudo[9143]: >> pam_unix(sudo:session): session opened for user root by root(uid=0) >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: USER_START pid=9143 >> uid=0 auid=0 ses=1 msg='op=PAM:session_open >> grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limi> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com sudo[9143]: >> pam_unix(sudo:session): session closed for user root >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: USER_END pid=9143 >> uid=0 auid=0 ses=1 msg='op=PAM:session_close >> grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limit> >> Mar 28 14:47:15 dhcp-0-221.tlv.redhat.com audit[9143]: CRED_DISP pid=9143 >> uid=0 auid=0 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_fprintd >> acct="root" exe="/usr/bin/sud> >> lines 2486-2509/2509 (END) >> >> # 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: exit-code) since Thu 2019-03-28 14:46:45 IST; 5min >> ago >> Process: 9059 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh >> --post-stop (code=exited, status=0/SUCCESS) >> Process: 9048 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh >> --pre-start (code=exited, status=1/FAILURE) >> >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: vdsmd.service: Service >> hold-off time over, scheduling restart. >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: vdsmd.service: >> Scheduled restart job, restart counter is at 5. >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: Stopped Virtual >> Desktop Server Manager. >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: vdsmd.service: Start >> request repeated too quickly. >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: vdsmd.service: Failed >> with result 'exit-code'. >> Mar 28 14:46:45 dhcp-0-221.tlv.redhat.com systemd[1]: Failed to start >> Virtual Desktop Server Manager. >> >> >> Occurred to me on a Fedora 28 virtual machine that runs on rhel 7.6 host. >> >> Thanks >> >> -- >> Regards, >> Eyal Shenitzky >> >> _______________________________________________ >> Devel mailing list -- devel@ovirt.org >> To unsubscribe send an email to devel-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AUY64PMITE2WTVLKGWSJOT77VR5TW2OQ/ > > > > -- > Regards, > Eyal Shenitzky > _______________________________________________ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QOXVWWGCLLLINJ3NKUZXBMPYQG4ZC6IE/ _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RSM7SCLNZC2EMLN2OVFCBZON7LLCSHW5/
