Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

2015-12-20 Thread Will Dennis
Fair enough… I think the phrase goes “the problem with idiot-proofing is that 
they keep making bigger idiots…” :)

Are you saying that vdsm isn’t a sub-project of oVirt? Who created it then, and 
where else is it used?


On Dec 20, 2015, at 2:07 AM, Yedidyah Bar David 
> wrote:
Well, I can think of other things as well, such as doing such a test
during rpm/yum install stage, etc., but the question is how far should
we go - there are many other ways to break ovirt, and we can't
possibly consider all of them. That said, I guess patches are welcome
(but you'll need to discuss this with a vdsm maintainer, not me,
probably on gerrit and not here).

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

2015-12-20 Thread Yedidyah Bar David
On Sun, Dec 20, 2015 at 9:05 PM, Will Dennis  wrote:
> Fair enough… I think the phrase goes “the problem with idiot-proofing is that 
> they keep making bigger idiots…” :)
>
> Are you saying that vdsm isn’t a sub-project of oVirt?

It is, but I am not a maintainer of it :-)

> Who created it then, and where else is it used?

Not sure, it's open-source after all.

>
>
> On Dec 20, 2015, at 2:07 AM, Yedidyah Bar David 
> > wrote:
> Well, I can think of other things as well, such as doing such a test
> during rpm/yum install stage, etc., but the question is how far should
> we go - there are many other ways to break ovirt, and we can't
> possibly consider all of them. That said, I guess patches are welcome
> (but you'll need to discuss this with a vdsm maintainer, not me,
> probably on gerrit and not here).
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

2015-12-19 Thread Yedidyah Bar David
On Thu, Dec 17, 2015 at 6:45 PM, Will Dennis <wden...@nec-labs.com> wrote:
> The vdsmd startup failing problem is now resolved :) The root cause was that 
> the /etc/sudoers file (that we maintain a customized version of which thru 
> Ansible) was missing the "#includedir /etc/sudoers.d" stanza, which caused a 
> sudo problem with the vdsmd startup, since the sudoers include file "50-vdsm" 
> wasn't being parsed.
>
> In going back and reviewing the thread, this was the first post that pointed 
> out the real problem...
>
> -Original Message-
> From: Fabian Deutsch [mailto:fdeutsch at redhat.com]
> Sent: Tuesday, December 01, 2015 12:58 AM
> To: Will Dennis
> Cc: Simone Tiraboschi; users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
> start
>
> On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis  wrote:
>> Any clues out of the strace of vdsm?
>
> read(9, "sudo: a password is required\n", 4096) = 29
>
> Could it be that sudo is not configured to operate passwordless?
>
> The strat-up can then fail, because sudo requires a ty, but this isn't 
> available during service start.
>
> - fabian
>
>> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi  
>> wrote:
>>
>>> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis  
>>> wrote:
>>> [root at ovirt-node-01 ~]# sudo -u vdsm /bin/bash
>>> bash-4.2$ /usr/share/vdsm/vdsm
>>> bash-4.2$ echo $?
>>> 1
>>
>> Can you please use strace on it?
>
> -Message End-
>
> However, not knowing about the missing sudoers include file, we continued to 
> chase a vdsm config problem (uninstall / reinstall vdsm RPM pkgs, & use 
> "vdsm-tool configure --force")
>
> Shame on me, it looks like I didn't think to check /var/log/messages for 
> "vdsm"-string entries until today, where we found the "vdsm user could not 
> manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to 
> run sudo']). Verify sudoer rules configuration” message that ultimately led 
> to the solution :(
>
> However, not sure if it's possible to do so, but could /usr/share/vdsm/vdsm 
> be made to emit a error to STDERR if it cannot run correctly? That's the only 
> thing I could think of that may have helped me to resolve this earlier with 
> what I did do...

Well, I can think of other things as well, such as doing such a test
during rpm/yum install stage, etc., but the question is how far should
we go - there are many other ways to break ovirt, and we can't
possibly consider all of them. That said, I guess patches are welcome
(but you'll need to discuss this with a vdsm maintainer, not me,
probably on gerrit and not here).

>
> Thanks for everyone's kind assistance, this really is a great community! :)

Thanks a lot for the time spent and the report!

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-18 Thread John Florian
On 12/17/2015 08:16 AM, Willard Dennis wrote:
> I checked and we do have a custom /etc/sudoers set —
>
>
> [root@ovirt-node-01 vdsm]# cat /etc/sudoers
> #
> # NECLA custom /etc/sudoers
> #
> # *** Managed by Ansible; do not edit manually,
> # file will be rewritten on next Ansible run! ***
> #
> # Do NOT add sudoers directly to this file; add them to the "wheel" group in 
> /etc/group
> #
>
> Defaultsrequiretty
> Defaults   !visiblepw
> Defaultsalways_set_home
> Defaultsenv_reset
> Defaultsenv_keep =  "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR 
> LS_COLORS"
> Defaultsenv_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
> Defaultsenv_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT 
> LC_MESSAGES"
> Defaultsenv_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
> Defaultsenv_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET 
> XAUTHORITY"
> Defaultssecure_path = /sbin:/bin:/usr/sbin:/usr/bin
> root  ALL=(ALL)   ALL
> %wheelALL=(ALL)   ALL
>
>
> What is missing / needs to be changed here to allow vdsmd to start correctly?

The first thing I'd do is to move that file aside and reinstall the
default from the package, i.e., yum/dnf reinstall sudo.  Make sure
ansible doesn't squash this while you test again.  If that resolves the
problem start looking at the differences between yours and the default
to isolate what & why.  If it doesn't resolve the problem then you need
to look elsewhere of course.

-- John Florian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Yedidyah Bar David
On Thu, Dec 17, 2015 at 2:45 PM, Willard Dennis  wrote:
> Sure, which ones would be useful?
>
> [root@ovirt-node-01 ~]# cd /var/log/vdsm/
> [root@ovirt-node-01 vdsm]# ls -la
> total 11520
> drwxr-xr-x   3 vdsm kvm 4096 Dec 17 04:34 .
> drwxr-xr-x. 13 root root4096 Dec 13 03:32 ..
> drwxr-xr-x   2 vdsm kvm6 Nov 24 05:42 backup
> -rw-r--r--   1 vdsm kvm0 Dec  1 23:42 connectivity.log
> -rw-r--r--   1 vdsm kvm   966994 Dec 17 07:20 mom.log
> -rw-r--r--   1 vdsm kvm  2097091 Dec 17 04:34 mom.log.1
> -rw-r--r--   1 vdsm kvm  2097117 Dec 16 22:34 mom.log.2
> -rw-r--r--   1 vdsm kvm  2097119 Dec 16 16:33 mom.log.3
> -rw-r--r--   1 vdsm kvm  2097120 Dec 16 10:32 mom.log.4
> -rw-r--r--   1 vdsm kvm  2097115 Dec 16 04:32 mom.log.5
> -rw-r--r--   1 root root  168714 Dec  2 10:30 supervdsm.log
> -rw-r--r--   1 root root3069 Oct 16 12:25 upgrade.log
> -rw-r--r--   1 vdsm kvm0 Dec  1 23:42 vdsm.log

Perhaps just upload all of them somewhere?

Also might be selinux? Please check/post also audit logs.

>
>
>> On Dec 17, 2015, at 2:51 AM, Fabian Deutsch  wrote:
>>
>> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis  
>> wrote:
>>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>>> install…
>>
>> Hey,
>>
>> so it looks like vdsm has an issue, can you provide some logs?
>>
>> - fabian
>>
>>
>> --
>> Fabian Deutsch 
>> RHEV Hypervisor
>> Red Hat
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Willard Dennis
Sure, which ones would be useful?

[root@ovirt-node-01 ~]# cd /var/log/vdsm/
[root@ovirt-node-01 vdsm]# ls -la
total 11520
drwxr-xr-x   3 vdsm kvm 4096 Dec 17 04:34 .
drwxr-xr-x. 13 root root4096 Dec 13 03:32 ..
drwxr-xr-x   2 vdsm kvm6 Nov 24 05:42 backup
-rw-r--r--   1 vdsm kvm0 Dec  1 23:42 connectivity.log
-rw-r--r--   1 vdsm kvm   966994 Dec 17 07:20 mom.log
-rw-r--r--   1 vdsm kvm  2097091 Dec 17 04:34 mom.log.1
-rw-r--r--   1 vdsm kvm  2097117 Dec 16 22:34 mom.log.2
-rw-r--r--   1 vdsm kvm  2097119 Dec 16 16:33 mom.log.3
-rw-r--r--   1 vdsm kvm  2097120 Dec 16 10:32 mom.log.4
-rw-r--r--   1 vdsm kvm  2097115 Dec 16 04:32 mom.log.5
-rw-r--r--   1 root root  168714 Dec  2 10:30 supervdsm.log
-rw-r--r--   1 root root3069 Oct 16 12:25 upgrade.log
-rw-r--r--   1 vdsm kvm0 Dec  1 23:42 vdsm.log


> On Dec 17, 2015, at 2:51 AM, Fabian Deutsch  wrote:
> 
> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis  wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
> 
> Hey,
> 
> so it looks like vdsm has an issue, can you provide some logs?
> 
> - fabian
> 
> 
> -- 
> Fabian Deutsch 
> RHEV Hypervisor
> Red Hat

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Willard Dennis
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?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Yedidyah Bar David
On Thu, Dec 17, 2015 at 2:50 PM, Willard Dennis  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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Willard Dennis
I checked and we do have a custom /etc/sudoers set —


[root@ovirt-node-01 vdsm]# cat /etc/sudoers
#
# NECLA custom /etc/sudoers
#
# *** Managed by Ansible; do not edit manually,
# file will be rewritten on next Ansible run! ***
#
# Do NOT add sudoers directly to this file; add them to the "wheel" group in 
/etc/group
#

Defaultsrequiretty
Defaults   !visiblepw
Defaultsalways_set_home
Defaultsenv_reset
Defaultsenv_keep =  "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR 
LS_COLORS"
Defaultsenv_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaultsenv_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT 
LC_MESSAGES"
Defaultsenv_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaultsenv_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET 
XAUTHORITY"
Defaultssecure_path = /sbin:/bin:/usr/sbin:/usr/bin
rootALL=(ALL)   ALL
%wheel  ALL=(ALL)   ALL


What is missing / needs to be changed here to allow vdsmd to start correctly?


> On Dec 17, 2015, at 7:54 AM, Yedidyah Bar David  wrote:
> 
> 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

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Willard Dennis
Took the easy way out on selinux…

[root@ovirt-node-01 vdsm]# sestatus
SELinux status: disabled


> On Dec 17, 2015, at 7:48 AM, Yedidyah Bar David  wrote:
> 
> 
> Perhaps just upload all of them somewhere?
> 
> Also might be selinux? Please check/post also audit logs.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Yedidyah Bar David
On Thu, Dec 17, 2015 at 2:53 PM, Willard Dennis  wrote:
> Took the easy way out on selinux…
>
> [root@ovirt-node-01 vdsm]# sestatus
> SELinux status: disabled

Up to you, but note that we do work hard to make sure things work
with it enabled.

>
>
> On Dec 17, 2015, at 7:48 AM, Yedidyah Bar David  wrote:
>
>
> Perhaps just upload all of them somewhere?
>
> Also might be selinux? Please check/post also audit logs.
>
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

2015-12-17 Thread Will Dennis
The vdsmd startup failing problem is now resolved :) The root cause was that 
the /etc/sudoers file (that we maintain a customized version of which thru 
Ansible) was missing the "#includedir /etc/sudoers.d" stanza, which caused a 
sudo problem with the vdsmd startup, since the sudoers include file "50-vdsm" 
wasn't being parsed.

