Anti-Virus failed to start

Hello Robert Sasvari,

has the Talpa module successfully been compiled?
Not sure though if a failed build would prevent savd from starting, I think DouglasLeeder could give some advice on troubleshooting.

Christian

The installer wasn't able to start sav-protect/savd. That suggests it doesn't understand the init system.

If you have systemd then 

systemctl status sav-protect might give some information.

Otherwise tell me what init system MX Linux uses, and I might be able to advise.

Please, take a look at the response I sent to qc!

Thanks!

Please, take a look at the response I sent to qc!

Thanks!

So Talpa compiled fine, the problem is in starting sav-protect/savd as I said before.

OK. I tried to run what you mentioned (systemctl status sav-protect)

The response is the following:

Failed to get D-Bus connection: Unknown error -1

Please, keep in mind, that I'm not a Linux guru. Therefore if you need any additional info, I need to know what commands to run.

That sounds like your system isn't using systemd.

Lets try:

ps aux | head -2

pstree -ap | head -1

ls -l /sbin/init

Here we go:

ps aux | head -2
USER PID %CPU %MEM    VSZ    RSS  TTY  STAT  START   TIME  COMMAND
root       1     0.0      0.0  3028  1428  ?     Ss      15:28   0:01  init [5]

$ pstree -ap | head -1
init,1

$ ls -l /sbin/init
-rwxr-xr-x 1 root root 39396 apr 6 2015 /sbin/init

The wikipedia page suggests MX Linux has systemd installed, but is actually using sysV-init.

This is probably confusing SAV, so it won't be able to install properly. 

I'm afraid MX Linux isn't a distribution Sophos is going to start supporting, so I don't think there's any way to get it working for your system.

Sorry.

No problem Douglas.

I gave it a try and did not work out as expected. That's it.

Thanks anyway!

BTW: MX 17 is expected to be released soon. There could be changes to the favor of Sophos as well.)