{"id":4143,"date":"2026-06-08T18:00:55","date_gmt":"2026-06-08T15:00:55","guid":{"rendered":"https:\/\/support.withsecure.com\/en\/?post_type=support_article&#038;p=4143"},"modified":"2026-06-08T18:00:55","modified_gmt":"2026-06-08T15:00:55","slug":"policy-manager-fails-to-start-the-automatic-update-server-process-bwserver-due-to-an-issue-with-server-cfg-permissions","status":"publish","type":"support_article","link":"https:\/\/support.withsecure.com\/fr\/support-articles\/policy-manager-fails-to-start-the-automatic-update-server-process-bwserver-due-to-an-issue-with-server-cfg-permissions\/","title":{"rendered":"Policy Manager fails to start the Automatic Update Server process (bwserver) due to an issue with server.cfg permissions"},"content":{"rendered":"<h3>Issue:<\/h3>\n<p>By default, Linux distributions set a umask of 022.\u00a0However, if this is modified e.g. to harden the underlying system, it can cause a problem where the <b>Automatic Update Server <\/b>process (bwserver) fails to start. This is due to the process <b>bwserver <\/b>not being able to read its own config-file <b>\/etc\/opt\/f-secure\/fsaus\/conf\/server.cfg<\/b>.<\/p>\n<p>This will prevent legacy clients from downloading updates from the Policy Manager Server. Legacy clients include:<\/p>\n<ul>\n<li>Email and\u00a0Server Security version 12.x and older\u00a0<\/li>\n<li>Server Security 12.x and older<\/li>\n<li>Client Security versions older than 13.x.<\/li>\n<\/ul>\n<h3>Resolution:<\/h3>\n<p>The workaround is to manually set the permission for server.cfg after installation and restart the fspms daemon.<\/p>\n<p><b>As root\u00a0execute the following commands:<\/b><\/p>\n<pre>\n# chown fspms.fspms \/etc\/opt\/f-secure\/fsaus\/conf\/server.cfg\n# \/etc\/init.d\/fspms restart<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>By default, Linux distributions set a umask of 022.\u00a0However, if this is modified e.g. to harden the underlying system, it can cause a problem where the <b>Automatic Update Server <\/b>process (bwserver) fails to start. This is due to the process <b>bwserver <\/b>not being able to read its own config-file <b>\/etc\/opt\/f-secure\/fsaus\/conf\/server.cfg<\/b>.<\/p>\n<p>This will prevent legacy clients from downloading updates from the Policy Manager Server. Legacy clients include:<\/p>\n<ul>\n<li>\nEmail and\u00a0<\/p>\n","protected":false},"template":"","support_article_product":[106],"class_list":["post-4143","support_article","type-support_article","status-publish","hentry"],"acf":{"source_foreign_id":"000005638","source_version":3,"source_system":"salesforce","source_date_updated":"2026-06-08 15:00:55","import_hash":"9fca58ee0e8731eb9904fce5b5750e99fb290e2e","vanilla_article_id":32333,"vanilla_url":"https:\/\/community.withsecure.com\/en\/kb\/articles\/32333-policy-manager-fails-to-start-the-automatic-update-server-process-bwserver-due-to-an-issue-with-server-cfg-permissions","vanilla_kb_id":30,"vanilla_category_id":103,"machine_translated":false,"reactions_helpful_yes":0,"reactions_helpful_no":0},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article\/4143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article"}],"about":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/types\/support_article"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/media?parent=4143"}],"wp:term":[{"taxonomy":"support_article_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article_product?post=4143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}