In going back and reviewing the thread, this was the first post that pointed 
out the real problem...

-Original Message-
From: Fabian Deutsch [mailto:fdeutsch at redhat.com] 
Sent: Tuesday, December 01, 2015 12:58 AM
To: Will Dennis
Cc: Simone Tiraboschi; users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis  wrote:
> Any clues out of the strace of vdsm?

read(9, "sudo: a password is required\n", 4096) = 29

Could it be that sudo is not configured to operate passwordless?

The strat-up can then fail, because sudo requires a ty, but this isn't 
available during service start.

- fabian

> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi  
> wrote:
> 
>> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis  
>> wrote:
>> [root at ovirt-node-01 ~]# sudo -u vdsm /bin/bash
>> bash-4.2$ /usr/share/vdsm/vdsm
>> bash-4.2$ echo $?
>> 1
> 
> Can you please use strace on it?

-Message End-

However, not knowing about the missing sudoers include file, we continued to 
chase a vdsm config problem (uninstall / reinstall vdsm RPM pkgs, & use 
"vdsm-tool configure --force")

Shame on me, it looks like I didn't think to check /var/log/messages for 
"vdsm"-string entries until today, where we found the "vdsm user could not 
manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to 
run sudo']). Verify sudoer rules configuration” message that ultimately led to 
the solution :(

However, not sure if it's possible to do so, but could /usr/share/vdsm/vdsm be 
made to emit a error to STDERR if it cannot run correctly? That's the only 
thing I could think of that may have helped me to resolve this earlier with 
what I did do...

Thanks for everyone's kind assistance, this really is a great community! :)

-Will
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Willard Dennis
OK, should not have used the term “vanilla” I guess… I have customized the OS 
to fit into my environment (not so much with kickstart, mostly via Ansible) and 
of course have installed Gluster 3.7 and configured volumes for the engine and 
VM storage. So it’s not like it’s running on a completely stock CentOS 7 
install (that would be basically unusable for me…)

Doing a complete reinstall would be many hours of work (already have done that 
once to reconfigure Gluster) so not really interested in doing that…

I’d love to continue debugging; just frustrated that everything done so far has 
not worked (read thread for details…) and we cannot get the vdsmd service to 
run… I do very much appreciate the assistance of all the RHAT folks who have 
responded to this thread, you are my only hope of getting this stuff running, 
as I’m not an oVirt expert by far

-Will

> On Dec 17, 2015, at 1:40 AM, Yedidyah Bar David  wrote:
> 
> On Wed, Dec 16, 2015 at 11:52 PM, Willard Dennis  wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
> 
> (Only briefly skimming the history of this thread:)
> 
> If all you want is to have it up and running, I'd suggest reinstalling
> the OS and then try again. Quite likely you have there some local
> non-default configurations or something. If it still fails, I'd suggest
> to open a bug, describe exact flow, and attach all relevant logs. When
> you reinstall the OS, keep in mind that things like a custom kickstart
> file etc are also non-default configurations, so if you need them,
> attach them to the bug as well.
> 
> If you are aware of such non-default stuff but do need them, you
> basically have two choices:
> 1. Keep on debugging this til it works. We can try helping, but can't
> guess every change you did to your system. In particular, as Simone
> said before, sudo is configured to work out-of-the-box by default.
> 2. Try a clean vanilla OS install on another system and compare them
> to try and see what difference breaks. This can be done also on a VM
> with nested kvm, if you do not have a spare physical machine.
> 
> Best,
> -- 
> Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Yedidyah Bar David
On Thu, Dec 17, 2015 at 9:51 AM, Fabian Deutsch <fdeut...@redhat.com> wrote:
> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis <wden...@nec-labs.com> wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
>
> Hey,
>
> so it looks like vdsm has an issue, can you provide some logs?
>

Perhaps it's this one:

https://bugzilla.redhat.com/show_bug.cgi?id=1292178

> - fabian
>
>> Thanks
>> Will
>>
>>
>> On Dec 2, 2015, at 10:35 AM, Will Dennis <wden...@nec-labs.com> wrote:
>>
>> Ran the configure the first time and got an error...
>>
>> root@ovirt-node-01 ~> vdsm-tool configure --force
>>
>> Checking configuration status...
>>
>> Current revision of multipath.conf detected, preserving
>> libvirt is not configured for vdsm yet
>> FAILED: conflicting vdsm and libvirt-qemu tls configuration.
>> vdsm.conf with ssl=True requires the following changes:
>> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
>> qemu.conf: spice_tls=1.
>>
>> Running configure...
>> Reconfiguration of sebool is done.
>> Reconfiguration of passwd is done.
>> Reconfiguration of libvirt is done.
>>
>> Done configuring modules to VDSM.
>>
>> So, made the appropriate edits to libvirtd.conf and qemu.conf
>>
>> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/libvirtd.conf
>> listen_tls = 1
>> listen_tcp = 0
>> auth_tcp = "sasl"
>> auth_unix_rw="sasl"
>> ca_file="/etc/pki/vdsm/certs/cacert.pem"
>> cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
>> host_uuid="2b026fff-bae2-429f-9386-c60ffc5f3f32"
>> keepalive_interval=-1
>> key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
>> unix_sock_group="qemu"
>> unix_sock_rw_perms="0770"
>>
>> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/qemu.conf
>> spice_tls = 1
>> auto_dump_path="/var/log/core"
>> dynamic_ownership=0
>> lock_manager="sanlock"
>> remote_display_port_max=6923
>> remote_display_port_min=5900
>> save_image_format="lzop"
>> spice_tls=1
>> spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"
>>
>> Then re-ran the config...
>>
>> root@ovirt-node-01 ~> vdsm-tool configure --force
>>
>> Checking configuration status...
>>
>> Current revision of multipath.conf detected, preserving
>> libvirt is already configured for vdsm
>> SUCCESS: ssl configured to true. No conflicts
>>
>> Running configure...
>> Reconfiguration of sebool is done.
>> Reconfiguration of libvirt is done.
>>
>> Done configuring modules to VDSM.
>>
>> Sadly, vdsmd STILL fails to start...
>>
>> root@ovirt-node-01 ~> systemctl restart vdsmd
>> root@ovirt-node-01 ~> systemctl status vdsmd
>> vdsmd.service - Virtual Desktop Server Manager
>>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
>>Active: activating (auto-restart) (Result: exit-code) since Wed
>> 2015-12-02 10:30:47 EST; 1s ago
>>   Process: 6522 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
>> --post-stop (code=exited, status=0/SUCCESS)
>>   Process: 6506 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1
>> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>>   Process: 6433 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
>> --pre-start (code=exited, status=0/SUCCESS)
>> Main PID: 6506 (code=exited, status=1/FAILURE)
>>
>> Dec 02 10:30:47 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed
>> 
>> Dec 02 10:30:47 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over,
>> s
>> Hint: Some lines were ellipsized, use -l to show in full.
>>
>> :(
>>
>> From: Simone Tiraboschi [mailto:stira...@redhat.com]
>> Sent: Wednesday, December 02, 2015 3:57 AM
>> To: Will Dennis
>> Cc: Fabian Deutsch; users
>> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not
>> start
>>
>> [snip]
>>
>> Now can you please now configure it with:
>>   vdsm-tool configure --force
>>
>> Then you have to restart it
>>
>>
>
>
>
> --
> Fabian Deutsch <fdeut...@redhat.com>
> RHEV Hypervisor
> Red Hat
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-16 Thread Willard Dennis
Any thoughts on this issue?? This is holding up my project (oVirt hosted engine 
install won’t proceed if VDSM service is not running…)  Why am I even having 
such problems with the VDSM service? It’s on a vanilla CentOS 7 install…

Thanks
Will


> On Dec 2, 2015, at 10:35 AM, Will Dennis <wden...@nec-labs.com> wrote:
> 
> Ran the configure the first time and got an error...
>  
> root@ovirt-node-01 ~> vdsm-tool configure --force
>  
> Checking configuration status...
>  
> Current revision of multipath.conf detected, preserving
> libvirt is not configured for vdsm yet
> FAILED: conflicting vdsm and libvirt-qemu tls configuration.
> vdsm.conf with ssl=True requires the following changes:
> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
> qemu.conf: spice_tls=1.
>  
> Running configure...
> Reconfiguration of sebool is done.
> Reconfiguration of passwd is done.
> Reconfiguration of libvirt is done.
>  
> Done configuring modules to VDSM.
>  
> So, made the appropriate edits to libvirtd.conf and qemu.conf
>  
> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/libvirtd.conf
> listen_tls = 1
> listen_tcp = 0
> auth_tcp = "sasl"
> auth_unix_rw="sasl"
> ca_file="/etc/pki/vdsm/certs/cacert.pem"
> cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
> host_uuid="2b026fff-bae2-429f-9386-c60ffc5f3f32"
> keepalive_interval=-1
> key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
> unix_sock_group="qemu"
> unix_sock_rw_perms="0770"
>  
> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/qemu.conf
> spice_tls = 1
> auto_dump_path="/var/log/core"
> dynamic_ownership=0
> lock_manager="sanlock"
> remote_display_port_max=6923
> remote_display_port_min=5900
> save_image_format="lzop"
> spice_tls=1
> spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"
>  
> Then re-ran the config...
>  
> root@ovirt-node-01 ~> vdsm-tool configure --force
>  
> Checking configuration status...
>  
> Current revision of multipath.conf detected, preserving
> libvirt is already configured for vdsm
> SUCCESS: ssl configured to true. No conflicts
>  
> Running configure...
> Reconfiguration of sebool is done.
> Reconfiguration of libvirt is done.
>  
> Done configuring modules to VDSM.
>  
> Sadly, vdsmd STILL fails to start...
>  
> root@ovirt-node-01 ~> systemctl restart vdsmd
> root@ovirt-node-01 ~> systemctl status vdsmd
> vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
>Active: activating (auto-restart) (Result: exit-code) since Wed 2015-12-02 
> 10:30:47 EST; 1s ago
>   Process: 6522 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 6506 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 
> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>   Process: 6433 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --pre-start (code=exited, status=0/SUCCESS)
> Main PID: 6506 (code=exited, status=1/FAILURE)
>  
> Dec 02 10:30:47 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed 
> 
> Dec 02 10:30:47 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over, 
> s
> Hint: Some lines were ellipsized, use -l to show in full.
>  
> :(
>  
> From: Simone Tiraboschi [mailto:stira...@redhat.com 
> <mailto:stira...@redhat.com>] 
> Sent: Wednesday, December 02, 2015 3:57 AM
> To: Will Dennis
> Cc: Fabian Deutsch; users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
> start
>  
> [snip]
>  
> Now can you please now configure it with:
>   vdsm-tool configure --force
>  
> Then you have to restart it

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-16 Thread Yedidyah Bar David
On Wed, Dec 16, 2015 at 11:52 PM, Willard Dennis  wrote:
> Any thoughts on this issue?? This is holding up my project (oVirt hosted
> engine install won’t proceed if VDSM service is not running…)  Why am I even
> having such problems with the VDSM service? It’s on a vanilla CentOS 7
> install…

(Only briefly skimming the history of this thread:)

If all you want is to have it up and running, I'd suggest reinstalling
the OS and then try again. Quite likely you have there some local
non-default configurations or something. If it still fails, I'd suggest
to open a bug, describe exact flow, and attach all relevant logs. When
you reinstall the OS, keep in mind that things like a custom kickstart
file etc are also non-default configurations, so if you need them,
attach them to the bug as well.

If you are aware of such non-default stuff but do need them, you
basically have two choices:
1. Keep on debugging this til it works. We can try helping, but can't
guess every change you did to your system. In particular, as Simone
said before, sudo is configured to work out-of-the-box by default.
2. Try a clean vanilla OS install on another system and compare them
to try and see what difference breaks. This can be done also on a VM
with nested kvm, if you do not have a spare physical machine.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-16 Thread Fabian Deutsch
On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis <wden...@nec-labs.com> wrote:
> Any thoughts on this issue?? This is holding up my project (oVirt hosted
> engine install won’t proceed if VDSM service is not running…)  Why am I even
> having such problems with the VDSM service? It’s on a vanilla CentOS 7
> install…

Hey,

so it looks like vdsm has an issue, can you provide some logs?

- fabian

> Thanks
> Will
>
>
> On Dec 2, 2015, at 10:35 AM, Will Dennis <wden...@nec-labs.com> wrote:
>
> Ran the configure the first time and got an error...
>
> root@ovirt-node-01 ~> vdsm-tool configure --force
>
> Checking configuration status...
>
> Current revision of multipath.conf detected, preserving
> libvirt is not configured for vdsm yet
> FAILED: conflicting vdsm and libvirt-qemu tls configuration.
> vdsm.conf with ssl=True requires the following changes:
> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
> qemu.conf: spice_tls=1.
>
> Running configure...
> Reconfiguration of sebool is done.
> Reconfiguration of passwd is done.
> Reconfiguration of libvirt is done.
>
> Done configuring modules to VDSM.
>
> So, made the appropriate edits to libvirtd.conf and qemu.conf
>
> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/libvirtd.conf
> listen_tls = 1
> listen_tcp = 0
> auth_tcp = "sasl"
> auth_unix_rw="sasl"
> ca_file="/etc/pki/vdsm/certs/cacert.pem"
> cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
> host_uuid="2b026fff-bae2-429f-9386-c60ffc5f3f32"
> keepalive_interval=-1
> key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
> unix_sock_group="qemu"
> unix_sock_rw_perms="0770"
>
> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/qemu.conf
> spice_tls = 1
> auto_dump_path="/var/log/core"
> dynamic_ownership=0
> lock_manager="sanlock"
> remote_display_port_max=6923
> remote_display_port_min=5900
> save_image_format="lzop"
> spice_tls=1
> spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"
>
> Then re-ran the config...
>
> root@ovirt-node-01 ~> vdsm-tool configure --force
>
> Checking configuration status...
>
> Current revision of multipath.conf detected, preserving
> libvirt is already configured for vdsm
> SUCCESS: ssl configured to true. No conflicts
>
> Running configure...
> Reconfiguration of sebool is done.
> Reconfiguration of libvirt is done.
>
> Done configuring modules to VDSM.
>
> Sadly, vdsmd STILL fails to start...
>
> root@ovirt-node-01 ~> systemctl restart vdsmd
> root@ovirt-node-01 ~> systemctl status vdsmd
> vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
>Active: activating (auto-restart) (Result: exit-code) since Wed
> 2015-12-02 10:30:47 EST; 1s ago
>   Process: 6522 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 6506 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1
> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>   Process: 6433 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
> Main PID: 6506 (code=exited, status=1/FAILURE)
>
> Dec 02 10:30:47 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed
> 
> Dec 02 10:30:47 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over,
> s
> Hint: Some lines were ellipsized, use -l to show in full.
>
> :(
>
> From: Simone Tiraboschi [mailto:stira...@redhat.com]
> Sent: Wednesday, December 02, 2015 3:57 AM
> To: Will Dennis
> Cc: Fabian Deutsch; users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not
> start
>
> [snip]
>
> Now can you please now configure it with:
>   vdsm-tool configure --force
>
> Then you have to restart it
>
>



-- 
Fabian Deutsch <fdeut...@redhat.com>
RHEV Hypervisor
Red Hat
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-02 Thread Will Dennis
Ran the configure the first time and got an error...

root@ovirt-node-01 ~> vdsm-tool configure --force

Checking configuration status...

Current revision of multipath.conf detected, preserving
libvirt is not configured for vdsm yet
FAILED: conflicting vdsm and libvirt-qemu tls configuration.
vdsm.conf with ssl=True requires the following changes:
libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
qemu.conf: spice_tls=1.

Running configure...
Reconfiguration of sebool is done.
Reconfiguration of passwd is done.
Reconfiguration of libvirt is done.

Done configuring modules to VDSM.

So, made the appropriate edits to libvirtd.conf and qemu.conf

root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/libvirtd.conf
listen_tls = 1
listen_tcp = 0
auth_tcp = "sasl"
auth_unix_rw="sasl"
ca_file="/etc/pki/vdsm/certs/cacert.pem"
cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
host_uuid="2b026fff-bae2-429f-9386-c60ffc5f3f32"
keepalive_interval=-1
key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
unix_sock_group="qemu"
unix_sock_rw_perms="0770"

root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/qemu.conf
spice_tls = 1
auto_dump_path="/var/log/core"
dynamic_ownership=0
lock_manager="sanlock"
remote_display_port_max=6923
remote_display_port_min=5900
save_image_format="lzop"
spice_tls=1
spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"

Then re-ran the config...

root@ovirt-node-01 ~> vdsm-tool configure --force

Checking configuration status...

Current revision of multipath.conf detected, preserving
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts

Running configure...
Reconfiguration of sebool is done.
Reconfiguration of libvirt is done.

Done configuring modules to VDSM.

Sadly, vdsmd STILL fails to start...

root@ovirt-node-01 ~> systemctl restart vdsmd
root@ovirt-node-01 ~> systemctl status vdsmd
vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2015-12-02 
10:30:47 EST; 1s ago
  Process: 6522 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop 
(code=exited, status=0/SUCCESS)
  Process: 6506 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 
/dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
  Process: 6433 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start 
(code=exited, status=0/SUCCESS)
Main PID: 6506 (code=exited, status=1/FAILURE)

Dec 02 10:30:47 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed 
Dec 02 10:30:47 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over, s
Hint: Some lines were ellipsized, use -l to show in full.

:(

From: Simone Tiraboschi [mailto:stira...@redhat.com]
Sent: Wednesday, December 02, 2015 3:57 AM
To: Will Dennis
Cc: Fabian Deutsch; users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

[snip]

Now can you please now configure it with:
  vdsm-tool configure --force

Then you have to restart it


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-02 Thread Simone Tiraboschi
On Wed, Dec 2, 2015 at 5:56 AM, Willard Dennis <wden...@nec-labs.com> wrote:

> Did the following:
>
> 1) yum remove vdsm*
> […]
> Removed:
>   vdsm.noarch 0:4.17.10.1-0.el7.centos vdsm-cli.noarch
> 0:4.17.10.1-0.el7.centosvdsm-gluster.noarch 0:4.17.10.1-0.el7.centos
>   vdsm-infra.noarch 0:4.17.10.1-0.el7.centos   vdsm-jsonrpc.noarch
> 0:4.17.10.1-0.el7.centosvdsm-python.noarch 0:4.17.10.1-0.el7.centos
>   vdsm-xmlrpc.noarch 0:4.17.10.1-0.el7.centos  vdsm-yajsonrpc.noarch
> 0:4.17.10.1-0.el7.centos
>
> Dependency Removed:
>   ovirt-hosted-engine-ha.noarch 0:1.3.2.1-1.el7.centos
> ovirt-hosted-engine-setup.noarch 0:1.3.0-1.el7.centos
>
>
> 2) yum install vdsm vdsm-cli vdsm-gluster vdsm-infra vdsm-jsonrpc
> vdsm-python vdsm-xmlrpc vdsm-yajsonrpc
> […]
> Installed:
>   vdsm.noarch 0:4.17.11-0.el7.centos   vdsm-cli.noarch
> 0:4.17.11-0.el7.centos  vdsm-gluster.noarch 0:4.17.11-0.el7.centos
>   vdsm-infra.noarch 0:4.17.11-0.el7.centos vdsm-jsonrpc.noarch
> 0:4.17.11-0.el7.centos  vdsm-python.noarch 0:4.17.11-0.el7.centos
>   vdsm-xmlrpc.noarch 0:4.17.11-0.el7.centosvdsm-yajsonrpc.noarch
> 0:4.17.11-0.el7.centos
>
> 3) yum install ovirt-hosted-engine-setup ovirt-hosted-engine-ha
> […]
> Installed:
>   ovirt-hosted-engine-ha.noarch 0:1.3.3-1.el7.centos
>  ovirt-hosted-engine-setup.noarch 0:1.3.1-1.el7.centos
>
> Dependency Updated:
>   ovirt-host-deploy.noarch 0:1.4.1-1.el7.centos
>
>
> Result:
> [root@ovirt-node-01 ~]# systemctl start vdsmd
> Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and
> 'journalctl -xn' for details.
> [root@ovirt-node-01 ~]# systemctl status vdsmd.service
> vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
>Active: failed (Result: start-limit) since Tue 2015-12-01 23:55:05 EST;
> 14s ago
>   Process: 21336 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=1/FAILURE)
>  Main PID: 20589 (code=exited, status=1/FAILURE)
>
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop
> Server Manager.
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered
> failed state.
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server
> Manager...
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over,
> scheduling restart.
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Stopping Virtual Desktop Server
> Manager...
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server
> Manager...
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service start request
> repeated too quickly, refusing to start.
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop
> Server Manager.
> Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered
> failed state.
>
> Different error now, but vdsmd service still won’t restart correctly...
>

Now can you please now configure it with:
  vdsm-tool configure --force

Then you have to restart it


>
>
> On Dec 1, 2015, at 9:25 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
> On Tue, Dec 1, 2015 at 3:15 PM, Will Dennis <wden...@nec-labs.com> wrote:
>
>> I believe sudo is NOT setup for passwordless (then again, didn't see that
>> in any pre-req instructions...) Who would be the sudoer in this case?
>>
>
> It's not required to take any manual action.
> Can you please try to reinstall vdsm from its rpms and try it again?
>
>
>>
>> -Original Message-
>> From: Fabian Deutsch [mailto:fdeut...@redhat.com]
>> Sent: Tuesday, December 01, 2015 12:58 AM
>> To: Will Dennis
>> Cc: Simone Tiraboschi; users
>> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does
>> not start
>>
>> On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <wden...@nec-labs.com> wrote:
>> > Any clues out of the strace of vdsm?
>>
>> read(9, "sudo: a password is required\n", 4096) = 29
>>
>> Could it be that sudo is not configured to operate passwordless?
>>
>> The strat-up can then fail, because sudo requires a ty, but this isn't
>> available during service start.
>>
>> - fabian
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-01 Thread Willard Dennis
Did the following:

1) yum remove vdsm*
[…]
Removed:
  vdsm.noarch 0:4.17.10.1-0.el7.centos vdsm-cli.noarch 
