Systemd error message in syslog "lacks a native systemd unit file."

Ask Fedora
, ,
1

Hi All

Found this errer in the system log:

[ 13.094988] systemd-sysv-generator[535]: SysV service ‘/etc/rc.d/init.d/livesys’ lacks a native systemd unit file. ~
Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in
order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !

This only appears on my upgraded server, not on my fresh install.

What can be done to resolve this?

Clive

1 Like
2

My guess is that /etc/rc.d/init.d/livesys is not required and is left over from the pre systemd world. I think you can delete it, but back it up first.

2 Likes
3

You can remove all these files and symlinks

/etc/rc.d/init.d/livesys
/etc/rc.d/init.d/livesys-late
/etc/rc.d/rc0.d/K01livesys-late
/etc/rc.d/rc0.d/K99livesys
/etc/rc.d/rc1.d/K01livesys-late
/etc/rc.d/rc1.d/K99livesys
/etc/rc.d/rc2.d/K01livesys-late
/etc/rc.d/rc2.d/K99livesys
/etc/rc.d/rc3.d/S00livesys
/etc/rc.d/rc3.d/S99livesys-late
/etc/rc.d/rc4.d/S00livesys
/etc/rc.d/rc4.d/S99livesys-late
/etc/rc.d/rc5.d/S00livesys
/etc/rc.d/rc5.d/S99livesys-late
/etc/rc.d/rc6.d/K01livesys-late
/etc/rc.d/rc6.d/K99livesys

They were used in older livesystem boot ISOs to do some special setup for the live system. After installing to the hard disk, you don’t need them, and they can safely be removed.

3 Likes
4

Thanks for the information, I have been upgrading this system since Fedora 31.

I will backup the system and then remove the files and see if it clears the error.

5

Upgrades often leave files that are no longer useful. When a new version of Fedora arrives I usually do a fresh install for testing on an external USB3 drive. In addition to helping ensure the update will run on my hardware, this gives me a way to boot if the main system does have a problem after upgrading, and also a way to check odd files/packages to see if they are used on a fresh install. By having a way to boot the configuration from a fresh install, you can rule out some problems that don’t appear with a fresh install and when you do have a problem, there is a good chances others will also experience the same issue – a solution is often already available by the time I encounter the issue.

1 Like
6

Thanks a lot for the information here, for the record I also had a broken K50netconsole -> ../init.d/netconsole in all of those which I just removed.

Dito for a broken symlink: /etc/rc.d/init.d/jexec -> /usr/java/latest/.java/init.d/jexec
Also removed the empty /usr/java while I’m at it. (Not sure where those came from, might have been rpmfusion or some other third party packages.)
The now mostly empty directories are owned by chkconfig and initscripts which I can’t remove because other packages depend on them.