|
During the installation of FortiClient EMS, a component called pgagent is downloaded from the PostgreSQL official repository, which Fortinet does not control the content of. On January 13, 2025, this component was updated. FortiClient EMS 7.4.0 has a strict version restriction on pgagent and if different than what the installation is expecting, the install fails.
Fortinet has re-packaged FortiClient EMS 7.4.1 to remove the strict version dependency. Customers considering a new installation or an upgrade to FortiClient EMS 7.4.1 must use .bin files dated January 14, 2025 on the download portal.
In some cases, the only available recovery option is an EMS DB backup from EMS version 7.4.0 and since EMS db backup-restore is version sensitive, installation of EMS 7.4.0 is inevitable. Currently, a repackaged installer for EMS 7.4.0 is not available. The following method can be used to install EMS 7.4.0 after January 2025 if an EMS 7.4.0 DB is to be restored and then upgraded to EMS 7.4.1.
- sudo -s
- wget http://ftp.debian.org/debian/pool/main/p/pgagent/pgagent_4.2.2-2_amd64.deb
- apt install ./pgagent_4.2.2-2_amd64.deb
- apt-mark hold pgagent
- ./forticlientems_7.4.0.1793.bin -- --allowed_hosts '*' --enable-remote-https
- Perform a DB restore on the installed EMS 7.4.0.
- Take a VM snapshot.
- apt-mark unhold pgagent
- ./forticlientems_7.4.1.1872.amd64.bin -- --allowed_hosts '*' --enable_remote_https
- Take a VM snapshot.
The forticlientems_7.4.1.1872.amd64.bin should be the new file (upload date 14-Jan-2025) available for download from support.fortinet.com.
The following error messages may be shown by the EMS 7.4 installer regarding the pgagent dependency:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
forticlientems : Depends: pgagent (< 4.2.3) but 4.2.3-1.pgdg22.04+1 is to be installed
E: Unable to correct problems, you have held broken packages.
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
forticlientems : Depends: pgagent (>= 4.2.2) but 4.2.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.
According to the logs, Forticlientems depends on pgagent (>= 4.2.2) and pgagent (< 4.2.3). The only possible matching version is 4.2.2.x which have been used in step 1 above for manual pgagent installation. The root cause of this issue, as previously explained, is the removal of this package from PostgreSQL repositories. The pgagent_4.2.2-2_amd64.deb used in this guide is downloaded from official Debian ftp mirror and can be considered a safe and trusted source.
pgagent_4.2.2-2_amd64.deb file checksum hash:
SHA256: 9E164ADB7F6385C4F31137BF7EF4E62527429098DB0D22405470FE044D398E16
MD5: BD922D5EA27E338E9411881FCE2422B9
|
