ansible.builtin.systemd_service module – Manage systemd units
Note
This module is part of ansible-core and included in all Ansible
installations. In most cases, you can use the short
module name
systemd_service even without specifying the collections keyword.
However, we recommend you use the Fully Qualified Collection Name (FQCN) ansible.builtin.systemd_service for easy linking to the
module documentation and to avoid conflicting with other collections that may have
the same module name.
Synopsis
Controls systemd units (services, timers, and so on) on remote hosts.
Aliases: systemd
Requirements
The below requirements are needed on the host that executes this module.
A system managed by systemd.
Parameters
Parameter |
Comments |
|---|---|
Run daemon_reexec command before doing any other operations, the systemd manager will serialize the manager state. Choices:
|
|
Run daemon-reload before doing any other operations, to make sure systemd has read any changes. When set to Choices:
|
|
Whether the unit should start on boot. At least one of state and enabled are required. Choices:
|
|
Whether to override existing symlinks. Choices:
|
|
Whether the unit should be masked or not, a masked unit is impossible to start. Choices:
|
|
Name of the unit. This parameter takes the name of exactly one unit to work with. When no extension is given, it is implied to a When using in a chroot environment you always need to specify the name of the unit with the extension. For example, |
|
Do not synchronously wait for the requested operation to finish. Enqueued job will continue without Ansible blocking on its completion. Choices:
|
|
Run systemctl within a given service manager scope, either as the default system scope For systemd to work with ‘user’, the executing user must have its own instance of dbus started and accessible (systemd requirement). The user dbus process is normally started during normal login, but not during the run of Ansible tasks. Otherwise you will probably get a ‘Failed to connect to bus: no such file or directory’ error. The user must have access, normally given via setting the Choices:
|
|
Choices:
|
Attributes
Attribute |
Support |
Description |
|---|---|---|
Support: full |
Can run in check_mode and return changed status prediction without modifying target |
|
Support: none |
Will return details on what has changed (or possibly needs changing in check_mode), when in diff mode |
|
Platform: posix |
Target OS/families that can be operated against |
Notes
Note
Since 2.4, one of the following options is required
state,enabled,masked,daemon_reload, (daemon_reexecsince 2.8), and all exceptdaemon_reloadand (daemon_reexecsince 2.8) also requirename.Before 2.4 you always required
name.Globs are not supported in name, i.e
postgres*.service.The service names might vary by specific OS/distribution
The order of execution when having multiple properties is to first enable/disable, then mask/unmask and then deal with service state. It has been reported that systemctl can behave differently depending on the order of operations if you do the same manually.
Examples
- name: Make sure a service unit is running
ansible.builtin.systemd_service:
state: started
name: httpd
- name: Stop service cron on debian, if running
ansible.builtin.systemd_service:
name: cron
state: stopped
- name: Restart service cron on centos, in all cases, also issue daemon-reload to pick up config changes
ansible.builtin.systemd_service:
state: restarted
daemon_reload: true
name: crond
- name: Reload service httpd, in all cases
ansible.builtin.systemd_service:
name: httpd.service
state: reloaded
- name: Enable service httpd and ensure it is not masked
ansible.builtin.systemd_service:
name: httpd
enabled: true
masked: no
- name: Enable a timer unit for dnf-automatic
ansible.builtin.systemd_service:
name: dnf-automatic.timer
state: started
enabled: true
- name: Just force systemd to reread configs (2.4 and above)
ansible.builtin.systemd_service:
daemon_reload: true
- name: Just force systemd to re-execute itself (2.8 and above)
ansible.builtin.systemd_service:
daemon_reexec: true
- name: Run a user service when XDG_RUNTIME_DIR is not set on remote login
ansible.builtin.systemd_service:
name: myservice
state: started
scope: user
environment:
XDG_RUNTIME_DIR: "/run/user/{{ myuid }}"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
A dictionary with the key=value pairs returned from Returned: success Sample: |