Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Services may not be automatically started when upgrading from F-Secure Internet Gatekeeper 5.xx to 5.40 - F-Secure Community
<main> <article class="userContent"> <p> </p>Services may not be automatically started when upgrading from F-Secure Internet Gatekeeper 5.xx to 5.40 <h3>Symptoms</h3> <p>When you upgrade F-Secure Internet Gatekeeper from version 5.xx to version 5.40, services may not be automatically started. </p> <h3>Diagnosis</h3> <p>The following operating systems are affected: CentOS/RHEL 7, Debian 8, Ubuntu 16.04 and SLES 12. </p> <p> Internet Gatekeeper 5.40 introduces native support for </p><pre class="code codeBlock" spellcheck="false">systemd</pre>. In the previous releases, the services were managed by SysV-style init scripts. <p></p><pre class="code codeBlock" spellcheck="false">Systemd</pre> attempts to provide backward compatibility with the SysV init scripts. While <pre class="code codeBlock" spellcheck="false">systemd</pre> is 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. <h3>Solution</h3> <p>There are two optional ways to solve the issue: </p> <ul><li>Restart the machine. This allows <pre class="code codeBlock" spellcheck="false">systemd</pre> to load the configuration and manage the services automatically according to the product configuration set in the Internet Gatekeeper Web UI. </li> <li>Start the services manually and refresh <pre class="code codeBlock" spellcheck="false">systemd</pre> service statuses. Login to the system and enter the following command as a root user: <ul><li><pre class="code codeBlock" spellcheck="false"># systemctl daemon-reload</pre> </li> <li><pre class="code codeBlock" spellcheck="false"># /opt/f-secure/fsigk/libexec/fsigk-reload.sh</pre> <strong>Note:</strong> This command must be run outside the product installer directory (fsigk-5.40.73)! </li> </ul></li> </ul><p><strong>Note:</strong> CentOS/RHEL 7.2 users and other platforms using </p><pre class="code codeBlock" spellcheck="false">systemd</pre> version 219-19.el7 or similar: Due to a change (see <a rel="nofollow" href="https://bugzilla.redhat.com/show_bug.cgi?id=1285492">https://bugzilla.redhat.com/show_bug.cgi?id=1285492</a>) how <pre class="code codeBlock" spellcheck="false">systemd</pre> handles 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. <br> </article> </main>