
This is a multi-part message in MIME format. --------------030102000703080903010508 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Dan Kenigsberg wrote: I have the same problem, see for answers below.
On Fri, Sep 21, 2012 at 11:36:01AM -0400, Douglas Landgraf wrote:
Hi Nathanaël,
On 09/21/2012 10:18 AM, Nathanaël Blanchet wrote:
Hi all,
In the latest vdsm build from git (vdsm-4.10.0-0.452.git87594e3.fc17.x86_64), vdsmd.service never starts alone after rebooting.
Does it start well when you restart it later, manually? Do you see "failed to connect to libvirt" slightly up the log?
manually restarting it works OK, service vdsmd restart
I have had a look to journalctl anfd I've found this :
systemd-vdsmd[538]: vdsm: Failed to define network filters on libvirt[FAILED]
[root@node ~]# service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: failed (Result: exit-code) since Fri, 21 Sep 2012 12:13:01 +0200; 4min 56s ago Process: 543 ExecStart=/lib/systemd/systemd-vdsmd start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/vdsmd.service
Sep 21 12:12:55 node.abes.fr systemd-vdsmd[543]: Note: Forwarding request to 'systemctl disable libvirt-guests.service'. Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: vdsm: libvirt already configured for vdsm [ OK ] Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting wdmd... Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting sanlock... Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting iscsid: Sep 21 12:13:01 node.abes.fr systemd-vdsmd[543]: Starting libvirtd (via systemctl): [ OK ]
May this nwfilter be the cause of the failure? If yes, do I need to open a BZ?
Thanks for your report. If you can, please open a BZ.
... but please first check whether running
python /usr/share/vdsm/nwfilter.pyc
reports anything fishy.
I don't have that file in /usr/share/vdsm rpm -aq | grep vdsm reports: vdsm-4.10.0-7.fc17.x86_64 vdsm-gluster-4.10.0-7.fc17.noarch vdsm-python-4.10.0-7.fc17.x86_64 vdsm-cli-4.10.0-7.fc17.noarch vdsm-xmlrpc-4.10.0-7.fc17.noarch vdsm-rest-4.10.0-7.fc17.noarch Joop --------------030102000703080903010508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Dan Kenigsberg wrote:<br> <br> I have the same problem, see for answers below.<br> <br> <blockquote cite="mid:20120923113534.GE31818@redhat.com" type="cite"> <pre wrap="">On Fri, Sep 21, 2012 at 11:36:01AM -0400, Douglas Landgraf wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi Nathanaël, On 09/21/2012 10:18 AM, Nathanaël Blanchet wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi all, In the latest vdsm build from git (vdsm-4.10.0-0.452.git87594e3.fc17.x86_64), vdsmd.service never starts alone after rebooting. </pre> </blockquote> </blockquote> <pre wrap=""><!----> Does it start well when you restart it later, manually? Do you see "failed to connect to libvirt" slightly up the log? </pre> </blockquote> manually restarting it works OK, service vdsmd restart<br> <br> <blockquote cite="mid:20120923113534.GE31818@redhat.com" type="cite"> <pre wrap=""></pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">I have had a look to journalctl anfd I've found this : systemd-vdsmd[538]: vdsm: Failed to define network filters on libvirt[FAILED] [root@node ~]# service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: failed (Result: exit-code) since Fri, 21 Sep 2012 12:13:01 +0200; 4min 56s ago Process: 543 ExecStart=/lib/systemd/systemd-vdsmd start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/vdsmd.service Sep 21 12:12:55 node.abes.fr systemd-vdsmd[543]: Note: Forwarding request to 'systemctl disable libvirt-guests.service'. Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: vdsm: libvirt already configured for vdsm [ OK ] Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting wdmd... Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting sanlock... Sep 21 12:12:56 node.abes.fr systemd-vdsmd[543]: Starting iscsid: Sep 21 12:13:01 node.abes.fr systemd-vdsmd[543]: Starting libvirtd (via systemctl): [ OK ] May this nwfilter be the cause of the failure? If yes, do I need to open a BZ? </pre> </blockquote> <pre wrap="">Thanks for your report. If you can, please open a BZ. </pre> </blockquote> <pre wrap=""><!----> ... but please first check whether running python /usr/share/vdsm/nwfilter.pyc reports anything fishy. </pre> </blockquote> I don't have that file in /usr/share/vdsm<br> <br> rpm -aq | grep vdsm reports:<br> vdsm-4.10.0-7.fc17.x86_64<br> vdsm-gluster-4.10.0-7.fc17.noarch <br> vdsm-python-4.10.0-7.fc17.x86_64 <br> vdsm-cli-4.10.0-7.fc17.noarch <br> vdsm-xmlrpc-4.10.0-7.fc17.noarch <br> vdsm-rest-4.10.0-7.fc17.noarch <br> <br> Joop<br> <br> </body> </html> --------------030102000703080903010508--