[ovirt-users] Hosted Engine setup - got " Failed to start service 'ovirt-ha-agent' "

2015-12-18 Thread Willard Dennis
Hi all,

Did a hosted engine setup using a Gluster storage domain, it went well until 
the end, where I got this error:

[ INFO  ] Saving hosted-engine configuration on the shared storage domain
[ INFO  ] Shutting down the engine VM
[ INFO  ] Enabling and starting HA services
[ ERROR ] Failed to execute stage 'Closing up': Failed to start service 
'ovirt-ha-agent’ 
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file 
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20151218124259.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination

Full screen output from setup run:
http://pastebin.com/yWkppmjG 

What’s my move now? Hopefully the install can be salvaged….

FYI, I have three hosts I’m using for oVirt; they are named 
“ovirt-node-[01,02,03]”

Thanks,
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
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 <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?
> 
> - fabian
> 
> 
> -- 
> 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-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 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


[ovirt-users] Hosted engine setup using Gluster - what is proper param's for the storage domain names?

2015-12-17 Thread Willard Dennis
Hi all,

Doing the hosted engine setup on Gluster; am at the point of configuring the 
storage domain / datacenter names, and not sure of what my best move is here… 
Here’s what I’m seeing:

——
  --== STORAGE CONFIGURATION ==--

  During customization use CTRL-D to abort.
  Please specify the storage you would like to use (glusterfs, iscsi, 
fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the shared storage.
  Please specify the full shared storage connection path to use 
(example: host:/path): localhost:/engine
[WARNING] Due to several bugs in mount.glusterfs the validation of GlusterFS 
share cannot be reliable.
[ INFO  ] GlusterFS replica 3 Volume detected
[ INFO  ] Installing on first host
  Please provide storage domain name. [hosted_storage]:
  Local storage datacenter name is an internal name
  and currently will not be shown in engine's admin UI.
  Please enter local datacenter name [hosted_datacenter]:
——

Concerned about the "Local storage datacenter name is an internal name and 
currently will not be shown in engine's admin UI” message… I want to use a 
second distributed Gluster volume (name = “vmdata”) for VM storage if I can, 
and don’t want to mess up the install… What should I consider when setting 
names for the storage domain name and local datacenter names?

Thanks,
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 <d...@redhat.com> wrote:
> 
> On Wed, Dec 16, 2015 at 11: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…
> 
> (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 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  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

___
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  wrote:
> 
> On Tue, Dec 1, 2015 at 3:15 PM, Will Dennis  > 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  > 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-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 Willard Dennis
strace output:
https://gist.githubusercontent.com/wdennis/d9913d8064af6a6b2c36/raw/6a33f7d9ba7da72ff9be7a15e2e81e5d06ad0fc5/vdsm-strace.txt
 
<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 
> <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


[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


[ovirt-users] Planning out oVirt Self-Hosted Engine on Gluster (oVirt 3.6.x / Gluster 3.7.5)

2015-10-22 Thread Willard Dennis
Hi all,

Back to trying out the latest oVirt with latest Gluster, and wanting to do a 
self-hosted Engine setup. I am reading the instructions I found on the 
following pages:

http://www.ovirt.org/Features/Self_Hosted_Engine_Gluster_Support 


http://www.ovirt.org/QA:TestCase_Hosted_Engine_External_Gluster_Support 


I have the requisite Gluster volume all ready to go:

[root@ovirt-node-01 ~]# gluster volume info engine

Volume Name: engine
Type: Distributed-Replicate
Volume ID: 974c9da4-b236-4fc1-b26a-645f14601db8
Status: Started
Number of Bricks: 2 x 3 = 6
Transport-type: tcp
Bricks:
Brick1: ovirt-node-01:/gluster_brick1/engine_brick
Brick2: ovirt-node-02:/gluster_brick2/engine_brick
Brick3: ovirt-node-03:/gluster_brick3/engine_brick
Brick4: ovirt-node-01:/gluster_brick3/engine_brick
Brick5: ovirt-node-02:/gluster_brick4/engine_brick
Brick6: ovirt-node-03:/gluster_brick5/engine_brick
Options Reconfigured:
server.allow-insecure: on
storage.owner-gid: 36
storage.owner-uid: 36
auth.allow: *
network.ping-timeout: 10
cluster.server-quorum-type: server
cluster.quorum-type: auto
network.remote-dio: enable
cluster.eager-lock: enable
performance.stat-prefetch: off
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off

The one question I have is, should it be mounted or not? I currently do have it 
mounted on each host (example off one of my oVirt hosts):

localhost:/engine  1.9T   65M  1.9T   1% /data/ovirt/engine

Will this interfere with the running of "hosted-engine —deploy”? Kindly advise.

Thanks,
Will___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Problem with 3.5.1 hosted engine setup

2015-04-22 Thread Willard Dennis
Hi all,

I’m trying to get a hosted engine set up on a CentOS 7.1 box, per the 
instructions found at 
http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ 
http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/

When I run the ‘hosted-engine —deploy’ step, I’m getting the following output…
https://gist.github.com/wdennis/f9783b04d77676881d5b 
https://gist.github.com/wdennis/f9783b04d77676881d5b

Looking at the log file, I see the following traceback:
https://gist.github.com/wdennis/4e4de8413cf2dd1a3c6b 
https://gist.github.com/wdennis/4e4de8413cf2dd1a3c6b

Can anyone tell me what exactly is failing, and how I might fix it?

Thanks,
Will___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Error when trying to create a new ISO storage domain

2014-01-21 Thread Willard Dennis
I am still trying to resolve this issue. I found the Troubleshooting NFS 
Storage Issues page, and have a few questions regarding the troubleshooting 
steps contained therein...
1) In the Permissions section, there's a suggestion under the SELinux 
subsection to su - vdsm -s /bin/bash and then try to mount the target NFS 
share under a temp mountpoint. However, the mount command is only usable as 
'root', right? If this can indeed be done, please let me know how (and I will 
update the wiki page...)
2) In the nfs-check program section, it says to run the Python script passing 
the the target NFS share path as a parameter. However, it does not indicate 
where to run the script -- on the engine, or on a node? (When I ran it on a 
node, it gives the output: return = 32 error mount.nfs: access denied by server 
while mounting stordevfs.nec-labs.com:/volumes/storage/ovirt-isos)

Thanks!Will

From: willardden...@live.com
To: stockhau...@collogia.de; users@ovirt.org
Date: Mon, 20 Jan 2014 16:17:28 -0500
Subject: Re: [Users] Error when trying to create a new ISO storage domain




Thanks for the reply, Markus.

 Did you follow the NFS export guidelines and userid 36? Here the
 export data from our ISO NFS server path
 
 # ls -ald /var/nas3/OVirtISO
 drwxrwxr-x 3 36 36 74 Dez 10 12:53 /var/nas3/OVirtISO
 # cat /etc/exports
 /var/nas3/OVirtEXP 
 10.0.0.0/12(rw,async,no_subtree_check,anonuid=36,anongid=36,all_squash)
 ...
 
 Markus

The share is on a Illumos (nee OpenSolaris) box, and uses ZFS's NFS 
implementation. Here is the output of the share command (i.e. exportfs) for 
this share:
-@storage/ovir  /volumes/storage/ovirt-isos   anon=36,sec=none,rw   
I did change the NFS mount options (added the anon=36, and changed the sec= 
option from sys to none), and now I'm getting a slightly different error:
-Error while executing action Add Storage Connection: Problem while trying 
to mount target-
Any way to get more info on what exactly the propblem is??  
  

___
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


Re: [Users] Error when trying to create a new ISO storage domain

2014-01-21 Thread Willard Dennis

Thanks for the response, Dafna...

 vdsm is using mount command.
 please look at vdsm log and find the mount command that is failing and 
 run it manually to see the mount trace.
 
 you can also attach the vdsm log here and we can try to find it :)
 
 Dafna

