Updating F-Secure Policy Manager from 15.11 to 15.20 results in fspms.service failing to start.

juru

Hello,

We run F-Secure Policy Manager 15.11 on Ubuntu 20.04.2 LTS. We updated to version 15.20 but now the fspms.service fails to start. We see the following error message in journalctl:

mai 17 16:36:33 server1 fspms[3981]: * Starting F-Secure Policy Manager Server
mai 17 16:36:33 server1 su[4909]: (to fspms) root on none
mai 17 16:36:33 server1 su[4909]: pam_unix(su:session): session opened for user fspms by (uid=0)
mai 17 16:36:34 server1 fspms[4924]: sh: 1: eval: Syntax error: "(" unexpected
mai 17 16:36:34 server1 su[4909]: pam_unix(su:session): session closed for user fspms
mai 17 16:36:39 server1 fspms[3981]: .....  ...fail!
mai 17 16:36:39 server1 systemd[1]: fspms.service: Control process exited, code=exited, status=1/FAILURE
mai 17 16:36:39 server1 systemd[1]: fspms.service: Failed with result 'exit-code'.
mai 17 16:36:39 server1 systemd[1]: Failed to start LSB: F-Secure Policy Manager Server.

Any pointers what might have gone wrong?

A_Grinkevitch

Hello,

New version 15.20.95101 has been published to the downloads page: https://www.f-secure.com/en/business/downloads/policy-manager-for-linux

Please use it for the upgrade. It is binary the same as the previous one, but rebuilt with the proper building system configuration.

ITService_LH

Same issue on Debian 10.9

Log:

####################

/etc/init.d/fspms start

[....] Starting fspms (via systemctl): fspms.serviceJob for fspms.service failed because the control process exited with error code.

See "systemctl status fspms.service" and "journalctl -xe" for details.

failed!

root@FsecureServer:~# journalctl -xe

May 18 08:48:41 FsecureServer systemd[1]: user@999.service: Succeeded.

-- Subject: Unit succeeded

-- Defined-By: systemd

-- Support: https://www.debian.org/support

############################

A_Grinkevitch

Hello,

Reason has been identified: recent changes made to our building system have caused incorrect AUS service start configuration. Relevant improvements have been made to our test automation to avoid such issues in the future.

We are going to publish the new PM 15.20 Linux package fixing this problem in the next few days.

Sorry for the inconvenience...

juru

Thank you, the new version solved the issue.