Product Troubleshooting WithSecure Business Suite

Warning message of "This installer version is going to be obsoleted at the end of year 2024" during the installation of Linux Security 64
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Where can I find the key code for the latest version of my Business Suite software?
Error: "The keycode that you entered is not valid" when trying to export an installation package for Client Security or Server Security
"capricorn-linux64" channel are added in product's database after Linux Security 64 update version 12.0.482 and Atlant update version 1.0.319
How to schedule Business Suite Software Updater to install updates automatically to Client Security and Server Security devices?
f-secure-baseguard services gone for Linux Security 64 and Atlant after FSBG 1.0.907 update
How to hide the real-time scanning exclusions or other exclusions from users in the local Client Security or Server Security user interface?
WithSecure Client Security or Server Security Web content control is not blocking categories that are set as "Disallowed"

Policy Manager fails to start the Automatic Update Server process (bwserver) due to an issue with server.cfg permissions

Issue:

By default, Linux distributions set a umask of 022. However, if this is modified e.g. to harden the underlying system, it can cause a problem where the Automatic Update Server process (bwserver) fails to start. This is due to the process bwserver not being able to read its own config-file /etc/opt/f-secure/fsaus/conf/server.cfg.

This will prevent legacy clients from downloading updates from the Policy Manager Server. Legacy clients include:

Email and Server Security version 12.x and older
Server Security 12.x and older
Client Security versions older than 13.x.

Resolution:

The workaround is to manually set the permission for server.cfg after installation and restart the fspms daemon.

As root execute the following commands:


# chown fspms.fspms /etc/opt/f-secure/fsaus/conf/server.cfg
# /etc/init.d/fspms restart

Article no: 000018505