Hi! I'm having an odd failure using a systemd socket unit controlled by the cluster. (Personally I feel: "cluster and systemd: One resource controller too much". But when you need to control a systemd unit...) When the unit is active already, a start peration fails:
Jan 29 12:12:46 h16 pacemaker-execd[7464]: notice: executing - rsc:prm_libvirtd-tls-sock action:start call_id:198 Jan 29 12:12:46 h16 systemd[1]: Reloading. Jan 29 12:12:47 h16 systemd[1]: libvirtd-tls.socket: Socket service libvirtd.service already active, refusing. Jan 29 12:12:47 h16 systemd[1]: Failed to listen on Libvirt TLS IP socket. Jan 29 12:12:49 h16 pacemaker-controld[7467]: notice: Transition 313 aborted by operation prm_libvirtd-tls-sock_start_0 'modify' on h19: Event failed Jan 29 12:12:49 h16 pacemaker-controld[7467]: notice: Transition 313 action 81 (prm_libvirtd-tls-sock_start_0 on h19): expected 'ok' but got 'error' Jan 29 12:12:49 h16 pacemaker-attrd[7465]: notice: Setting fail-count-prm_libvirtd-tls-sock#start_0[h19]: (unset) -> INFINITY Is there an easy fix other than a software upgrade? Regards, Ulrich _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