Just needed a clue where to look, thanks :)
I see that the mount cmd is being invoked with sudo, and that's how it works 
for the user vdsm --/usr/bin/sudo -n /bin/mount -t nfs -o 
soft,nosharecache,timeo=600,retrans=6,nfsvers=3 
stordevfs.nec-labs.com:/volumes/storage/ovirt-isos 
/rhev/data-center/mnt/stordevfs.nec-labs.com:_volumes_storage_ovirt-isos
And then the resulting error I'm getting:MountError: (32, ';mount.nfs: access 
denied by server while mounting 
stordevfs.nec-labs.com:/volumes/storage/ovirt-isos\n')
...which correlates with the output of the nfs-check.py script.
So, I will have to debug on the Illumos side as to why I don't seem to have the 
needed perm's; but, in the meantime, I did set up a NFS share on a CentOS 6.4 
box I have available, following directions on  
http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues , and it does work fine 
from there. 
Thanks for your assistance!
Best,Will ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] Error when trying to create a new ISO storage domain

2014-01-20 Thread Willard Dennis
Hi all,
I am trying to define a new ISO storage domain. I go to System  Storage, click 
on the New Domain link, and fill in the requisite fields. Domain Function / 
Storage Type drop is set to ISO / NFS, and I verified that I have the proper 
NFS path to the export on the NFS server I want to use. However, when I click 
the OK button, I am getting the following popup:

-Error while executing action Add Storage Connection: Permission settings 
on the specified path do not allow access to the storage.Verify permission 
settings on the specified storage path.-
I have verified that I can manually mount the NFS filesystem on the host 
defined in the Use Host drop [as root], and I have looked in 
/var/log/messages (on the mounting host, as well as the NFS server, and do not 
see any errors... Please not that the NFS export is a pre-existing share on the 
NFS server, and does contain pre-existing data (ISOs, etc.)
How can I debug this? ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Error when trying to create a new ISO storage domain

2014-01-20 Thread Willard Dennis
Thanks for the reply, Markus.

 Did you follow the NFS export guidelines and userid 36? Here the
 export data from our ISO NFS server path
 
 # ls -ald /var/nas3/OVirtISO
 drwxrwxr-x 3 36 36 74 Dez 10 12:53 /var/nas3/OVirtISO
 # cat /etc/exports
 /var/nas3/OVirtEXP 
 10.0.0.0/12(rw,async,no_subtree_check,anonuid=36,anongid=36,all_squash)
 ...
 
 Markus

The share is on a Illumos (nee OpenSolaris) box, and uses ZFS's NFS 
implementation. Here is the output of the share command (i.e. exportfs) for 
this share:
-@storage/ovir  /volumes/storage/ovirt-isos   anon=36,sec=none,rw   
I did change the NFS mount options (added the anon=36, and changed the sec= 
option from sys to none), and now I'm getting a slightly different error:
-Error while executing action Add Storage Connection: Problem while trying 
to mount target-
Any way to get more info on what exactly the propblem is??  
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] New user to oVirt, and I haz a sad so far...

2014-01-17 Thread Willard Dennis
Aha!
Host hostname does not comply with the cluster Default networks, the 
following networks are missing on host: 'ovirtmgmt' 
 
What must I do to correct this? I do not remember reading about having to do 
something like this in the docs... Also, the node is on a different network 
that the engine, not sure if this matters or not (the two network do have 
connectivity to each other thru a router.)
 
