For me it is pretty logical, as in: the service started in relation to socket unit gets the respective socket. If service is already started there is no way to pass additional socket to it without restarting it. It may even listen exactly on the socket specified, just creating it on it's own. W dniu 29.01.2021 o 12:30, Ulrich Windl pisze: > Hi! > > I wonder whether this is a bug: > When starting a socket unit that finds ist service active already, I get an error > systemd[1]: libvirtd-tls.socket: Socket service libvirtd.service already active, refusing. > systemd[1]: Failed to listen on Libvirt TLS IP socket. > > When using systemd units in a pacemaker cluster this is fatal: > pacemaker-controld[7467]: notice: Transition 316 action 81 (prm_libvirtd-tls-sock_start_0 on rksaph19): expected 'ok' but got 'error' > > Maybe the special problem is that two socket units (libvirtd-ro.socket, libvirtd-tls.socket) exist to start the same service (libvirtd.service). > > I'm clueless how to handle that. Ideas? > > Regards, > Ulrich > > > > _______________________________________________ > systemd-devel mailing list > systemd-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/systemd-devel >
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