0:4.17.10.1-0.el7.centosvdsm-gluster.noarch 0:4.17.10.1-0.el7.centos
  vdsm-infra.noarch 0:4.17.10.1-0.el7.centos   vdsm-jsonrpc.noarch 
0:4.17.10.1-0.el7.centosvdsm-python.noarch 0:4.17.10.1-0.el7.centos
  vdsm-xmlrpc.noarch 0:4.17.10.1-0.el7.centos  vdsm-yajsonrpc.noarch 
0:4.17.10.1-0.el7.centos

Dependency Removed:
  ovirt-hosted-engine-ha.noarch 0:1.3.2.1-1.el7.centos 
ovirt-hosted-engine-setup.noarch 0:1.3.0-1.el7.centos 


2) yum install vdsm vdsm-cli vdsm-gluster vdsm-infra vdsm-jsonrpc vdsm-python 
vdsm-xmlrpc vdsm-yajsonrpc
[…]
Installed:
  vdsm.noarch 0:4.17.11-0.el7.centos   vdsm-cli.noarch 
0:4.17.11-0.el7.centos  vdsm-gluster.noarch 0:4.17.11-0.el7.centos
  vdsm-infra.noarch 0:4.17.11-0.el7.centos vdsm-jsonrpc.noarch 
0:4.17.11-0.el7.centos  vdsm-python.noarch 0:4.17.11-0.el7.centos
  vdsm-xmlrpc.noarch 0:4.17.11-0.el7.centosvdsm-yajsonrpc.noarch 
