Tatu Argillander
d7487032d2
Ansible can open multiple connections and it's possible for a new socket to open before activation is fully disabled, leaving a zombie sshd process. At least that is the guess. Ubuntu 24.04 suffers from this. Reload the configuration after disabling socket activation to not enable it again. Signed-off-by: Tatu Argillander <[email protected]>
23 lines
614 B
YAML
23 lines
614 B
YAML
---
|
|
- name: Disable systemd-socket activation
|
|
ansible.builtin.systemd:
|
|
name: ssh.socket
|
|
state: stopped
|
|
enabled: false
|
|
masked: true
|
|
|
|
- name: Remove ssh service systemd-socket file
|
|
ansible.builtin.file:
|
|
path: "{{ item }}"
|
|
state: absent
|
|
loop:
|
|
- /etc/systemd/system/ssh.service.d/00-socket.conf
|
|
- /etc/systemd/system/ssh.service.requires/ssh.socket
|
|
- /etc/systemd/system/sockets.target.wants/ssh.socket
|
|
|
|
- name: Ensure ssh service is started after disabling socket activation
|
|
ansible.builtin.systemd:
|
|
name: "{{ sshd_service_name }}"
|
|
state: started
|
|
enabled: true
|