On Sun, Sep 23, 2012 at 03:42:38PM +0200, Joop wrote:
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
You are using an older code base, relative to the original poster, and
it seems that the mode of failure is different. I suppose you do not
have
>>>systemd-vdsmd[538]: vdsm: Failed to define network
filters on
>>>libvirt[FAILED]
but something else causing vdsm to fail to start. Could you look in the
logs for clues?
Regards,
Dan.