Re: Many systemd units do not start anymore

[Max Nikulin <manikulin@gmail.com>]

On 05/02/2024 23:28, Christoph Pleger wrote:
> This is the output of systemctl list-jobs :
>
> JOB UNIT                                 TYPE  STATE
> 102 autofs.service                       start waiting
> 82  mlocate.timer                        start waiting
> 80  e2scrub_all.timer                    start waiting
> 117 cron.service                         start waiting
> 1   graphical.target                     start waiting
> 140 apache2.service                      start waiting

When timers are excluded, most services in the list depends on network. 
Is it configured? What services fail?

    systemctl --failed

Is there anything suspicious in output of

    journalctl --boot
    dmesg

Are there active processes in "top" output?

I am unsure if the following commands will provide anything useful in 
such state

    systemd-analyze blame
    systemd-analyze critical-chain

A wild shot... Is it a bare metal system or a virtualized host?

    hostnamectl
    cat /proc/sys/kernel/random/entropy_avail