Skip to main content
Jason_ZA
Jason_ZA
Explorer
November 20, 2024
Question

Unable to sign installer package - invalid cross-device link

  • November 20, 2024
  • 2 replies
  • 1459 views

Hi,

 

I'm seriously at my wits end with issue after issue with the migration process to FortiClient EMS v7.4.x.

 

Besides all the other issues I experienced and managed to resolve myself (here), I now have a new one where I can't sign the Windows installer with the code signing certificate due to the following error.

 

failed to sign installer file /opt/forticlientems/data/clients/installers/default/Corporate_Laptop_v7.4.x/FortiClientSetup_7.4.1_x64.exe: fail to move signed file: rename /tmp/emssign191630999/FortiClientSetup_7.4.1_x64.exe /opt/forticlientems/data/clients/installers/default/Corporate_Laptop_v7.4.x/FortiClientSetup_7.4.1_x64.exe: invalid cross-device link

 

/opt and /tmp are on different mount points. We've tried mounting it (successfully) so that /tmp now sits on top of /opt/tmp (same partition) but it doesn't solve the problem.

 

Please help!

2 replies

Jason_ZA
Jason_ZAAuthor
Explorer
November 20, 2024

Okay, so a colleague and I managed to fix this one as well. The mount didn't work, as per above. What did work was overriding the TMPDIR variable in the fcems_installer service.

root@fems:/etc/systemd/system/fcems_installer.service.d# cat override.conf
[Service]
Environment="TMPDIR=/opt/tmp"

romitvo1
romitvo1
New Member
November 20, 2024

This happens when you are moving files across different mount points on the server and the FTP service is trying to swap links rather than copy the data across the mount points. Typically when you move a file in Linux it does not move the file, but rather the link to the file. If it's on a different mount point it needs to actually copy the data and not just move the file link, but the FTP service isn't aware they are different mount points https://mobdro.bio/ .

    Terms & ConditionsAccessibility statement