2019-01-12 15:53:00 +00:00
|
|
|
---
|
|
|
|
|
2020-07-29 10:37:05 +00:00
|
|
|
- name: Ensure systemd is reloaded
|
2022-07-18 07:39:08 +00:00
|
|
|
ansible.builtin.service:
|
2022-02-05 20:32:54 +00:00
|
|
|
daemon_reload: true
|
2019-01-12 15:53:00 +00:00
|
|
|
|
2020-07-29 10:37:05 +00:00
|
|
|
- name: Ensure Matrix services are stopped
|
2022-07-18 07:39:08 +00:00
|
|
|
ansible.builtin.service:
|
2022-11-23 06:43:46 +00:00
|
|
|
name: "{{ item.name }}"
|
2019-01-12 15:53:00 +00:00
|
|
|
state: stopped
|
2022-11-23 06:43:46 +00:00
|
|
|
with_items: "{{ matrix_systemd_services_list | sort (attribute='priority,name', reverse=true) }}"
|
2020-07-29 10:37:05 +00:00
|
|
|
when: not ansible_check_mode
|
2019-01-12 15:53:00 +00:00
|
|
|
|
2020-07-29 10:37:05 +00:00
|
|
|
- name: Ensure Matrix services are started
|
2022-07-18 07:39:08 +00:00
|
|
|
ansible.builtin.service:
|
2022-11-23 06:43:46 +00:00
|
|
|
name: "{{ item.name }}"
|
2019-01-12 15:53:00 +00:00
|
|
|
state: started
|
2022-11-23 06:43:46 +00:00
|
|
|
enabled: "{{ matrix_systemd_services_autostart_enabled }}"
|
|
|
|
with_items: "{{ matrix_systemd_services_list | sort (attribute='priority,name') }}"
|
2020-07-29 10:37:05 +00:00
|
|
|
when: not ansible_check_mode
|
2019-04-03 08:19:06 +00:00
|
|
|
|
|
|
|
# If we check service state immediately, we may succeed,
|
|
|
|
# because it takes some time for the service to attempt to start and actually fail.
|
|
|
|
#
|
|
|
|
# Waiting too long (30s) may not work for a similar reason,
|
|
|
|
# as we may run into systemd's automatic restart logic retrying the service.
|
|
|
|
- name: Wait a bit, so that services can start (or fail)
|
2022-07-18 08:22:05 +00:00
|
|
|
ansible.builtin.wait_for:
|
2021-05-19 05:39:28 +00:00
|
|
|
timeout: "{{ matrix_common_after_systemd_service_start_wait_for_timeout_seconds }}"
|
2019-04-03 08:19:06 +00:00
|
|
|
delegate_to: 127.0.0.1
|
|
|
|
become: false
|
|
|
|
|
2022-11-23 06:55:34 +00:00
|
|
|
- block:
|
|
|
|
- name: Populate service facts
|
|
|
|
ansible.builtin.service_facts:
|
|
|
|
|
|
|
|
- name: Fail if service isn't detected to be running
|
|
|
|
ansible.builtin.fail:
|
|
|
|
msg: >-
|
|
|
|
{{ item }} was not detected to be running.
|
|
|
|
It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.).
|
|
|
|
Try running `systemctl status {{ item }}` and `journalctl -fu {{ item }}` on the server to investigate.
|
|
|
|
If you're on a slow or overloaded server, it may be that services take a longer time to start and that this error is a false-positive.
|
|
|
|
You can consider raising the value of the `matrix_common_after_systemd_service_start_wait_for_timeout_seconds` variable.
|
|
|
|
See `roles/custom/matrix-common-after/defaults/main.yml` for more details about that.
|
|
|
|
with_items: "{{ matrix_systemd_services_list | map(attribute='name') }}"
|
|
|
|
when:
|
|
|
|
- "item.endswith('.service') and (ansible_facts.services[item] | default(none) is none or ansible_facts.services[item].state != 'running')"
|