• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Kaspersky broken after update

janl

New Pleskian
This is a fork of this Thread as this seems to be a different problem then originally expected.

Since the last update, Kaspersky is not running any more and can't be started again:

plesk fail 1.png

console: /etc/init.d/kavehost start -> FAILED

This expectedly leads to these effects in maillog:
Apr 29 09:31:53 XXX kav-handler[30472]: Initializing: unknown error 0x80040000, please check that kavehost is running
Apr 29 09:31:53 XXX /usr/lib64/plesk-9.0/psa-pc-remote[725]: _mh_fork(): unrecognized status code '81'
Apr 29 09:31:53 XXX /usr/lib64/plesk-9.0/psa-pc-remote[725]: Error during 'kav-snd' handler

As well as:
Apr 29 13:44:24 XXX kav-handler[19093]: Initializing: unknown error 0x80040000, please check that kavehost is running
Apr 29 13:44:24 XXX /usr/lib64/plesk-9.0/psa-pc-remote[725]: _mh_fork(): unrecognized status code '81'
Apr 29 13:44:24 XXX /usr/lib64/plesk-9.0/psa-pc-remote[725]: Error during 'kav-rcpt' handler


Also this happens:

[root@XXX ~]# /opt/kav/sdk8l3/bin/kav8update
Loading engine...
Current product version: 8.0.1.25
Initializing engine...
Using xml-file: /opt/kav/sdk8l3/bin/settings.xml.
Can't initialize engine. Error code: 0x8004025c


The system is a virtual CentOS.


Can anyone shed a light on this one?

Thanks,
Jan
 
Coming back to this issue here:

KAV is still not running and all Attempts to start the service fail even though the license allows for KAV use.

Please, is there anyone having an idea?
If not I think I will cancel my KAV-license as it is apparently useless.
 
Looks like there is wrong permissions on /var/run/kav directory:

# chown -R root:root /var/run/kav
# chmod 0755 /var/run/kav
# /etc/init.d/kavehost restart
 
Hi igor,

thanks for your help.

But that's not it...

[root@XXX ~]# ls -la /var/run/kav/
total 12
drwxr-xr-x 2 root root 4096 May 7 11:27 .
drwxr-xr-x 28 root root 4096 May 1 07:47 ..
-rw-r--r-- 1 root root 5 May 7 11:26 pid
[root@XXX ~]# chown -R root:root /var/run/kav
[root@XXX ~]# chmod 0755 /var/run/kav
[root@XXX ~]# ls -la /var/run/kav/
total 12
drwxr-xr-x 2 root root 4096 May 7 11:27 .
drwxr-xr-x 28 root root 4096 May 1 07:47 ..
-rw-r--r-- 1 root root 5 May 7 11:26 pid
[root@XXX ~]# /etc/init.d/kavehost restart
Stopping kavehost: kavehost is not running. [FAILED]
Starting kavehost: [FAILED]


Strange is that it takes about 1 minute until the "Failed" appears after the start command... It tries starting pretty long... is there something that might cause a timeout?

EDIT: oh, there's a PID file. Strange. Deleted it.

Funny: Another restart results in FAILED again but produces a new pid-file.

Strange: how can it start and produce a PID, but not be running?!

[root@XXX ~]# cat /var/run/kav/pid
11309
[root@XXX ~]# ps -aux | grep 11309
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
root 11566 0.0 0.0 103240 852 pts/1 S+ 15:41 0:00 grep 11309

...and nothing more.
Nothing.
 
Last edited:
I was struggling with this issue also on new Plesk Onyx 17. Even complete reinstallation of Kaspersky did not change anything. Apparently "error 0x80040000" is error, which simply indicates corrupted system files. I believe in our case something went wrong with definition update.

In any case - what solved my issue was:
1) Uninstalling Kaspersky (and to be sure, also SpamAssasin) from within Plesk
2) Remove the garbage left: rm -Rf /opt/kav /run/kav
3) Install them fresh again

I believe this issue is cause by some incorrect update of virus database or something like that. If it was a Kaspersky update, then some file might not be properly updated. In any case - the above has solved the issue for me.
 
Thanks a lot for this article! I've tried many things yesterday to fix it and that includes retrieving the license for several times (before/after renabling/einstallation of Kaspersky). In any case it's very easy resolution and I hope it'll help many others.
 
Back
Top