Thanks,
Will
 
 Date: Fri, 17 Jan 2014 12:10:50 -0500
 From: eco...@redhat.com
 To: willardden...@live.com
 CC: n...@nieuwland.nl; users@ovirt.org
 Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
 
  - Original Message -
  From: Will Dennis (Live.com) willardden...@live.com
  Sent: Friday, January 17, 2014 11:55:55 AM
  
  
  
  Thanks, Joop, for the node platform best practices… I did turn selinux from
  “enforcing” to “permissive”, and then when I tried to ping the engine by
  fqdn, I saw that DNS lookups were failing (even tho resolv.conf looked
  correct…) Did a ‘yum remove NetworkManager” and then fixed the
  /etc/sysconfig/network-scripts/ifcfg-nic, and then after a reboot, I can
  now see the info for the node in the WUI on the manager, although the status
  for the node is still “Non Operational”…
 
 In the GUI, within the Events sub-tab of that node, there should be an 
 error 
 message detailing the reason for that node being in the Non-Operational 
 state; 
 what does this message say?
 
  
  
  
  Where can I find the node install log (on the engine or the node, and name?)
  (Sorry for noob status, but I am a quick learner ;)
  
  
  
  Thanks,
  
  Will
  
  
  
  
  From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of
  noc
  Sent: Friday, January 17, 2014 3:35 AM
  To: users@ovirt.org
  Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
  
  
  
  
  
  On 17-1-2014 8:53, Gabi C wrote:
  
  
  
  
  
  've been there! :-D
  
  
  I mean exactly same issuse you had on Centos, I had on Fedora 19.
  
  
  Did you disable selinux on nodes? 'cause that's what is causing SSh
  connection closing
  
  
  My setup:
  
  
  1 engine on vmware - fedora 19, up-to-date
  
  
  
  
  
  
  
  
  2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 - 
  1.1.fc19
  with nodes beig in glusterfs cluster also.
  
  
  
  Right now, I'm banging my head against Operation Add-Disk failed to
  complete. , message I have got after adding a new virtual machine and try
  to addd its disk
  
  
  
  
  
  On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) 
  willardden...@live.com  wrote:
  
  Hi all, ready for a story? (well, more of a rant, but hopefully it will be a
  good UX tale, and may even be entertaining.)
  
  Had one of the groups come to me at work this week and request a OpenStack
  setup. When I sat down and discussed their needs, it turns out that they
  really only need a multi-hypervisor setup where they can spin up VMs for
  their research projects. The VMs should be fairly long-lived, and will have
  persistent storage. Their other request is that the storage should be local
  on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB drives
  for VM storage on each node.) They desire this in order to keep the VM I/O
  local - they do not have a SAN of any sort anyhow, and they do not care
  about live migration, etc
  
  
  @Will
  If the installation ends, either with or without error, it will give you a
  log location. Upload the log to a paste.bin and mail the link.
  
  @Gabi,
  There should be more info in either the vdsm.log on the SPM server or in the
  engine.log on the engine server, see above for lettings us know what the
  error is.
  
  Having installed oVirt, probably dozens of times, I have some guidelines:
  - temporarily disable firewalld/iptables (if all works, enable should still
  work, scripts with rules are generated and location is given)
  - make selinux permissive either via setenforce 0 (until next boot) or via
  /etc/selinux/config ( survives reboots), dont disable it!
  - make sure fqdn work in both directions between engine and host(s) (either
  using /etc/hosts or DNS)
  - make sure NetworkManager is disabled and network enabled
  
  Joop
  
  ___
  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


Re: [Users] New user to oVirt, and I haz a sad so far...

2014-01-17 Thread Willard Dennis
 
 Date: Fri, 17 Jan 2014 15:12:20 +0100
 From: dne...@redhat.com
 To: willardden...@live.com; users@ovirt.org
 Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
 
 Hi Will,
 
 Great to see you on the users list! (well, not great to see the content,
 but you know what I mean...) Thanks for your help to date!
 
 On 01/17/2014 05:08 AM, Will Dennis (Live.com) wrote:
  Thanks for reading, and any clues on getting a node up and running
  gratefully accepted...
 
 I have had success setting up CentOS 6.5 minimal in nodes, configuring
 network, and then adding the node through the management interface - the
 Engine takes care of installing  configuring the nodes.
 
 Have you tried this? No, I was told by someone else (in IRC I believe) that 
 only Fedora could be used as a node... I would much rather use EL6.5 
 (CentOS)... What/where is the proper RPM for this platform?
 Cheers,
 Dave.
Thanks again,Will
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] New user to oVirt, and I haz a sad so far...

2014-01-17 Thread Willard Dennis
Uuup!  :)
 
Thanks for your assistance, Einav!
 
Now onwards
 
 Date: Fri, 17 Jan 2014 12:18:30 -0500
 From: eco...@redhat.com
 To: willardden...@live.com
 CC: n...@nieuwland.nl; users@ovirt.org
 Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
 
 go to the Network Interface sub-tab of that node and click the Setup 
 Host Networks button. 
 In the dialog that has opened, attach the 'ovirtmgmt' network from the 
 right-hand side of the dialog to one of your node's NICs on the left-hand 
 side by dragging that network onto the NIC.
 click OK.
 after a short while, your Host should become 'Up'.
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users