[systemd-devel] gluster & libvritd

[Lennart Poettering]

On Wed, 18.01.17 12:30, lejeczek (peljasz at yahoo.co.uk) wrote:

> sorry guys, I bugged libvirtd but... weirdly, quiet there, so I'm hoping an
> expert here would share a thought.
> 
> I've a few VM guest which work/run perfectly fine, I believe, except for
> autostart.
> Configuration of system, gluster and libvirt is pretty regular and not
> complex.
> Errors I see:
> ...
> failed to initialize gluster connection (src=0x7f9424266350
> priv=0x7f94242922b0): Transport endpoint is
> internal error: Failed to autostart VM 'rhel-work2': failed to initialize
> gluster connection (src=0x7f9
> failed to initialize gluster connection (src=0x7f942423fef0
> priv=0x7f9424256320): Transport endpoint is
> internal error: Failed to autostart VM 'rhel-work3': failed to initialize
> gluster connection (src=0x7f9
> failed to initialize gluster connection (src=0x7f9424261b20
> priv=0x7f94242a18b0): Transport endpoint is
> internal error: Failed to autostart VM 'rhel-work1': failed to initialize
> gluster connection (src=0x7f9
> ...
> 
> I tried to make systemd libvirtd to wait for gluster:
> 
> After=glusterd.service
> 
> but if that's all required then, well, still fails.
> Would you have any suggestions?

Are you sure that glusterd guarantees that it is fully connectible
when telling systemd its ready?

Please ask the gluster folks about that, it's really a question
specific to that service.

Lennart

-- 
Lennart Poettering, Red Hat