Re: systemd-analyze
Bob, Same: # systemd-analyze critical-chain Bootup is not yet finished. Please try again later. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. -Mike On Thu, Oct 27, 2016 at 2:21 PM, Nix, Robert P. <nix.rob...@mayo.edu> wrote: > Did you try ³systems-analyze critical-path²? If it would work, then it > should show the longest path, which at this point, should be the one which > is incomplete. > -- > Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure > Services > > Mayo Clinic | 200 First Street SW | Rochester, MN 55905 > 507-284-0844 | nix.rob...@mayo.edu > "quando omni flunkus moritati" > > > > > On 10/27/16, 12:24 PM, "Linux on 390 Port on behalf of Michael MacIsaac" > <LINUX-390@VM.MARIST.EDU on behalf of mike99...@gmail.com> wrote: > > >Thanks for the replies. > > > ># systemctl list-units --failed > >0 loaded units listed. Pass --all to see loaded but inactive units, too. > ># systemctl is-system-running > >Unknown operation 'is-system-running'. > > > >With the systemctl status output sent to a file, I found a service > >'waiting'. I stopped it, but still get: > > > ># systemd-analyze time > >Bootup is not yet finished. Please try again later. > > > >I don't really need the output of 'systemd-analyze time' that badly. This > >was more of a curiosity. > > > > -Mike > > > > > >On Thu, Oct 27, 2016 at 12:13 PM, Dimitri John Ledkov <x...@ubuntu.com> > >wrote: > > > >> On 27 October 2016 at 15:32, Michael MacIsaac <mike99...@gmail.com> > >>wrote: > >> > I heard about this new cool command and tried it, but it did not work: > >> > > >> > # systemd-analyze time > >> > Bootup is not yet finished. Please try again later. > >> > > >> > How would I analyze systemd to know why 'bootup is not yet finished'? > >> This > >> > is SLES 12 SP1. > >> > > >> > >> Generic / architecture independent systemd commands to try: > >> > >> $ systemctl list-units --failed > >> > >> Should show some culprits. > >> > >> Also look at full output of $ systemctl list-units > >> > >> and grep/look for things that are activating or waiting. Hopefully > >> this should give you enough hints to figure out what components are > >> not ready yet, to class system as started. > >> > >> Ideally, at the end of the boot you should be able to see that system > >> is in running state: > >> > >> $ systemctl is-system-running > >> running > >> > >> It is for me on machines that I maintain. Loads of things can make > >> systemd believe things are degraded - e.g. when optional services are > >> required or wanted by accident and similar. > >> > >> -- > >> Regards, > >> > >> Dimitri. > >> > >> -- > >> For LINUX-390 subscribe / signoff / archive access instructions, > >> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > >> visit > >> http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> -- > >> For more information on Linux on System z, visit > >> http://wiki.linuxvm.org/ > >> > > > >-- > >For LINUX-390 subscribe / signoff / archive access instructions, > >send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > >visit > >http://www.marist.edu/htbin/wlvindex?LINUX-390 > >-- > >For more information on Linux on System z, visit > >http://wiki.linuxvm.org/ > > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: systemd-analyze
Did you try ³systems-analyze critical-path²? If it would work, then it should show the longest path, which at this point, should be the one which is incomplete. -- Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure Services Mayo Clinic | 200 First Street SW | Rochester, MN 55905 507-284-0844 | nix.rob...@mayo.edu "quando omni flunkus moritati" On 10/27/16, 12:24 PM, "Linux on 390 Port on behalf of Michael MacIsaac" <LINUX-390@VM.MARIST.EDU on behalf of mike99...@gmail.com> wrote: >Thanks for the replies. > ># systemctl list-units --failed >0 loaded units listed. Pass --all to see loaded but inactive units, too. ># systemctl is-system-running >Unknown operation 'is-system-running'. > >With the systemctl status output sent to a file, I found a service >'waiting'. I stopped it, but still get: > ># systemd-analyze time >Bootup is not yet finished. Please try again later. > >I don't really need the output of 'systemd-analyze time' that badly. This >was more of a curiosity. > > -Mike > > >On Thu, Oct 27, 2016 at 12:13 PM, Dimitri John Ledkov <x...@ubuntu.com> >wrote: > >> On 27 October 2016 at 15:32, Michael MacIsaac <mike99...@gmail.com> >>wrote: >> > I heard about this new cool command and tried it, but it did not work: >> > >> > # systemd-analyze time >> > Bootup is not yet finished. Please try again later. >> > >> > How would I analyze systemd to know why 'bootup is not yet finished'? >> This >> > is SLES 12 SP1. >> > >> >> Generic / architecture independent systemd commands to try: >> >> $ systemctl list-units --failed >> >> Should show some culprits. >> >> Also look at full output of $ systemctl list-units >> >> and grep/look for things that are activating or waiting. Hopefully >> this should give you enough hints to figure out what components are >> not ready yet, to class system as started. >> >> Ideally, at the end of the boot you should be able to see that system >> is in running state: >> >> $ systemctl is-system-running >> running >> >> It is for me on machines that I maintain. Loads of things can make >> systemd believe things are degraded - e.g. when optional services are >> required or wanted by accident and similar. >> >> -- >> Regards, >> >> Dimitri. >> >> -- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> -- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ >> > >-- >For LINUX-390 subscribe / signoff / archive access instructions, >send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or >visit >http://www.marist.edu/htbin/wlvindex?LINUX-390 >-- >For more information on Linux on System z, visit >http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: systemd-analyze
Thanks for the replies. # systemctl list-units --failed 0 loaded units listed. Pass --all to see loaded but inactive units, too. # systemctl is-system-running Unknown operation 'is-system-running'. With the systemctl status output sent to a file, I found a service 'waiting'. I stopped it, but still get: # systemd-analyze time Bootup is not yet finished. Please try again later. I don't really need the output of 'systemd-analyze time' that badly. This was more of a curiosity. -Mike On Thu, Oct 27, 2016 at 12:13 PM, Dimitri John Ledkov <x...@ubuntu.com> wrote: > On 27 October 2016 at 15:32, Michael MacIsaac <mike99...@gmail.com> wrote: > > I heard about this new cool command and tried it, but it did not work: > > > > # systemd-analyze time > > Bootup is not yet finished. Please try again later. > > > > How would I analyze systemd to know why 'bootup is not yet finished'? > This > > is SLES 12 SP1. > > > > Generic / architecture independent systemd commands to try: > > $ systemctl list-units --failed > > Should show some culprits. > > Also look at full output of $ systemctl list-units > > and grep/look for things that are activating or waiting. Hopefully > this should give you enough hints to figure out what components are > not ready yet, to class system as started. > > Ideally, at the end of the boot you should be able to see that system > is in running state: > > $ systemctl is-system-running > running > > It is for me on machines that I maintain. Loads of things can make > systemd believe things are degraded - e.g. when optional services are > required or wanted by accident and similar. > > -- > Regards, > > Dimitri. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: systemd-analyze
On 27 October 2016 at 15:32, Michael MacIsaac <mike99...@gmail.com> wrote: > I heard about this new cool command and tried it, but it did not work: > > # systemd-analyze time > Bootup is not yet finished. Please try again later. > > How would I analyze systemd to know why 'bootup is not yet finished'? This > is SLES 12 SP1. > Generic / architecture independent systemd commands to try: $ systemctl list-units --failed Should show some culprits. Also look at full output of $ systemctl list-units and grep/look for things that are activating or waiting. Hopefully this should give you enough hints to figure out what components are not ready yet, to class system as started. Ideally, at the end of the boot you should be able to see that system is in running state: $ systemctl is-system-running running It is for me on machines that I maintain. Loads of things can make systemd believe things are degraded - e.g. when optional services are required or wanted by accident and similar. -- Regards, Dimitri. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: systemd-analyze
>>> On 10/27/2016 at 10:32 AM, Michael MacIsaac <mike99...@gmail.com> wrote: > How would I analyze systemd to know why 'bootup is not yet finished'? This > is SLES 12 SP1. It looks like systemd-analyze opens a socket to systemd and a bunch of "stuff" gets sent back and forth. An strace on systemd during this doesn't reveal any files being opened, so it appears the information needed is being kept in memory by systemd. I guess that you would need to start with "systemctl status" and go from there. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: systemd-analyze
Hi Mike I just tried that same command and it worked. Sent from my iPhone > On Oct 27, 2016, at 10:32 AM, Michael MacIsaac <mike99...@gmail.com> wrote: > > I heard about this new cool command and tried it, but it did not work: > > # systemd-analyze time > Bootup is not yet finished. Please try again later. > > How would I analyze systemd to know why 'bootup is not yet finished'? This > is SLES 12 SP1. > > Thanks. > >-Mike MacIsaac > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
systemd-analyze
I heard about this new cool command and tried it, but it did not work: # systemd-analyze time Bootup is not yet finished. Please try again later. How would I analyze systemd to know why 'bootup is not yet finished'? This is SLES 12 SP1. Thanks. -Mike MacIsaac -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
