CentOS - Sep 2020 - Server entering Emergency Shell, but continues fine after pressing Enter

On 9/11/20 4:51 PM, Quinn Comendant wrote:
> Does anyone know what initrd-parse-etc.service does? Or have suggestions
how to troubleshoot that unit specifically?

Run "systemctl daemon-reload && echo success" and verify that
it reports
success, and not errors.

Check the output of "systemctl status initrd-cleanup" too.

On 11 Sep 2020 17:23:00, Gordon Messmer wrote:
> Run "systemctl daemon-reload && echo success" and verify
that it
> reports success, and not errors.
> 
> Check the output of "systemctl status initrd-cleanup" too.
Those have always reported success (even before I removed the OnFailure option):


[~] sudo systemctl daemon-reload && echo success
success
[~] sudo systemctl status initrd-cleanup
? initrd-cleanup.service - Cleaning Up and Shutting Down Daemons
   Loaded: loaded (/usr/lib/systemd/system/initrd-cleanup.service; static;
vendor preset: disabled)
   Active: inactive (dead)

Sep 11 23:34:01 durian systemd[1]: Starting Cleaning Up and Shutting Down
Daemons...
Sep 11 23:34:01 durian systemd[1]: Stopped Cleaning Up and Shutting Down
Daemons.

> On 11 Sep 2020 17:23:00, Gordon Messmer wrote:
>> Run "systemctl daemon-reload && echo success" and
verify that it
>> reports success, and not errors.
>>
>> Check the output of "systemctl status initrd-cleanup" too.
>
> Those have always reported success (even before I removed the OnFailure
> option):
>
>
> [~] sudo systemctl daemon-reload && echo success
> success
> [~] sudo systemctl status initrd-cleanup
> ? initrd-cleanup.service - Cleaning Up and Shutting Down Daemons
>    Loaded: loaded (/usr/lib/systemd/system/initrd-cleanup.service; static;
> vendor preset: disabled)
>    Active: inactive (dead)
>
> Sep 11 23:34:01 durian systemd[1]: Starting Cleaning Up and Shutting Down
> Daemons...
> Sep 11 23:34:01 durian systemd[1]: Stopped Cleaning Up and Shutting Down
> Daemons.
Hi,

I'm wondering what the proper solution is in this case. One thing I
learned in the past and can also be learned from the list archives is that
a lot of issues exist with systemd but almost never one really finds a
good solution to fix the problem.

In most cases ugly hacks and workarounds are used but no real fix is
available. IMHO it's in no way better than old days SysVinit hacking :-)

Regards,
Simon

On 9/11/20 5:29 PM, Quinn Comendant wrote:
> Those have always reported success (even before I removed the OnFailure
option):

In that case, I'd revert the change you made, unlock the root account so 
that you can use the emergency shell, let the system boot to an 
emergency shell, and collect the output of "systemctl status 
initrd-parse-etc.service" and "journalctl -b 0".

(You can still do that in the VM, right?)