This section is archived and will no longer be updated. For the latest articles about F-Secure products and services, go to the new and improved How-tos & FAQs.
We are in the process of adding a direct link from this page to its latest version in the new How-tos & FAQs section.
In the meantime, to find the latest version of this article, search for the article title in the searchbox on the left.
Services may not be automatically started when upgrading from F-Secure Internet Gatekeeper 5.xx to
When you upgrade F-Secure Internet Gatekeeper from version 5.xx to version 5.40, services may not be automatically started.
The following operating systems are affected: CentOS/RHEL 7, Debian 8, Ubuntu 16.04 and SLES 12.
Internet Gatekeeper 5.40 introduces native support for
systemd. In the previous releases, the services were managed by SysV-style init scripts.
Systemdattempts to provide backward compatibility with the SysV init scripts. While
systemdis aware of the product services, it may not be able to report the correct status when the services are started or stopped after a restart. This may cause that the enabled services are not automatically started when the product is upgraded.
There are two optional ways to solve the issue:
- Restart the machine. This allows
systemdto load the configuration and manage the services automatically according to the product configuration set in the Internet Gatekeeper Web UI.
- Start the services manually and refresh
systemdservice statuses. Login to the system and enter the following command as a root user:
# systemctl daemon-reload
Note: This command must be run outside the product installer directory (fsigk-5.40.73)!
Note: CentOS/RHEL 7.2 users and other platforms using
systemdversion 219-19.el7 or similar: Due to a change (see https://bugzilla.redhat.com/show_bug.cgi?id=1285492) how
systemdhandles SysV-style init scripts, the product services were not starting automatically at restart. If you have added a workaround, for example by replacing the init script symlinks in /etc/init.d/ by regular files, or by starting the services via /etc/rc.local, it should be removed after upgrading to product version 5.40.