Assist runs on MX Linux and survives restart but install error is confusing

Hello,

Unattended Access is running well on my MX Linux although it is bit laggy.
It survives a restart, so autostart seems to work.

What confuses me is that I get the following error (this time from reinstall)

Reloading configuration files for periodic command scheduler: cron.
Failed to get unit file state for crond.service: No such file or directory
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
installing systemV service
ln: failed to create symbolic link '/usr/bin/ZohoAssistURS': File exists
ln: failed to create symbolic link '/etc/init.d/ZohoAssistUrs': File exists
Failed to enable unit, unit ZohoAssistUrs.service does not exist.

Can you tell me how to deal with it.

thx

Stefan

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Topic Participants
stefan.mueller
Ayman Khan

Sticky Posts
Release Notes: Version 1.91, February 2015
Unattended Access (Beta) is live! Unattended Access, a feature requested by a lot of our customers is live now. Currently, it's in beta. You can add up to 100 computers per Technician subscription. They can also be accessed by your organization members. My Computers list in Zoho Assist home page will always display the online status of your unattended computers. You can rename the computers whenever you wish. Currently, Unattended Access can be configured only for Windows computers. Nevertheless,