0:4.17.11-0.el7.centos

3) yum install ovirt-hosted-engine-setup ovirt-hosted-engine-ha
[…]
Installed:
  ovirt-hosted-engine-ha.noarch 0:1.3.3-1.el7.centos  
ovirt-hosted-engine-setup.noarch 0:1.3.1-1.el7.centos

Dependency Updated:
  ovirt-host-deploy.noarch 0:1.4.1-1.el7.centos


Result:
[root@ovirt-node-01 ~]# systemctl start vdsmd
Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and 
'journalctl -xn' for details.
[root@ovirt-node-01 ~]# systemctl status vdsmd.service
vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
   Active: failed (Result: start-limit) since Tue 2015-12-01 23:55:05 EST; 14s 
ago
  Process: 21336 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
--pre-start (code=exited, status=1/FAILURE)
 Main PID: 20589 (code=exited, status=1/FAILURE)

Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop 
Server Manager.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed 
state.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server 
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over, 
scheduling restart.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Stopping Virtual Desktop Server 
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server 
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service start request repeated 
too quickly, refusing to start.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop 
Server Manager.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed 
state.

Different error now, but vdsmd service still won’t restart correctly...


> On Dec 1, 2015, at 9:25 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
> 
> On Tue, Dec 1, 2015 at 3:15 PM, Will Dennis <wden...@nec-labs.com 
> <mailto:wden...@nec-labs.com>> wrote:
> I believe sudo is NOT setup for passwordless (then again, didn't see that in 
> any pre-req instructions...) Who would be the sudoer in this case?
> 
> It's not required to take any manual action.
> Can you please try to reinstall vdsm from its rpms and try it again?
>  
> 
> -Original Message-
> From: Fabian Deutsch [mailto:fdeut...@redhat.com <mailto:fdeut...@redhat.com>]
> Sent: Tuesday, December 01, 2015 12:58 AM
> To: Will Dennis
> Cc: Simone Tiraboschi; users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
> start
> 
> On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <wden...@nec-labs.com 
> <mailto:wden...@nec-labs.com>> wrote:
> > Any clues out of the strace of vdsm?
> 
> read(9, "sudo: a password is required\n", 4096) = 29
> 
> Could it be that sudo is not configured to operate passwordless?
> 
> The strat-up can then fail, because sudo requires a ty, but this isn't 
> available during service start.
> 
> - fabian

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-01 Thread Will Dennis
I believe sudo is NOT setup for passwordless (then again, didn't see that in 
any pre-req instructions...) Who would be the sudoer in this case?

