Antw: Antw: Re: Re: Antw: [EXT] Re: Still confused with socket activation

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx> schrieb am 09.02.2021
um
10:28 in Nachricht <602255B4020000A10003ED3B@xxxxxxxxxxxxxxxxxxxxxxxx>:
>>>> Andrei Borzenkov <arvidjaar@xxxxxxxxx> schrieb am 09.02.2021 um 10:14 in
> Nachricht
> <CAA91j0UtJmQ0y3dGLA6E0xiWXG_UXavY85bKyTYqk5_k+F8Gzg@xxxxxxxxxxxxxx>:
>> On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl
>> <Ulrich.Windl@xxxxxx‑regensburg.de> wrote:
>>>
>>> Thanks and "back to the mess": If I use libvirtd.service instead of
>>> libvirtd‑tls.socket, it does *not* open the TLS socket, even though the
>>> configuration file contains "listen_tls=1"...
> 
> ...and if I use libvirtd‑tls.socket, it fails on restarting:
> Feb 09 10:20:17 h18 systemd[1]: libvirtd‑tls.socket: Socket service 
> libvirtd.service already active, refusing.
> Feb 09 10:20:17 h18 systemd[1]: Failed to listen on Libvirt TLS IP socket.
> Feb 09 10:20:19 h18 pacemaker‑controld[36557]:  notice: Result of start 
> operation for prm_libvirtd on h18: error
> 
>> 
>> libvirtd ‑‑listen
>> 
>> Did you read the link I gave you on the pacemaker list?
> 
> Not yet, but due to your hint I found:
> # If systemd socket activation is disabled, then the following
> # can be used to listen on TCP/TLS sockets
> #LIBVIRTD_ARGS="‑‑listen"
> 
> ("back to the mess")
> 
>> 
>> https://bugzilla.redhat.com/show_bug.cgi?id=1750340#c0 
>> 
>> quoting
>> 
>> ‑‑><‑‑
>> Thus if the mgmt app / admin wants to use TCP/TLS sockets they have two 
>> choices
>> 
>>   ‑ To continue the old approach (setting ‑‑listen in
>> /etc/sysconfig/libvirtd), then they MUST use 'systemctl mask ...' for
>> all the socket units listed above, before libvirtd.service is started.
>> ‑‑><‑‑
>> 
>> Does it not work?
> 
> I'll roll‑back and try ;‑)

OK, I tried (staring libvirtd.service with --listen and without --timout):
Feb 09 10:59:23 h18 libvirtd[42540]: --listen parameter not permitted with
systemd activation sockets, see 'man libvirtd' for further guidance
Feb 09 10:59:23 h18 systemd[1]: libvirtd.service: Main process exited,
code=exited, status=6/NOTCONFIGURED
Feb 09 10:59:23 h18 systemd[1]: Failed to start Virtualization daemon.

Is libvirtd.service (as opposed to libvirtd.socket) as "socket activation"? I
thought: "no".

> 
> Regards,
> Ulrich
> 
> 
> 
> _______________________________________________
> systemd‑devel mailing list
> systemd‑devel@xxxxxxxxxxxxxxxxxxxxx 
> https://lists.freedesktop.org/mailman/listinfo/systemd‑devel 



_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel