FortiClient Migration from 7.2.9 to 7.4.3 failed

[PaoloZangheri]

During a migration from FortiClient EMS 7.4.9 (windows) to FortiCLient EMS 7.4.3 (Linux) the migration.exe program signaled a failed migration, with the last lines log the log stating:

2025-04-11 13:27:38,091 Exception type : Traceback (most recent call last):
File "main.py", line 66, in main
File "lib\ems_client_lib.py", line 101, in copy_cert_files
File "lib\ems_client_lib.py", line 62, in copy_files
File "lib\helper\scphelper.py", line 50, in copy
File "lib\helper\scphelper.py", line 33, in ExecCmd
Exception: ExecCmd: echo 'xxxx-omitted-xxx' | sudo -S chown -R forticlientems.forticlientems "/opt/forticlientems/data/certs", Error: [sudo] password for test: chown: warning: '.' should be ':': ‘forticlientems.forticlientems’

2025-04-11 13:27:38,094 [chan 1] EOF sent (1)
2025-04-11 13:27:38,095 EOF in transport thread
2025-04-11 13:27:38,097 EOF in transport thread
2025-04-11 13:27:38,097 EOF in transport thread
2025-04-11 13:27:38,098 EOF in transport thread

It appears that the executable contains a syntax error in the chown command.

I've manually changed the ownership of the certificate that was copied from the Windows machine to Linux. The FortiClient EMS platform on the new machine appears healthy, but I don't know if the migration procedure has been completed or if the error has aborted some other part of the migration.

Thanks

[Jean-Philippe_P]

Hello PaoloZangheri, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Thanks, 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Thanks,

[PaoloZangheri]

Thanks

[Jean-Philippe_P]

Hello again Paolo,

I found this solution, can you tell me if it helped you, please?

The error message indicates a syntax issue with the 'chown' command during the migration process. The warning suggests using a colon ':' instead of a period '.' in the command for specifying the user and group. Since you've manually corrected the ownership of the certificate files, the immediate issue seems resolved. However, to ensure the migration process is fully completed, follow these steps:

1. Verify Migration Logs: Check the migration logs for any additional errors or warnings that might indicate incomplete tasks. Look for any steps that were not executed after the error occurred.
   
   
2. Check EMS Functionality: Verify that all EMS services are running correctly on the new Linux machine. Test key functionalities to ensure they operate as expected.
   
   
3. Review Configuration: Ensure that all configurations, settings, and data have been successfully migrated. Compare with the original setup on the Windows machine.
   
   
4. Re-run Migration Tool: If possible, re-run the migration tool to see if it completes without errors. This can help confirm that all steps are executed properly.
   
   
5. Backup and Restore: If issues persist, consider restoring from a backup taken before the migration and attempt the migration again, ensuring all prerequisites and steps are followed.

If the EMS platform appears healthy and all functionalities are working as expected, the migration might have completed successfully despite the error. However, thorough verification is recommended to ensure no critical components were missed.