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 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 something > > else and so by luck > > > > systemd does not lie here - you just need to do the ordering proper > > based on how your network is configured at all which you refuse to tell > > > > so your better options would have been report thate network ordering > > problem here before touch anything else > > > > "There are absolutely 0 entires about my monitor service" is because > > it's thrown out of the startup transaction cause dby your other config > > screwup > > And there we have it. Systemd is not logging the problem. And then you > wonder why users like me go down rabbit holes. > > Perhaps Systemd should hire someone who understands usability and > design. Maybe they can explain why throwing important information away > is a bad idea. Not helpful at all. Consider both of you warned. One more post like this and you are moderated. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 information to > troubleshoot a problem. Cron was replaced with a more complex system > that does not work as expected. Jeff. This attitude is not appropriate either. Guys, stop posting this kind of stuff. Be civil, or I'll put both of you on moderation. Please ask you questions in a friendly tone, and please answer questions in a friendly tone. It's fine to be direct, but don#t deride stuff as "joke" all the time. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 > >> dependencies you add to your units problems gow > >> > >> perfomance wise because you break parallel starts for no benefit and > >> because of such unsolveable cycles if you obviously don't understand > >> what you define becaus eotherwise you won't have After/Before/wants in > >> combinations which are impossible > >> > >> 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 ordering problem I need Systemd to stop lying about when the > > network is ready. > > it don't - you most likely did something wrong by the ordering afetr > networking and you even don't tell how your networking is configured > (network.service, networkmanager, systemd-networkd...) > > in other words: instead fix your network-ordering properly you touch > other random stuff in weird ways and it's annyoing that one needs to ask > for each and every bit given your initial posting was a completly joke > with no single information and the whole topic "Service fails to start > with no log messages" is wrong at all Reindl, tone it down please. That's not helpful. "was completely joke" is not nice. I mean, yes I think jeffreys mail could be more precise, but that's not a reason to call something "a joke"... Thank you for understanding, Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 ordering problem I need Systemd to stop lying about when the > network is ready. systemd has no clue when your network is "ready", since that might mean many things. i.e. did you acquire a DHCP lease? did you just UP the iface? Did you reach some server? in systemd we can't know this, as in particular on clients and on servers "network ready" means very different things. If you use systemd-network-wait-online.service you can configure what "up" means. It's not enabled by default, but you can do that with "systemctl enable". It's not enabled by default since in the general case we don't want the local boot to be delayed because of some external condition. If you use NetworkMAnager there's a similar service. > I keep pushing it back because I can't get accurate information from Systemd. I am sorry, what? Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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: > > $ journalctl -e | grep callboot > Jan 06 20:25:33 raspberrypi systemd[1]: graphical.target: Found > dependency on callboot-ui.service/start > 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 The logs actually show you the full ordering cycle you defined. But your "grep" hides that. Drop the "grep", and look for the lines around the above it tells you where you have an ordering cycle. Ordering cycle means your service is ordererd after some other service (or multiple of them) that are ultimately ordered again after your own service, which is hence a cycle. systemd cannot fulfill that and complains. > > $ cat /etc/systemd/system/callboot-monitor.service > [Unit] > Description=Callboot service > > # This service waits for the UI. It slows down the > # boot so the service starts without failure. > After=graphical.target > Wants=graphical.target > # Service waits for the USB modem > After=usb.target > Wants=usb.target > > [Service] > Type=simple > ExecStart=/opt/callboot/bin/callboot.exe > > [Install] > WantedBy=multi-user.target So this is your cycle: your service is declared to start before multi-user.target (since WantedBy= generally implies Before=, unless DefaultDependencies=no is specified), but after graphical.target, but graphical.target itself is ordered after multi-user.target. Hence you declare the following cycle: graphical.target → callboot-monitor.service → multi-user.target → graphical.target Break that up. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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"? Such a concept does not exist. I mean your service is a system service itself, so what is that even supposed to mean that the service shall start 5s after it already started? But even if you mean to say "5s after all other services", then think how that falls apart if you have multiple services declaring that. hence, in systemd there's no concept for that. Instead you are supposed to properly order your units and declare the exact ordering you rely on and not less nor more. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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: > > > > whatever crap you did ending in the ordering cycle did not solve > > your wrong ordering after network, it just burried it by slow down > > something else and so by luck > > > > systemd does not lie here - you just need to do the ordering proper > > based on how your network is configured at all which you refuse to > > tell > > > > so your better options would have been report thate network ordering > > problem here before touch anything else > > > > "There are absolutely 0 entires about my monitor service" is because > > it's thrown out of the startup transaction cause dby your other > > config screwup > > And there we have it. Systemd is not logging the problem. And then you > wonder why users like me go down rabbit holes. > > Perhaps Systemd should hire someone who understands usability and > design. Maybe they can explain why throwing important information away > is a bad idea. > > Jeff I can't tell whether you're deliberately trolling Reindl, which helps nobody and certainly doesn't help solve your problem, or whether you simply have a lot of prejudice about systemd that you're keen to talk about. Either way, it's counterproductive; please stop it. Just write about your technical issues. I'd suggest you start again, and try to post complete information - such as you have - about your services and problems with them. But first please reread all Reindl and Paul's comments and try to apply the useful information that is contained within them. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 Immediately jump to the end of the journal inside the implied pager tool. This implies -n1000 to guarantee that the pager will not buffer logs of unbounded size. This may be overridden with an explicit -n with some other numeric value, while -nall will disable this cap. Note that this option is only supported for the less(1) pager. Does `journalctl -b | grep -i callboot` show something? `-b` only shows log messages for the current boot. […] Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 something >>> else and so by luck >>> >>> systemd does not lie here - you just need to do the ordering proper >>> based on how your network is configured at all which you refuse to tell >>> >>> so your better options would have been report thate network ordering >>> problem here before touch anything else >>> >>> "There are absolutely 0 entires about my monitor service" is because >>> it's thrown out of the startup transaction cause dby your other config >>> screwup >> >> And there we have it. Systemd is not logging the problem. And then you >> wonder why users like me go down rabbit holes. > > it does and common sense should tell you *fix that* and whatever you did > introducing that issue by try to work aorund a completly different issue > (network ordering) was simply bullhsit and has to be reverted > > common sense should tell you that *every* error / warning should be > adressed before try to debug something else further > > 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 comment alone shows the bullshit you are doing "It slows down the boot so the service starts without failure" bsides that it obviously don#t work "slow down the boot" is no solution for a problem # This service waits for the UI. It slows down the # boot so the service starts without failure. After=graphical.target Wants=graphical.target # Service waits for the USB modem After=usb.target Wants=usb.target ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 did ending in the ordering cycle did not solve your >> wrong ordering after network, it just burried it by slow down something >> else and so by luck >> >> systemd does not lie here - you just need to do the ordering proper >> based on how your network is configured at all which you refuse to tell >> >> so your better options would have been report thate network ordering >> problem here before touch anything else >> >> "There are absolutely 0 entires about my monitor service" is because >> it's thrown out of the startup transaction cause dby your other config >> screwup > > And there we have it. Systemd is not logging the problem. And then you > wonder why users like me go down rabbit holes. it does and common sense should tell you *fix that* and whatever you did introducing that issue by try to work aorund a completly different issue (network ordering) was simply bullhsit and has to be reverted common sense should tell you that *every* error / warning should be adressed before try to debug something else further 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 > wrong ordering after network, it just burried it by slow down something > else and so by luck > > systemd does not lie here - you just need to do the ordering proper > based on how your network is configured at all which you refuse to tell > > so your better options would have been report thate network ordering > problem here before touch anything else > > "There are absolutely 0 entires about my monitor service" is because > it's thrown out of the startup transaction cause dby your other config > screwup And there we have it. Systemd is not logging the problem. And then you wonder why users like me go down rabbit holes. Perhaps Systemd should hire someone who understands usability and design. Maybe they can explain why throwing important information away is a bad idea. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 something else and so by luck systemd does not lie here - you just need to do the ordering proper based on how your network is configured at all which you refuse to tell so your better options would have been report thate network ordering problem here before touch anything else "There are absolutely 0 entires about my monitor service" is because it's thrown out of the startup transaction cause dby your other config screwup ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 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 >>> >>> But there is no ordering problem. callboot-ui.service is not related >>> to callboot-monitor.service. callboot-ui.service is a Qt program and >>> front-end to the LCD screen. callboot-monitor.service is a command >>> line program that waits for reads of the modem. >>> >>> The only thing they have in common is they use the same database. >> >> frankly "to break ordering cycle starting with graphical.target" and >> your "callboot-monitor.service" has "Wants=graphical.target" and you >> call that "not releated"? >> >> 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 >> dependencies you add to your units problems gow >> >> perfomance wise because you break parallel starts for no benefit and >> because of such unsolveable cycles if you obviously don't understand >> what you define becaus eotherwise you won't have After/Before/wants in >> combinations which are impossible >> >> 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 ordering problem I need Systemd to stop lying about when the > network is ready. it don't - you most likely did something wrong by the ordering afetr networking and you even don't tell how your networking is configured (network.service, networkmanager, systemd-networkd...) in other words: instead fix your network-ordering properly you touch other random stuff in weird ways and it's annyoing that one needs to ask for each and every bit given your initial posting was a completly joke with no single information and the whole topic "Service fails to start with no log messages" is wrong at all >>> >>> 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. >> >> there are, it's orderred after graphical.traget which has a dependency cycle > > There are absolutely 0 entires about my monitor service: > > $ journalctl -e | grep -i callboot | grep monitor > $ > > If you are claiming I fiddled with graphical.target and when/how it > starts, I did not. god damned! you did with "After=graphical.target" and "Wants=graphical.target" as well as nobody knows what "usb.target" does given it's not default than your "callboot-ui.service" has a dependency cycle in context of "ordering cycle starting with graphical.target" which needs to be solved and you pretend you did not fiddle with grahpical target frankly - remove all your Wants where you likely only think you know what you are doing and also all your After/Before and start to define them from scratch while you are at it verify that you ordering after network was done correctly because what you did because of it was the start of all the other issues nad all your problemls magically disappear what people all the time are doing wrong is not understaning how network ordering works and given that you are not willing to provide informations by common sense unasked im am done with you the problem is not systemd, not journald and not systemd-timers, it's in front of the screen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 > >>> 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 > > > > But there is no ordering problem. callboot-ui.service is not related > > to callboot-monitor.service. callboot-ui.service is a Qt program and > > front-end to the LCD screen. callboot-monitor.service is a command > > line program that waits for reads of the modem. > > > > The only thing they have in common is they use the same database. > > frankly "to break ordering cycle starting with graphical.target" and > your "callboot-monitor.service" has "Wants=graphical.target" and you > call that "not releated"? > > 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 > dependencies you add to your units problems gow > > perfomance wise because you break parallel starts for no benefit and > because of such unsolveable cycles if you obviously don't understand > what you define becaus eotherwise you won't have After/Before/wants in > combinations which are impossible > > 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 ordering problem I need Systemd to stop lying about when the > >>> network is ready. > >> > >> it don't - you most likely did something wrong by the ordering afetr > >> networking and you even don't tell how your networking is configured > >> (network.service, networkmanager, systemd-networkd...) > >> > >> in other words: instead fix your network-ordering properly you touch > >> other random stuff in weird ways and it's annyoing that one needs to ask > >> for each and every bit given your initial posting was a completly joke > >> with no single information and the whole topic "Service fails to start > >> with no log messages" is wrong at all > > > > 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. > > there are, it's orderred after graphical.traget which has a dependency cycle There are absolutely 0 entires about my monitor service: $ journalctl -e | grep -i callboot | grep monitor $ If you are claiming I fiddled with graphical.target and when/how it starts, I did not. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 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 > > But there is no ordering problem. callboot-ui.service is not related > to callboot-monitor.service. callboot-ui.service is a Qt program and > front-end to the LCD screen. callboot-monitor.service is a command > line program that waits for reads of the modem. > > The only thing they have in common is they use the same database. frankly "to break ordering cycle starting with graphical.target" and your "callboot-monitor.service" has "Wants=graphical.target" and you call that "not releated"? 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 dependencies you add to your units problems gow perfomance wise because you break parallel starts for no benefit and because of such unsolveable cycles if you obviously don't understand what you define becaus eotherwise you won't have After/Before/wants in combinations which are impossible 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 ordering problem I need Systemd to stop lying about when the >>> network is ready. >> >> it don't - you most likely did something wrong by the ordering afetr >> networking and you even don't tell how your networking is configured >> (network.service, networkmanager, systemd-networkd...) >> >> in other words: instead fix your network-ordering properly you touch >> other random stuff in weird ways and it's annyoing that one needs to ask >> for each and every bit given your initial posting was a completly joke >> with no single information and the whole topic "Service fails to start >> with no log messages" is wrong at all > > 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. there are, it's orderred after graphical.traget which has a dependency cycle > The joke is Systemd and its inability to provide basic information to > troubleshoot a problem. the joke is that not understanding basic onformations don't mean they aren't there so what about revert all the nonsense you did after your conclusion sstemd is lying about the network state and review how you tried ot order stuff after networking which you pretty sure simply did wrong > Cron was replaced with a more complex system > that does not work as expected. completly unrelated nonsense besides that it works and you can still use crond like 20 years ago if you like ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 > >>> > >>> But there is no ordering problem. callboot-ui.service is not related > >>> to callboot-monitor.service. callboot-ui.service is a Qt program and > >>> front-end to the LCD screen. callboot-monitor.service is a command > >>> line program that waits for reads of the modem. > >>> > >>> The only thing they have in common is they use the same database. > >> > >> frankly "to break ordering cycle starting with graphical.target" and > >> your "callboot-monitor.service" has "Wants=graphical.target" and you > >> call that "not releated"? > >> > >> 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 > >> dependencies you add to your units problems gow > >> > >> perfomance wise because you break parallel starts for no benefit and > >> because of such unsolveable cycles if you obviously don't understand > >> what you define becaus eotherwise you won't have After/Before/wants in > >> combinations which are impossible > >> > >> 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 ordering problem I need Systemd to stop lying about when the > > network is ready. > > it don't - you most likely did something wrong by the ordering afetr > networking and you even don't tell how your networking is configured > (network.service, networkmanager, systemd-networkd...) > > in other words: instead fix your network-ordering properly you touch > other random stuff in weird ways and it's annyoing that one needs to ask > for each and every bit given your initial posting was a completly joke > with no single information and the whole topic "Service fails to start > with no log messages" is wrong at all 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 information to troubleshoot a problem. Cron was replaced with a more complex system that does not work as expected. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 >>> >>> But there is no ordering problem. callboot-ui.service is not related >>> to callboot-monitor.service. callboot-ui.service is a Qt program and >>> front-end to the LCD screen. callboot-monitor.service is a command >>> line program that waits for reads of the modem. >>> >>> The only thing they have in common is they use the same database. >> >> frankly "to break ordering cycle starting with graphical.target" and >> your "callboot-monitor.service" has "Wants=graphical.target" and you >> call that "not releated"? >> >> 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 >> dependencies you add to your units problems gow >> >> perfomance wise because you break parallel starts for no benefit and >> because of such unsolveable cycles if you obviously don't understand >> what you define becaus eotherwise you won't have After/Before/wants in >> combinations which are impossible >> >> 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 ordering problem I need Systemd to stop lying about when the > network is ready. it don't - you most likely did something wrong by the ordering afetr networking and you even don't tell how your networking is configured (network.service, networkmanager, systemd-networkd...) in other words: instead fix your network-ordering properly you touch other random stuff in weird ways and it's annyoing that one needs to ask for each and every bit given your initial posting was a completly joke with no single information and the whole topic "Service fails to start with no log messages" is wrong at all http://www.catb.org/~esr/faqs/smart-questions.html#beprecise ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 > > > > But there is no ordering problem. callboot-ui.service is not related > > to callboot-monitor.service. callboot-ui.service is a Qt program and > > front-end to the LCD screen. callboot-monitor.service is a command > > line program that waits for reads of the modem. > > > > The only thing they have in common is they use the same database. > > frankly "to break ordering cycle starting with graphical.target" and > your "callboot-monitor.service" has "Wants=graphical.target" and you > call that "not releated"? > > 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 > dependencies you add to your units problems gow > > perfomance wise because you break parallel starts for no benefit and > because of such unsolveable cycles if you obviously don't understand > what you define becaus eotherwise you won't have After/Before/wants in > combinations which are impossible > > 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 ordering problem I need Systemd to stop lying about when the network is ready. I keep pushing it back because I can't get accurate information from Systemd. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 >>> 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 > > But there is no ordering problem. callboot-ui.service is not related > to callboot-monitor.service. callboot-ui.service is a Qt program and > front-end to the LCD screen. callboot-monitor.service is a command > line program that waits for reads of the modem. > > The only thing they have in common is they use the same database. frankly "to break ordering cycle starting with graphical.target" and your "callboot-monitor.service" has "Wants=graphical.target" and you call that "not releated"? 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 dependencies you add to your units problems gow perfomance wise because you break parallel starts for no benefit and because of such unsolveable cycles if you obviously don't understand what you define becaus eotherwise you won't have After/Before/wants in combinations which are impossible 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 Thanks. But there is no ordering problem. callboot-ui.service is not related to callboot-monitor.service. callboot-ui.service is a Qt program and front-end to the LCD screen. callboot-monitor.service is a command line program that waits for reads of the modem. The only thing they have in common is they use the same database. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[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]: graphical.target: Found dependency on callboot-ui.service/start 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 Jan 06 20:25:39 raspberrypi callboot-trim.sh[332]: Info: Trimming entries older than 120 days Jan 06 20:25:58 raspberrypi callboot-trim.sh[332]: Info: Trimmed 21997 old entries Jan 06 20:25:58 raspberrypi callboot-trim.sh[332]: Info: Vacuuming database Jan 06 20:26:38 raspberrypi systemd[1]: callboot-trim.service: Succeeded. Here is the status: $ systemctl status callboot-monitor.service ● callboot-monitor.service - Callboot service Loaded: loaded (/etc/systemd/system/callboot-monitor.service; enabled; vendor Active: inactive (dead) Here is the service: $ cat /etc/systemd/system/callboot-monitor.service [Unit] Description=Callboot service # This service waits for the UI. It slows down the # boot so the service starts without failure. After=graphical.target Wants=graphical.target # Service waits for the USB modem After=usb.target Wants=usb.target [Service] Type=simple ExecStart=/opt/callboot/bin/callboot.exe [Install] WantedBy=multi-user.target ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
