doc:appunti:linux:sa:systemd_tmpfiles_problem
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:linux:sa:systemd_tmpfiles_problem [2024/02/22 12:48] – [Analyzing Systemd] niccolo | doc:appunti:linux:sa:systemd_tmpfiles_problem [2024/02/26 09:50] (current) – [Analyzing Systemd] niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Problem with systemd-tmpfiles-setup service ====== | ====== Problem with systemd-tmpfiles-setup service ====== | ||
- | In a **Debian 12 Bookworm** installation I faced several | + | In a **Debian 12 Bookworm** installation I faced some problems at bootstrap. Some services does not start basically because the **%%/ |
< | < | ||
Line 16: | Line 16: | ||
</ | </ | ||
- | I.e. the service **sysinit.target** cannot start due a service ordering problem, so it decided to delete the **systemd-tmpfiles-setup.service**. The problem could be with other Systemd unit too, e.g. the **avahi-daemon.socket**: | + | I.e. the service **sysinit.target** cannot start due a service ordering problem, so Systemd |
< | < | ||
Line 32: | Line 32: | ||
</ | </ | ||
- | May be the problem was introduced by this Postfix/ | + | The command highlights an **ordering cycle** problem, which causes |
+ | < | ||
+ | sockets.target: | ||
+ | sockets.target: | ||
+ | ... | ||
+ | sockets.target: | ||
+ | cycle starting with sockets.target/ | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | Notice that the ordering (and the deleting choice) is not deterministic: | ||
+ | |||
+ | The problem was introduced by this custom Postfix/ | ||
+ | **[[postfix_courier_authdaemon_debian_12]]**. In fact disabling the Systemd '' | ||
+ | |||
+ | In this specific case the problem was completely solved changing the dependencies of the **[[https:// | ||
doc/appunti/linux/sa/systemd_tmpfiles_problem.txt · Last modified: 2024/02/26 09:50 by niccolo