(forgot to reply to the list)
According to the manual page Requisite= should honor After= BTW:
Requisite=
Similar to Requires=. However, if the units listed here are not
started already, they will not be started and the starting of this
unit will fail immediately. Requisite= does not imply an ordering
dependency, even if both units are started in the same transaction.
Hence this setting should usually be combined with After=, to
ensure this unit is not started before the other unit.
So is the doc wrong, or is there some bug?
Kind regards,
Ulrich Windl
From: Windl, Ulrich
Sent: Thursday, June 5, 2025 2:22 PM
To: 'Mantas Mikulėnas' <graw...@gmail.com>
Subject: RE: [EXT] Re: [systemd-devel] Suggestion for " failed with result
'dependency'."
H!
You are right!:
“systemd[1]: Host and Network Name Lookups is inactive.”
The problem is when you grep for your service name, because it’s not present
anywhere.
Strangely the message “systemd[1]: Reached target Host and Network Name
Lookups.” Appears afterwards.
Doesn’t “After=” play well with “Requisite=”?
Kind regards,
Ulrich Windl
From: Mantas Mikulėnas <graw...@gmail.com>
Sent: Thursday, June 5, 2025 9:27 AM
To: Windl, Ulrich <u.wi...@ukr.de>
Subject: [EXT] Re: [systemd-devel] Suggestion for " failed with result
'dependency'."
On 05/06/2025 10.00, Windl, Ulrich wrote:
Hi!
I wrote a simple service that did not start after boot. The joural message was:
REST-server.service: Job REST-server.service/start failed with result
'dependency'.
Wouldn’t it be helpful to log WHICH dependency failed? As I started the server
meanwhile that information isn’t available any more (it seems).
It is logged in the journal, one line above the message you mention. It is
merely not tagged with _SYSTEMD_UNIT= for 'systemctl status' to find it.
Jun 05 10:25:24 frost systemd[1]: test2.service is inactive.
Jun 05 10:25:24 frost systemd[1]: Dependency failed for test.service.
Jun 05 10:25:24 frost systemd[1]: test.service: Job test.service/start failed
with result 'dependency'.
