VDSM doesn't start in new ovirt host
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@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, -- André Freitas System & Network Administrator | (+351) 234 484 466 ISO 9001 CMMI Level 2 Ubiwhere Copyright © Ubiwhere. 2014. All rights reserved. Content for exclusive use of their rightful recipients. Dissemination, copy or use of information by third parties is prohibited. If you are not an authorised recipient and received this message, please notify the sender and then delete it without copying the text and attachments nor distributing or disclosing its contents.
-----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@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-----
I have removed vdsm and libvirt from that host before the reinstalation of the host in ovirt engine but the problem persists with "s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave". i have put the new log referring to this instalation in http://ur1.ca/hrc7d Best regards, -- André Freitas André Freitas System & Network Administrator | (+351) 234 484 466 ISO 9001 CMMI Level 2 Ubiwhere Copyright © Ubiwhere. 2014. All rights reserved. Content for exclusive use of their rightful recipients. Dissemination, copy or use of information by third parties is prohibited. If you are not an authorised recipient and received this message, please notify the sender and then delete it without copying the text and attachments nor distributing or disclosing its contents. -----Original Message----- From: Sven Kieske <svenkieske@gmail.com> To: users@ovirt.org Subject: Re: [ovirt-users] VDSM doesn't start in new ovirt host Date: Mon, 14 Jul 2014 21:24:02 +0200 -----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@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----- _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 15.07.2014 11:17, schrieb André Freitas:
I have removed vdsm and libvirt from that host before the reinstalation of the host in ovirt engine but the problem persists with "s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave".
i have put the new log referring to this instalation in http://ur1.ca/hrc7d
Best regards,
Hi, can you try to downgrade the package python-pthreading using yum? don't install 0.1.3-2 as it breaks your host, updated 0.1.3-3 is not yet available in epel. 0.1.2 should be safe. HTH - -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTxPaTAAoJEC5d3lL7/I9zlNwQALcWjMEGjRQ+6e4j6xxrDEPs unU4ZTn3YKXpzysPBURSq2ULw5c5kRWRurOVaLaKM/IZHjYNN924tlJeIP36IUFs FMWokT78HDDfgPJi9BK/T6YIkdN7g9BKFDPGqDiypt6nCEjlNSfKOF6vzu93LJ+b 5bpxFuuE5lqdUD5J43foHsZ8zllpJjP2RUa3lcmgkXz8R7LZkwvEAscEsAZ+i9YL qAYQoSGiIfbC/Kg5i6uGs4TJVoRejmGQUd9UtgJSwEMM7KSsFzenYbvTY74GlKhY CwXqG3BmZuwOJ0EBtoLXBmesV/wiTdyYO73PDXxl9kZI4ZRMnx6anQ61QTKw3J1b NZN8GoEPv3MCW0Q6APVJy76w7NvWwP758b65ioi6CFid6aVN4aaQUuTAUvTh428A SzIym+oY+MEs3yCBbMnJu7euEU9hWWUZeRUTGALH3aQeKVegcEtDn2zdyKP3FSqp CMYyVVG4E4BMi7pp1kqkbtD9BcEIPdVmIGNTSGKJkfrxUW54PGD90d/not8Xtx7p SDjLcMb6PdmckGK2DqFEYqzZWgYTpcMNsLvqvJmR9/IyzfYDG6/O+yGjYutH9MG6 fWmgGtbNOtX/yVcO4DQOOQaHQWbEt/sSNcF96gKx81KfvWw8lMO27qhn8+daQj/L M7uLrkKBHOxmwWQO5u4t =bXS/ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-15 11:36, Sven Kieske wrote:
Am 15.07.2014 11:17, schrieb André Freitas:
I have removed vdsm and libvirt from that host before the reinstalation of the host in ovirt engine but the problem persists with "s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave".
i have put the new log referring to this instalation in http://ur1.ca/hrc7d
Best regards,
Hi,
can you try to downgrade the package python-pthreading using yum? don't install 0.1.3-2 as it breaks your host, updated 0.1.3-3 is not yet available in epel. 0.1.2 should be safe.
HTH
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
As I got stucked with the same error since yesterday I will confirm this solution did the trick. Now I got the new host up and running. Thanks Ricky Schneberger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPE+psACgkQOap81biMC2NkUQCeLLC61MxWjxOvxNKfFITu6Q9v BNgAnRSKCGMvX7fbEQsCGQkSehIlPy65 =wQxT -----END PGP SIGNATURE-----
hi, i have installed the new version indicated in http://lists.ovirt.org/pipermail/users/2014-July/025979.html an now my host concludes the installation with sucess. -- André Freitas André Freitas System & Network Administrator | (+351) 234 484 466 ISO 9001 CMMI Level 2 Ubiwhere Copyright © Ubiwhere. 2014. All rights reserved. Content for exclusive use of their rightful recipients. Dissemination, copy or use of information by third parties is prohibited. If you are not an authorised recipient and received this message, please notify the sender and then delete it without copying the text and attachments nor distributing or disclosing its contents. -----Original Message----- From: Sven Kieske <S.Kieske@mittwald.de> To: users@ovirt.org <users@ovirt.org> Subject: Re: [ovirt-users] VDSM doesn't start in new ovirt host Date: Tue, 15 Jul 2014 09:36:09 +0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 15.07.2014 11:17, schrieb André Freitas:
I have removed vdsm and libvirt from that host before the reinstalation of the host in ovirt engine but the problem persists with "s1 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave".
i have put the new log referring to this instalation in http://ur1.ca/hrc7d
Best regards,
Hi, can you try to downgrade the package python-pthreading using yum? don't install 0.1.3-2 as it breaks your host, updated 0.1.3-3 is not yet available in epel. 0.1.2 should be safe. HTH - -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTxPaTAAoJEC5d3lL7/I9zlNwQALcWjMEGjRQ+6e4j6xxrDEPs unU4ZTn3YKXpzysPBURSq2ULw5c5kRWRurOVaLaKM/IZHjYNN924tlJeIP36IUFs FMWokT78HDDfgPJi9BK/T6YIkdN7g9BKFDPGqDiypt6nCEjlNSfKOF6vzu93LJ+b 5bpxFuuE5lqdUD5J43foHsZ8zllpJjP2RUa3lcmgkXz8R7LZkwvEAscEsAZ+i9YL qAYQoSGiIfbC/Kg5i6uGs4TJVoRejmGQUd9UtgJSwEMM7KSsFzenYbvTY74GlKhY CwXqG3BmZuwOJ0EBtoLXBmesV/wiTdyYO73PDXxl9kZI4ZRMnx6anQ61QTKw3J1b NZN8GoEPv3MCW0Q6APVJy76w7NvWwP758b65ioi6CFid6aVN4aaQUuTAUvTh428A SzIym+oY+MEs3yCBbMnJu7euEU9hWWUZeRUTGALH3aQeKVegcEtDn2zdyKP3FSqp CMYyVVG4E4BMi7pp1kqkbtD9BcEIPdVmIGNTSGKJkfrxUW54PGD90d/not8Xtx7p SDjLcMb6PdmckGK2DqFEYqzZWgYTpcMNsLvqvJmR9/IyzfYDG6/O+yGjYutH9MG6 fWmgGtbNOtX/yVcO4DQOOQaHQWbEt/sSNcF96gKx81KfvWw8lMO27qhn8+daQj/L M7uLrkKBHOxmwWQO5u4t =bXS/ -----END PGP SIGNATURE----- _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 07/14/2014 02:17 PM, 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@s1 <mailto:root@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?
Oi André, What's the version of your python-pthreading? Depending of version of python-pthreading you might be facing: http://lists.ovirt.org/pipermail/users/2014-July/025979.html -- Cheers Douglas
participants (5)
-
André Freitas -
Douglas Schilling Landgraf -
Ricky Schneberger -
Sven Kieske -
Sven Kieske