Error while upgrading Forticlient EMS to 7.4.8

hi,

the key line seems to be this one:

cp: cannot stat '/tmp/ems/info/ems.*': no such file or directory

so i would first focus on the /tmp path and available disk space, rather than the generic dpkg error.

it looks like the installer expected some ems files under /tmp/ems/info/, but they were not there when the post-install script tried to continue.

i would check:

df -h /tmp
df -h /opt
df -h /

fortinet also recommends running the ems installer from a directory other than /tmp, and making sure /tmp has enough free space during the upgrade.

docs:
https://docs.fortinet.com/document/forticlient/7.4.7/ems-administration-guide/880046/upgrading-from-an-earlier-forticlient-ems-version

troubleshooting article:
https://community.fortinet.com/forticlient-4/troubleshooting-tip-how-to-identify-forticlient-ems-upgrade-fails-due-to-the-tmp-folder-not-having-enough-free-disk-space-223859

i would take a vm snapshot or backup first, then copy the installer to another folder, for example /home/”user”/, make it executable again and rerun it from there.

if the package is now left in a half-configured state, after fixing the /tmp space/path issue you can try:

sudo dpkg --configure -a

or rerun the ems installer again from the new location.

if it still fails, the next useful thing would be to review the full install log, because the current error only shows that the expected ems files under /tmp were missing.

ERROR: insert or update on table "client_events_summary" violates foreign key constraint "fk_client_events_summary_machine_user_id"

It seems like a psql error.

thanks, this looks much more like a database consistency issue.

i found a similar ems upgrade case where the installation failed because of a postgresql foreign key constraint. in that case, the root cause was orphaned references in the database and the upgrade completed after the invalid references were repaired.

https://community.fortinet.com/support-forum-92/ems-7-4-4-upgrade-failed-due-to-fk-software-software-icons-constraint-fixed-by-manual-db-repair-216005

your constraint is different (fk_client_events_summary_machine_user_id), so i would not apply the same sql commands directly, but it looks like a very similar type of database consistency problem.

i would collect the full detail: line from postgresql and open a tac case before modifying the ems database manually.

Same issue here (EMS 7.4.7.2194 → 7.4.8.2245, Linux VM appliance).

TAC provided hotfix forticlientems_7.4.7_hotfix_package_mantis_1325735_amd64.zip. I applied it (execute hotfix --list shows Status: applied), then ran the upgrade again. The hotfix did clear the original orphaned record (67, 9), but the same migration now fails on a different key:

psql:../sqitch/vdom/deploy/changes/7408/mantis_1244773_retain_event_counts.sql:51: ERROR: insert or update on table "client_events_summary" violates foreign key constraint "fk_client_events_summary_machine_user_id"
DETAIL: Key (machine_user_id, vdom_id)=(7, 30) is not present in table "users".

So hotfix 1325735 doesn't seem to cover all orphaned records. @vpolovnikov, is there an updated hotfix or a known way to identify all affected records before upgrading? I'm opening a new TAC case as well.