[systemd-devel] Service fails to start with no log messages
Jeffrey Walton
noloader at gmail.com
Tue Jan 7 01:46:45 UTC 2020
On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald <h.reindl at thelounge.net> wrote:
>
> Am 07.01.20 um 02:28 schrieb Jeffrey Walton:
> > I'm trying to determine my service fails to start. I copied the
> > service to the systemd unit directory, and then enabled and started
> > the service. Upon reboot the service is not started automatically.
> >
> > Here are the logs:
>
> Jan 06 20:25:33 raspberrypi systemd[1]: graphical.target: Job
> callboot-ui.service/start deleted to break ordering cycle starting
> with graphical.target/start
>
> you have some conflicting After/Before ordering which is impossible to
> solve automatically, it's that simple
Maybe I can try this... How do I tell Systemd to use After= and Wants=
such that "5 seconds after all systems services have actually
started"?
I don't use any Befores=, so I hope that is not a problem.
Jeff
More information about the systemd-devel
mailing list