[ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Yedidyah Bar David]

On Thu, Dec 17, 2015 at 2:50 PM, Willard Dennis <wdennis at nec-labs.com> wrote:
> This is from /var/log/messages —
>
> Dec 17 07:46:25 ovirt-node-01 systemd: vdsmd.service holdoff time over, scheduling restart.
> Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service stopping timed out. Killing.
> Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service: main process exited, code=killed, status=9/KILL
> Dec 17 07:46:35 ovirt-node-01 systemd: Unit mom-vdsm.service entered failed state.
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running mkdirs
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running configure_coredump
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running configure_vdsm_logs
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running wait_for_network
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running run_init_hooks
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running upgraded_version_check
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running check_is_configured
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: Current revision of multipath.conf detected, preserving
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: libvirt is already configured for vdsm
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running validate_configuration
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: SUCCESS: ssl configured to true. No conflicts
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running prepare_transient_repository
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running syslog_available
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running nwfilter
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running dummybr
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running tune_system
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_space
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_lo
> Dec 17 07:46:37 ovirt-node-01 vdsm: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
> Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service: main process exited, code=exited, status=1/FAILURE
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running run_final_hooks
> Dec 17 07:46:37 ovirt-node-01 systemd: Unit vdsmd.service entered failed state.
> Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service holdoff time over, scheduling restart.
>
>
> So, the message "vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration” — what would have to be set in sudden rules to allow this to succeed?

I thought this was already discussed some messages ago.

No idea, but you should check your sudo (and perhaps related? e.g. pam
or whatever)
conf. vdsm ships /etc/sudoers.d/50_vdsm which normally works.
If you changed it, or have some other conflicting configuration,
this might break it.

-- 
Didi