[ovirt-users] VDSM doesn't start in new ovirt host

[Sven Kieske]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14.07.2014 20:17, André Freitas wrote:
> Hi to all.
> 
> Today i was trying to add a third host to my existing ovirt 3.4
> cluster but i can't because it stays in non-responsive status.
> 
> The steps that i did were: 1ª minimal instalation of CentOS 6.5
> with SeLinux disabled 2º yum localinstall 
> http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm
> -y 3º add the new host by ovirt engine webpage
> 
> In /var/log/messages of the third host (the one that i'm trying to
> add) i receive a lot of this messages
> 
> Jul 14 19:03:37 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:37 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:38 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave Jul 14
> 19:03:39 s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile
> /var/run/vdsm/vdsmd.pid' died too quickly for more than 30 seconds,
> master sleeping for 900 seconds
> 
> All the research that i did all go to this 
> https://bugzilla.redhat.com/show_bug.cgi?id=1055153 but i have all
> the correct permissions on my logs
> 
> [root at s1 ~]# ls -l /var/log/vdsm/ total 16 drwxr-xr-x. 2 vdsm kvm
> 4096 Jun  9 22:25 backup -rw-r--r--. 1 vdsm kvm      0 Jul 14 15:27
> metadata.log -rw-r--r--. 1 vdsm kvm      0 Jul 14 15:27 mom.log 
> -rw-r--r--. 1 root root 11039 Jul 14 18:32 supervdsm.log 
> -rw-r--r--. 1 vdsm kvm      0 Jul 14 15:27 vdsm.log
> 
> i have put the log referring the instalation of this host in 
> http://ur1.ca/hr3x7 (/var/log/ovirt-engine/host-deploy) Can anyone
> help me?
> 
> Best regards,

As far as I can tell, the error boils down to the following
lines from your host-deploy log:


Starting up vdsm daemon:
[  OK  ]
vdsm start[  OK  ]

2014-07-14 18:32:06 DEBUG otopi.plugins.otopi.services.rhel
plugin.execute:866 execute-output: ('/sbin/service', 'vdsmd', 'start')
stderr:
initctl: Job is already running: libvirtd

so you might want to try to re-deploy (click reinstall in webadmin)
but make sure vdsm and libvirtd are of prior to the deployment.
Are you sure they weren't started(maybe by someone else)?

HTH

kind regards

Sven

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQGcBAEBAgAGBQJTxC5SAAoJEAq0kGAWDrqleiML/34+U87ZKjbYDs4FtZFbncdW
qj83hoaei9G2W3QuASwmwIehMFuMoMdyCePk2kNzNoGwSrgWzmwxDeI0SkXBwoDS
X4J9NpZhm5dJggf4oMAk1osc2B6HEwGUH4J6WukBYhinnkVTW+hGRqJiTadgVZtw
MfAB4T+UbQ0mE8noD363bI8goNaFB5/XfUy5Yd+I9cNZYApCGE1CfyNEvFRF+nji
ria1B2vyiW398HL1/i7fGb49pIakg1zAp3lUA7KXpwIYXrlwFfxUHdSTH5uPY6nO
QM906MtAhVSHcnkn6OSMUhtzxtKXiXo1DXkRo0IYmurWZvIMVhri85MEV56UQiRi
oNPpFzHW5EZExI+FnQmfJJwNWnQ3/UKlmtoI+ljsgGDbnrOeBn4sekVSfhMipBLj
OzNTUU2ytEDAwEcC9FMwUdJqsTK87rJCorNrXvZRCVkjDFKWqKp7U1hKpn+IJi6u
ALGaVn6zKcNlisc/UrMHwb5sSg3sT/cJiePUDerORg==
=Vapy
-----END PGP SIGNATURE-----