Re: [systemd-devel] Service fails to start with no log messages

On Mo, 06.01.20 21:47, Jeffrey Walton (noloa...@gmail.com) wrote: > On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald wrote: > > > > Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > > > To fix my ordering problem I need Systemd to stop lying about when the > > > network is ready. > > > > one last

Re: [systemd-devel] Service fails to start with no log messages

On Mo, 06.01.20 21:06, Jeffrey Walton (noloa...@gmail.com) wrote: > I think that was a very good summary of the problem. > > I want my monitor service to start (it is the most important one), but > there are absolutely no traces of it. > > The joke is Systemd and its inability to provide basic

Re: [systemd-devel] Service fails to start with no log messages

On Di, 07.01.20 03:03, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Especially the "Wants" is problematic and noramlly not needed for > >> enabled services, normally your only use After/NBefore unless there is a > >> compelling resason for Wants/Requires and with growing useless > >>

Re: [systemd-devel] Service fails to start with no log messages

On Mo, 06.01.20 20:57, Jeffrey Walton (noloa...@gmail.com) wrote: > > and to your other post "5 seconds after all systems services have > > actually started" is something which simply don#t exist and can't exist > > at all > > > > fix your orderings and your problems are gone > > To fix my

Re: [systemd-devel] Service fails to start with no log messages

On Mo, 06.01.20 20:28, Jeffrey Walton (noloa...@gmail.com) wrote: > 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: > >

Re: [systemd-devel] Service fails to start with no log messages

On Mo, 06.01.20 20:46, Jeffrey Walton (noloa...@gmail.com) wrote: > On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald 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

Re: [systemd-devel] Service fails to start with no log messages

On Mon, 6 Jan 2020 21:47:37 -0500 Jeffrey Walton wrote: > On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald > wrote: > > > > Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > > > To fix my ordering problem I need Systemd to stop lying about > > > when the network is ready. > > > > one last comment:

Re: [systemd-devel] Service fails to start with no log messages

Dear Jeffrey, On 2020-01-07 03:17, Jeffrey Walton wrote: […] > There are absolutely 0 entires about my monitor service: > > $ journalctl -e | grep -i callboot | grep monitor > $ The switch `-e` implies that by default only 1000 lines are shown. -e, --pager-end

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 03:56 schrieb Reindl Harald: > > > Am 07.01.20 um 03:47 schrieb Jeffrey Walton: >> On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald wrote: >>> >>> Am 07.01.20 um 02:57 schrieb Jeffrey Walton: To fix my ordering problem I need Systemd to stop lying about when the network

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 03:47 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald wrote: >> >> Am 07.01.20 um 02:57 schrieb Jeffrey Walton: >>> To fix my ordering problem I need Systemd to stop lying about when the >>> network is ready. >> >> one last comment: >> >> whatever crap you

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald wrote: > > Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > > To fix my ordering problem I need Systemd to stop lying about when the > > network is ready. > > one last comment: > > whatever crap you did ending in the ordering cycle did not solve your >

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > To fix my ordering problem I need Systemd to stop lying about when the > network is ready. one last comment: whatever crap you did ending in the ordering cycle did not solve your wrong ordering after network, it just burried it by slow down

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 03:17 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 9:13 PM Reindl Harald wrote: >> >> Am 07.01.20 um 03:06 schrieb Jeffrey Walton: >>> On Mon, Jan 6, 2020 at 9:03 PM Reindl Harald wrote: Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 9:13 PM Reindl Harald wrote: > > Am 07.01.20 um 03:06 schrieb Jeffrey Walton: > > On Mon, Jan 6, 2020 at 9:03 PM Reindl Harald wrote: > >> > >> Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > >>> On Mon, Jan 6, 2020 at 8:56 PM Reindl Harald > >>> wrote: > > Am

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 03:06 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 9:03 PM Reindl Harald wrote: >> >> Am 07.01.20 um 02:57 schrieb Jeffrey Walton: >>> On Mon, Jan 6, 2020 at 8:56 PM Reindl Harald wrote: Am 07.01.20 um 02:42 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 9:03 PM Reindl Harald wrote: > > Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > > On Mon, Jan 6, 2020 at 8:56 PM Reindl Harald wrote: > >> > >> Am 07.01.20 um 02:42 schrieb Jeffrey Walton: > >>> On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald > >>> wrote: > > Am

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 02:57 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 8:56 PM Reindl Harald wrote: >> >> Am 07.01.20 um 02:42 schrieb Jeffrey Walton: >>> On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald wrote: Am 07.01.20 um 02:28 schrieb Jeffrey Walton: > I'm trying to determine my

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 8:56 PM Reindl Harald wrote: > > Am 07.01.20 um 02:42 schrieb Jeffrey Walton: > > On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald 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

Re: [systemd-devel] Service fails to start with no log messages

Am 07.01.20 um 02:42 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald 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 >>>

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald 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

Re: [systemd-devel] Service fails to start with no log messages

On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald 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

Re: [systemd-devel] Service fails to start with no log messages

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

[systemd-devel] Service fails to start with no log messages

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: $ journalctl -e | grep callboot Jan 06 20:25:33 raspberrypi systemd[1]: