Upgrade from 15.6 to 16 headless wants to start plymouth

I have a Leap 15.6 headless server running at Linode.com. I tried to upgrade it to 16.0, but after the upgrade, it wants to start plymouth. It is not installed and not required. There is no plymouth services set up.
I added the plymouth.enable=0 to the boot command, but it still insists on starting it.
The boot goes to rescue mode and the last journal message is:
Subject: Process plymouth could not be executed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The process plymouth could not be executed and failed.
░░
░░ The error number returned by this process is 2.

If I run init3 then it finish the startup and the server is fine.
So my current solution is to create a plymouth script /usr/bin/plymouth the just run init3:

#!/bin/bash
init 3

Now the server start normal.
But what will make it try to start plymouth if it is a headless setup with nothing plymouth installed?

Thanks
Andre Truter

@andretr Hi, if you have removed the libply* and ply* files, you must rebuild the kernel image to remove the plymouth modules dracut -f --regenerate-all.

Likewise, init is deprecated, if wanting to start with just a console session systemctl set-default multi-user.target

@malcolmlewis Hi, the weird thing is that no libply* or ply* packages are installed or have ever been installed. I have no idea where it gets the idea to start plymouth.
The only package that contains ply in the name is python packages:

rpm -qa | grep ply
python311-ply-3.11-150400.12.6.1.noarch
python3-ply-3.10-150000.3.5.1.noarch
python2-ply-3.10-1.27.noarch

But according to the package info it has nothing to do with plymouth.

I did rebuild the kernel image, but it did not make a difference.

The reason I use init 3 is because systemctl set-default multi-user.target does not allow the boot process to continue, it just sets the boot target, but does not get the system past the rescue mode.

But, I ran systemctl set-default multi-user.target now in rescue mode and rebooted and this time it booted normally. So it seems that setting the boot target solved the problem.

Thanks

I guess he meant to say systemctl isolate multi-user.target

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.