Infscape Appliance for Raspberry Pi 4: SysV service "..." lacks a native systemd unit file

Hi there,
I work with the most recent appliance, kernel 5.10.60-20210825-ge4cb65cf23c7-p4-bis .
On booting the appliance I receive 3 messages:

  • SysV service /etc/init.d/urbackupsrv lacks a native systemd unit file …
  • SysV service /etc/init.d/exim4 lacks a native systemd unit file …
  • SysV service /etc/init.d/shellinabox lacks a native systemd unit file …

All messages end with advice to build a native systemd unit in order to make it more safe and robust.

When I look at the UrBackup service after startup of the appliance:
service urbackupsrv status
● urbackupsrv.service - LSB: Server for doing backups
Loaded: loaded (/etc/init.d/urbackupsrv; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
But the UrbackUp server is happily working!

However, if I issue
service urbackupsrv status
● urbackupsrv.service - LSB: Server for doing backups
Loaded: loaded (/etc/init.d/urbackupsrv; generated)
Active: active (exited) since Mon 2021-09-13 13:31:08 CEST; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 15532 ExecStart=/etc/init.d/urbackupsrv start (code=exited, status=0/SUCCESS)
CPU: 804ms

Sep 13 13:31:08 ubr1 systemd[1]: Starting LSB: Server for doing backups…
Sep 13 13:31:08 ubr1 urbackupsrv[15537]: ERROR: ld.so: object ‘/usr/lib/x86_64-linux-gnu/libjemalloc.so.1’ from LD_PRELOAD cannot be preloa
Sep 13 13:31:08 ubr1 systemd[1]: Started LSB: Server for doing backups

Now, the UrbackUp server is also working and corrctly detected by the status request. However, it yields now “ERROR: ld.so: object ‘/usr/lib/x86_64-linux-gnu/libjemalloc.so.1’ from LD_PRELOAD cannot be preloa”

Please advice on how to correct this. Thanks in advance.