To upgrade Kaspersky Scan Engine 2.0 and later manually:
/etc/init.d/kavicapd stop
/etc/init.d/kavhttpd stop
/etc/init.d/klScanEngineUI stop
service kavicapd stop
service kavhttpd stop
service klScanEngineUI stop
/opt/kaspersky/ScanEngine/etc/klScanEngineUI.xml/opt/kaspersky/ScanEngine/etc/kavicapd.xml/opt/kaspersky/ScanEngine/icap_data, if you configured ICAP rules in kavicapd_gui_rules.conf/opt/kaspersky/ScanEngine/etc/kavhttpd.xmlTlsCertificateKeyFile and TlsCertificateFile elements of the kavhttpd.xml configuration file.You can find information on the location of the certificate and private key in the SSLCertificatePath and SSLPrivateKeyPath elements of the klScanEngineUI.xml file.
You can find information on the location of the key file or activation code in the LicensePath element of the kavhttpd.xml configuration file (if Kaspersky Scan Engine worked in HTTP mode) or kavicapd.xml configuration file (if Kaspersky Scan Engine worked in ICAP mode).
/opt/kaspersky/ScanEngine directory, uninstall Kaspersky Scan Engine with uninstall.If you used the Kaspersky Scan Engine GUI and you want to continue using the kavebase database created earlier in PostgreSQL, you do not need to submit the deletion of data from this database. However, you need to upgrade the database with the following command:
psql -d kavebase -a -f %tempdir%/samples/migrate.sql
The above command imports the contents of %tempdir%/samples/migrate.sql.
%tempdir% in this command is the directory that contains the unpacked Kaspersky Scan Engine distribution kit contents.
Make sure that the user running the database queries has access to the directory containing migrate.sql and also has read access to migrate.sql itself.
Do not use migrate.sql to upgrade the database used by Kaspersky Scan Engine version below 2.0.
You also need to specify the same username and password as used to connect to the previous version of the database. You can specify the username and password later, during the installation of Kaspersky Scan Engine.
If you forgot the username or password, use the psql utility.
/opt/kaspersky/ScanEngine/ or delete this directory.service kavicapd stop
service kavhttpd stop
service klScanEngineUI stop
klScanEngineUI.xml to /opt/kaspersky/ScanEngine/etc/kavicapd.xml to /opt/kaspersky/ScanEngine/etc/icap_data to /opt/kaspersky/ScanEngine/icap_data, if you configured ICAP rules in kavicapd_gui_rules.conf kavhttpd.xml to /opt/kaspersky/ScanEngine/etc/TlsCertificateKeyFile and TlsCertificateFile elements of the kavhttpd.xml configuration file.Make sure that only users with administrator rights have read access to the certificate and the private key.
SSLCertificatePath and SSLPrivateKeyPath elements of the klScanEngineUI.xml file, respectively.Make sure that only users with administrator rights have read access to the certificate and the private key.
You can find information on the location of the key file or activation code in the LicensePath element of the kavhttpd.xml configuration file (if Kaspersky Scan Engine worked in HTTP mode) or kavicapd.xml configuration file (if Kaspersky Scan Engine worked in ICAP mode).
service kavicapd startservice kavhttpd startservice klScanEngineUI startIf you decided to use the same kavebase database when installing the new version of Kaspersky Scan Engine, the password you specified in the previous version for Kaspersky Scan Engine GUI administrator remains valid, it is not reset to the default password.