-Original Message-
From: Fabian Deutsch [mailto:fdeut...@redhat.com] 
Sent: Tuesday, December 01, 2015 12:58 AM
To: Will Dennis
Cc: Simone Tiraboschi; users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <wden...@nec-labs.com> wrote:
> Any clues out of the strace of vdsm?

read(9, "sudo: a password is required\n", 4096) = 29

Could it be that sudo is not configured to operate passwordless?

The strat-up can then fail, because sudo requires a ty, but this isn't 
available during service start.

- fabian



> From: Willard Dennis [mailto:wden...@nec-labs.com]
> Sent: Wednesday, November 25, 2015 12:58 PM
> To: Simone Tiraboschi
> Cc: users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd 
> does not start
>
>
>
> strace output:
>
> https://gist.githubusercontent.com/wdennis/d9913d8064af6a6b2c36/raw/6a
> 33f7d9ba7da72ff9be7a15e2e81e5d06ad0fc5/vdsm-strace.txt
>
>
>
>
>
> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
>
>
> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis <wden...@nec-labs.com>
> wrote:
>
> [root@ovirt-node-01 ~]# sudo -u vdsm /bin/bash
>
> bash-4.2$ /usr/share/vdsm/vdsm
>
> bash-4.2$ echo $?
>
> 1
>
>
>
> Can you please use strace on it?
>
>
>
>
>
> On Nov 25, 2015, at 11:16 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
> On Wed, Nov 25, 2015 at 5:09 PM, Willard Dennis <wden...@nec-labs.com>
> wrote:
>
>
>
> On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
>
>
> On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis <wden...@nec-labs.com> wrote:
>
> Hi Simone,
>
> Looks like the vdsm log is empty...
>
> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
>
> Yes, I did execute the ‘vdsm-tool configure –force’ command before the 
> restart, looks like it worked OK, but still the same problem with 
> starting vdsm...
>
>
>
>
>
> Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?
>
>
>
>
>
> [root@ovirt-node-01 ~]# su - vdsm
>
> This account is currently not available.
>
> [root@ovirt-node-01 ~]#
>
> [root@ovirt-node-01 ~]# grep vdsm /etc/passwd
>
> vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
>
> [root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
>
> This account is currently not available.
>
>
>
>
>
> [root@tiramd1 ~]# sudo -u vdsm /bin/bash
>
> bash-4.2$ whoami
>
> vdsm
>
>
>
>
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



--
Fabian Deutsch <fdeut...@redhat.com>
RHEV Hypervisor
Red Hat
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-30 Thread Fabian Deutsch
On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <wden...@nec-labs.com> wrote:
> Any clues out of the strace of vdsm?

read(9, "sudo: a password is required\n", 4096) = 29

Could it be that sudo is not configured to operate passwordless?

The strat-up can then fail, because sudo requires a ty, but this isn't
available during service start.

- fabian



> From: Willard Dennis [mailto:wden...@nec-labs.com]
> Sent: Wednesday, November 25, 2015 12:58 PM
> To: Simone Tiraboschi
> Cc: users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not
> start
>
>
>
> strace output:
>
> https://gist.githubusercontent.com/wdennis/d9913d8064af6a6b2c36/raw/6a33f7d9ba7da72ff9be7a15e2e81e5d06ad0fc5/vdsm-strace.txt
>
>
>
>
>
> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
>
>
> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis <wden...@nec-labs.com>
> wrote:
>
> [root@ovirt-node-01 ~]# sudo -u vdsm /bin/bash
>
> bash-4.2$ /usr/share/vdsm/vdsm
>
> bash-4.2$ echo $?
>
> 1
>
>
>
> Can you please use strace on it?
>
>
>
>
>
> On Nov 25, 2015, at 11:16 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
> On Wed, Nov 25, 2015 at 5:09 PM, Willard Dennis <wden...@nec-labs.com>
> wrote:
>
>
>
> On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
>
>
>
>
> On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis <wden...@nec-labs.com> wrote:
>
> Hi Simone,
>
> Looks like the vdsm log is empty...
>
> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
>
> Yes, I did execute the ‘vdsm-tool configure –force’ command before the
> restart, looks like it worked OK, but still the same problem with starting
> vdsm...
>
>
>
>
>
> Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?
>
>
>
>
>
> [root@ovirt-node-01 ~]# su - vdsm
>
> This account is currently not available.
>
> [root@ovirt-node-01 ~]#
>
> [root@ovirt-node-01 ~]# grep vdsm /etc/passwd
>
> vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
>
> [root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
>
> This account is currently not available.
>
>
>
>
>
> [root@tiramd1 ~]# sudo -u vdsm /bin/bash
>
> bash-4.2$ whoami
>
> vdsm
>
>
>
>
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Fabian Deutsch <fdeut...@redhat.com>
RHEV Hypervisor
Red Hat
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-30 Thread Will Dennis
Any clues out of the strace of vdsm?

From: Willard Dennis [mailto:wden...@nec-labs.com]
Sent: Wednesday, November 25, 2015 12:58 PM
To: Simone Tiraboschi
Cc: users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

strace output:
https://gist.githubusercontent.com/wdennis/d9913d8064af6a6b2c36/raw/6a33f7d9ba7da72ff9be7a15e2e81e5d06ad0fc5/vdsm-strace.txt


On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi 
<stira...@redhat.com<mailto:stira...@redhat.com>> wrote:



On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis 
<wden...@nec-labs.com<mailto:wden...@nec-labs.com>> wrote:
[root@ovirt-node-01 ~]# sudo -u vdsm /bin/bash
bash-4.2$ /usr/share/vdsm/vdsm
bash-4.2$ echo $?
1

Can you please use strace on it?


On Nov 25, 2015, at 11:16 AM, Simone Tiraboschi 
<stira...@redhat.com<mailto:stira...@redhat.com>> wrote:


On Wed, Nov 25, 2015 at 5:09 PM, Willard Dennis 
<wden...@nec-labs.com<mailto:wden...@nec-labs.com>> wrote:

On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi 
<stira...@redhat.com<mailto:stira...@redhat.com>> wrote:



On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis 
<wden...@nec-labs.com<mailto:wden...@nec-labs.com>> wrote:
Hi Simone,

Looks like the vdsm log is empty...

[root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
-rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log

Yes, I did execute the ‘vdsm-tool configure –force’ command before the restart, 
looks like it worked OK, but still the same problem with starting vdsm...


Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?


[root@ovirt-node-01 ~]# su - vdsm
This account is currently not available.
[root@ovirt-node-01 ~]#
[root@ovirt-node-01 ~]# grep vdsm /etc/passwd
vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
[root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
This account is currently not available.


[root@tiramd1 ~]# sudo -u vdsm /bin/bash
bash-4.2$ whoami
vdsm




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Will Dennis
Hi Simone,

Looks like the vdsm log is empty...

[root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
-rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log

Yes, I did execute the ‘vdsm-tool configure –force’ command before the restart, 
looks like it worked OK, but still the same problem with starting vdsm...



From: Simone Tiraboschi [mailto:stira...@redhat.com] 
Sent: Wednesday, November 25, 2015 5:24 AM
To: Will Dennis
Cc: users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

Could you please attach vdsm logs (/var/log/vdsm/vdsm.log)?

did you tried  manually running 
 vdsm-tool configure --force
before restarting vdsm?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Simone Tiraboschi
On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis <wden...@nec-labs.com> wrote:

> Hi Simone,
>
> Looks like the vdsm log is empty...
>
> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
>
> Yes, I did execute the ‘vdsm-tool configure –force’ command before the
> restart, looks like it worked OK, but still the same problem with starting
> vdsm...
>


Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?


>
>
>
> From: Simone Tiraboschi [mailto:stira...@redhat.com]
> Sent: Wednesday, November 25, 2015 5:24 AM
> To: Will Dennis
> Cc: users
> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does
> not start
>
> Could you please attach vdsm logs (/var/log/vdsm/vdsm.log)?
>
> did you tried  manually running
>  vdsm-tool configure --force
> before restarting vdsm?
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Willard Dennis

> On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis  > wrote:
> Hi Simone,
> 
> Looks like the vdsm log is empty...
> 
> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
> 
> Yes, I did execute the ‘vdsm-tool configure –force’ command before the 
> restart, looks like it worked OK, but still the same problem with starting 
> vdsm...
> 
> 
> Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?
> 

[root@ovirt-node-01 ~]# su - vdsm
This account is currently not available.
[root@ovirt-node-01 ~]#
[root@ovirt-node-01 ~]# grep vdsm /etc/passwd
vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
[root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
This account is currently not available.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Simone Tiraboschi
On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis 
wrote:

> [root@ovirt-node-01 ~]# sudo -u vdsm /bin/bash
> bash-4.2$ /usr/share/vdsm/vdsm
> bash-4.2$ echo $?
> 1
>

Can you please use strace on it?


>
> On Nov 25, 2015, at 11:16 AM, Simone Tiraboschi 
> wrote:
>
>
> On Wed, Nov 25, 2015 at 5:09 PM, Willard Dennis 
> wrote:
>
>>
>> On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi 
>> wrote:
>>
>>
>>
>> On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis 
>> wrote:
>>
>>> Hi Simone,
>>>
>>> Looks like the vdsm log is empty...
>>>
>>> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
>>> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
>>>
>>> Yes, I did execute the ‘vdsm-tool configure –force’ command before the
>>> restart, looks like it worked OK, but still the same problem with starting
>>> vdsm...
>>>
>>
>>
>> Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?
>>
>>
>> [root@ovirt-node-01 ~]# su - vdsm
>> This account is currently not available.
>> [root@ovirt-node-01 ~]#
>> [root@ovirt-node-01 ~]# grep vdsm /etc/passwd
>> vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
>> [root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
>> This account is currently not available.
>>
>>
> [root@tiramd1 ~]# sudo -u vdsm /bin/bash
> bash-4.2$ whoami
> vdsm
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Willard Dennis
strace output:
https://gist.githubusercontent.com/wdennis/d9913d8064af6a6b2c36/raw/6a33f7d9ba7da72ff9be7a15e2e81e5d06ad0fc5/vdsm-strace.txt
 



> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis  > wrote:
> [root@ovirt-node-01 ~]# sudo -u vdsm /bin/bash
> bash-4.2$ /usr/share/vdsm/vdsm
> bash-4.2$ echo $?
> 1
> 
> Can you please use strace on it?
>  
> 
>> On Nov 25, 2015, at 11:16 AM, Simone Tiraboschi > > wrote:
>> 
>> 
>> On Wed, Nov 25, 2015 at 5:09 PM, Willard Dennis > > wrote:
>> 
>>> On Nov 25, 2015, at 10:37 AM, Simone Tiraboschi >> > wrote:
>>> 
>>> 
>>> 
>>> On Wed, Nov 25, 2015 at 4:20 PM, Will Dennis >> > wrote:
>>> Hi Simone,
>>> 
>>> Looks like the vdsm log is empty...
>>> 
>>> [root@ovirt-node-01 ~]# ls -l /var/log/vdsm/vdsm.log
>>> -rw-r--r-- 1 vdsm kvm 0 Nov 23 15:41 /var/log/vdsm/vdsm.log
>>> 
>>> Yes, I did execute the ‘vdsm-tool configure –force’ command before the 
>>> restart, looks like it worked OK, but still the same problem with starting 
>>> vdsm...
>>> 
>>> 
>>> Can you please try manually run /usr/share/vdsm/vdsm as vdsm user?
>>> 
>> 
>> [root@ovirt-node-01 ~]# su - vdsm
>> This account is currently not available.
>> [root@ovirt-node-01 ~]#
>> [root@ovirt-node-01 ~]# grep vdsm /etc/passwd
>> vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin
>> [root@ovirt-node-01 ~]# runuser -l vdsm -c '/usr/share/vdsm/vdsm'
>> This account is currently not available.
>> 
>> 
>> [root@tiramd1 ~]# sudo -u vdsm /bin/bash
>> bash-4.2$ whoami
>> vdsm
>> 
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Will Dennis
[root@ovirt-node-01 ~]# yum list installed | grep engine
ovirt-engine-sdk-python.noarch 3.6.0.3-1.el7.centos   @ovirt-3.6
ovirt-hosted-engine-ha.noarch  1.3.2.1-1.el7.centos   @ovirt-3.6
ovirt-hosted-engine-setup.noarch   1.3.0-1.el7.centos @ovirt-3.6
[root@ovirt-node-01 ~]#
[root@ovirt-node-01 ~]# yum list installed | grep vdsm
vdsm.noarch4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-cli.noarch4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-gluster.noarch4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-infra.noarch  4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-jsonrpc.noarch4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-python.noarch 4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-xmlrpc.noarch 4.17.10.1-0.el7.centos @ovirt-3.6
vdsm-yajsonrpc.noarch  4.17.10.1-0.el7.centos @ovirt-3.6


From: Roman Mohr [mailto:rm...@redhat.com]
Sent: Wednesday, November 25, 2015 5:23 AM
To: Will Dennis
Cc: users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

Hi Willard,

Which packages versions are you using?

Could you provide the output of the following commands:
# yum list installed | grep engine
# yum list installed | grep vdsm

Best Regards,
Roman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Roman Mohr
Hi Willard,

On Tue, Nov 24, 2015 at 7:41 PM, Willard Dennis 
wrote:

> Hi all,
>
> Tried to run the hosted engine setup, got:
> [ ERROR ] Failed to execute stage 'Environment setup': [Errno 111]
> Connection refused
>
> Which packages versions are you using?

Could you provide the output of the following commands:
# yum list installed | grep engine
# yum list installed | grep vdsm


> ( full run output here:
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/hosted-engine-setup-output.txt
>  )
>
> Looked at the setup log file referenced in the output, saw this traceback
> in it that also referenced the Error 111:
>
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/configurevm-py_error.txt
>
> I diagnosed it (Google ftw) and saw that it was likely a vdsmd problem;
> sure enough, when I did a 'systemctl status vdsmd’ I saw that it was in
> error state -
> Process: 28163 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1
> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>
> ( full status output here:
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/systemctl_status_vdsmd.txt
>  )
>
>
Could you add the vdsm log file in /var/log/vdsm/vdsm.log?



> Does anyone know how I can troubleshoot and fix the VDSM daemon start
> process?
>
>
You could try to run

# vdsm-tool configure --force

and then

# systemctl restart vdsmd



> Thanks,
> Will
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
Best Regards,
Roman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-11-25 Thread Simone Tiraboschi
On Tue, Nov 24, 2015 at 7:41 PM, Willard Dennis 
wrote:

> Hi all,
>
> Tried to run the hosted engine setup, got:
> [ ERROR ] Failed to execute stage 'Environment setup': [Errno 111]
> Connection refused
>
> ( full run output here:
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/hosted-engine-setup-output.txt
>  )
>
> Looked at the setup log file referenced in the output, saw this traceback
> in it that also referenced the Error 111:
>
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/configurevm-py_error.txt
>
> I diagnosed it (Google ftw) and saw that it was likely a vdsmd problem;
> sure enough, when I did a 'systemctl status vdsmd’ I saw that it was in
> error state -
> Process: 28163 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1
> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>
> ( full status output here:
> https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/systemctl_status_vdsmd.txt
>  )
>
> Does anyone know how I can troubleshoot and fix the VDSM daemon start
> process?
>

Could you please attach vdsm logs (/var/log/vdsm/vdsm.log)?

did you tried  manually running
 vdsm-tool configure --force
before restarting vdsm?



>
> Thanks,
> Will
>
>
> ___
> 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


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

2015-11-24 Thread Willard Dennis
Hi all,

Tried to run the hosted engine setup, got:
[ ERROR ] Failed to execute stage 'Environment setup': [Errno 111] Connection 
refused

( full run output here: 
https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/hosted-engine-setup-output.txt
 

 )

Looked at the setup log file referenced in the output, saw this traceback in it 
that also referenced the Error 111:
https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/configurevm-py_error.txt
 


I diagnosed it (Google ftw) and saw that it was likely a vdsmd problem; sure 
enough, when I did a 'systemctl status vdsmd’ I saw that it was in error state -
Process: 28163 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 
/dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)

( full status output here: 
https://gist.githubusercontent.com/wdennis/4390042447354b2cb1c4/raw/c0f9127c676759b19b1d32a212c8c3694fac580e/systemctl_status_vdsmd.txt
 

 )

Does anyone know how I can troubleshoot and fix the VDSM daemon start process?

Thanks,
Will

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users