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
Re: [systemd-devel] Where are the places systemd logs?
Am 07.01.20 um 02:16 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 7:49 PM Reindl Harald wrote: >> >> >> >> Am 07.01.20 um 01:43 schrieb Jeffrey Walton: >>> On Mon, Jan 6, 2020 at 7:41 PM Reindl Harald wrote: Am 07.01.20 um 01:34 schrieb Jeffrey Walton: > I am missing information about my services. I've got dead services > without logs. > > Where are the places systemd logs? journalctl unless you configure rsylog or something else to fetch the logs for classic textfiles >>> >>> No, journalctl is missing the entries. >> >> you really need to be morte specific what you are talking about at all - >> i get the feeling you talk about logs which are completly unrelated to >> syslog at all >> >>> Is there a way to configure systemd to log to /var/log/messages? >> >> no, and anything that's not visibile in journalctl simply don't exist > > Thanks. > > Something is broken here. I can manually start a service, but systemd > can't/won't automatically start it at boot. But the kicker is, there > are no logs anywhere until I manually start it. > > The service was previously [trying to] starting at boot, but it failed > to start because systemd seems to lie about when the network is > available. So I added additional After= and Wants=, and now no service > and no logs. > > I really don't get this tool and why it hides so much information from people. i don't hide anything what about stop talking generic stuff and post your systemd-units and learn about "systemctl status" which at least on not 10 years old systems even outputs the logs of a specific service including stdout/stderr ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Where are the places systemd logs?
On Mon, Jan 6, 2020 at 7:49 PM Reindl Harald wrote: > > > > Am 07.01.20 um 01:43 schrieb Jeffrey Walton: > > On Mon, Jan 6, 2020 at 7:41 PM Reindl Harald wrote: > >> > >> Am 07.01.20 um 01:34 schrieb Jeffrey Walton: > >>> I am missing information about my services. I've got dead services > >>> without logs. > >>> > >>> Where are the places systemd logs? > >> > >> journalctl unless you configure rsylog or something else to fetch the > >> logs for classic textfiles > > > > No, journalctl is missing the entries. > > you really need to be morte specific what you are talking about at all - > i get the feeling you talk about logs which are completly unrelated to > syslog at all > > > Is there a way to configure systemd to log to /var/log/messages? > > no, and anything that's not visibile in journalctl simply don't exist Thanks. Something is broken here. I can manually start a service, but systemd can't/won't automatically start it at boot. But the kicker is, there are no logs anywhere until I manually start it. The service was previously [trying to] starting at boot, but it failed to start because systemd seems to lie about when the network is available. So I added additional After= and Wants=, and now no service and no logs. I really don't get this tool and why it hides so much information from people. Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Where are the places systemd logs?
Am 07.01.20 um 01:43 schrieb Jeffrey Walton: > On Mon, Jan 6, 2020 at 7:41 PM Reindl Harald wrote: >> >> Am 07.01.20 um 01:34 schrieb Jeffrey Walton: >>> I am missing information about my services. I've got dead services without >>> logs. >>> >>> Where are the places systemd logs? >> >> journalctl unless you configure rsylog or something else to fetch the >> logs for classic textfiles > > No, journalctl is missing the entries. you really need to be morte specific what you are talking about at all - i get the feeling you talk about logs which are completly unrelated to syslog at all > Is there a way to configure systemd to log to /var/log/messages? no, and anything that's not visibile in journalctl simply don't exist P.S.: don't break threading by send off-list copies, this is a maling-list, no need to address my directly too ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Where are the places systemd logs?
On Mon, Jan 6, 2020 at 7:41 PM Reindl Harald wrote: > > Am 07.01.20 um 01:34 schrieb Jeffrey Walton: > > I am missing information about my services. I've got dead services without > > logs. > > > > Where are the places systemd logs? > > journalctl unless you configure rsylog or something else to fetch the > logs for classic textfiles No, journalctl is missing the entries. Is there a way to configure systemd to log to /var/log/messages? Jeff ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Where are the places systemd logs?
Am 07.01.20 um 01:34 schrieb Jeffrey Walton: > I am missing information about my services. I've got dead services without > logs. > > Where are the places systemd logs? journalctl unless you configure rsylog or something else to fetch the logs for classic textfiles ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Where are the places systemd logs?
I am missing information about my services. I've got dead services without logs. Where are the places systemd logs? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Better network naming on Hyper-V/Azure?
About a year ago there was some discussion on having persistent network names on Hyper-V/Azure. Haiyang did some patches to add an attribute which could be used by udev to do this. But there are some reluctance because of how the channel id works. The motivation to provide network naming is to allow vmbus to change to parallel probing. Right now probing is serialized so naming is always in same order. My question is what exactly does systemd/udev need to provide persistent naming. The obvious ones are: 1. Must be unique (although PCI slot isn't) 2. Must be persistent across reboot. 3. Must be stable if device is removed. There are more questions. 1. Is there a particular ordering and non-reuse requirement. Obviously, names have to be 15 characters or less but what else. 2. How to handle the device associated with Accelerated Networking? Do you want to hide or rename the VF that is associated with the virtual device? There are a couple of other quirks: 1. The current cloudinit and other startup applications require eth0 as the administrative and always there interface, hard wired into the code. How to handle that? 2. Hyper-V has the ability for host administrator to assign a name, but it is more of a free form string so it is used as default network description. 3. Azure has names as part of the CLI for manipulating VM's but these are not currently exposed to guest. If this could happen would it help or hurt. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Portable service and bind paths
On Mon, Jan 6, 2020 at 1:40 PM Lennart Poettering wrote: > > If possible use DynamicUser=1, i.e. have a short-lived user that only > exists while your service is running. > > For some usecases that doesn#t work though. There's a TODO list item, > to add AllocateUser= as new switch to create a user persistently on > first start, as an alternative for such cases. Nobody worked on that > yet though. And of course, it's much less sexy since for such users > the portable services would suddenly leave traces on the system, in a > way that is never cleaned up... > I will see if I can get DynamicUser to work. If I understand that correctly, it is mainly useful when the service is truly self contained / having its own sandbox. I want the service and myself to be able to read and write to the files in its configuration / runtime directory. That is why I have Bind-mounted it into the service's file system. Need to read up on the state directory concept for DynamicUser. But it seems complex. The AllocateUser concept seems very useful for when the usecase is to bundle up a fast moving application with all its dependencies. I would not mind so much about the traces that can be left. If it is implemented, probably should include something like AllocateGroup too. By the way, after working with portable services, I am impressed. Simpler than the alternatives (after some initial confusion on my part.) Best regards Claes -- C l a e sH o l m e r s o n ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Verbose output from systemctl?
Check journalctl for errors (journalctl -e is probably what you'd want). On Mon, Jan 6, 2020, 7:51 AM Jeffrey Walton wrote: > Hi Everyone, > > I'm trying to install a service. The script is failing with: > > + systemctl enable callboot-monitor.service > Failed to enable unit: File callboot-monitor.service: Invalid argument > + exit 1 > > The man page does not list an option for verbose output, and there is > no -v option. > > How do I get more information about the failure? > > Thanks. > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Verbose output from systemctl?
Hi Everyone, I'm trying to install a service. The script is failing with: + systemctl enable callboot-monitor.service Failed to enable unit: File callboot-monitor.service: Invalid argument + exit 1 The man page does not list an option for verbose output, and there is no -v option. How do I get more information about the failure? Thanks. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Portable service and bind paths
On So, 05.01.20 19:25, Claes H (claesatw...@gmail.com) wrote: > Turns out the problem was not with the mount - that was working well. > Instead it was a user problem and I did not realize the process ran as > root and used a different home directory. > When I added the user homeassistant in the host and added it to the > User= configuration in the service file it worked > But this required the "admin" of the host to do something additional, > it did not work "out of the box". > > I was thinking - how is it supposed to work with a portable service, > which user is it recommended to run as? > Maybe portablectl attach should create the user the service has > declared, if it does not exist already? > Or should is there be a general user that portable services to run as? > Interested to hear if there is any recommendation for how a portable > service "packager" should define the user aspect of the service If possible use DynamicUser=1, i.e. have a short-lived user that only exists while your service is running. For some usecases that doesn#t work though. There's a TODO list item, to add AllocateUser= as new switch to create a user persistently on first start, as an alternative for such cases. Nobody worked on that yet though. And of course, it's much less sexy since for such users the portable services would suddenly leave traces on the system, in a way that is never cleaned up... Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
