EMS 7.4.4 Web Server 500 Error after migration

These updates are Linux related. I didn't use the virtual appliance version yet, so I don't know how to manage Lunix updates in this new version. Before it was possible because Linux shell was directly accessible.

Hope some more experienced member can help.

I reran the migration and can now access the console.

The only things I've changed this time are entering static IP addresses and configuring the timezone for the migration.

Later, I noticed in the DHCP leases that the Linux EMS server, during the previous migration, initially received a different IP address.

After a reboot, it received a different IP address again.

This could maybe have caused the web access issues.

Anyway, in the console output, I saw percentages and verifications that didn't show 100%.

I also had this during the first migration test
I don't know if this still requires further attention.

See link for migration log file

https://filebin.net/4yvvgrobkgkublaq

See link for "all log files"
https://filebin.net/y2qgdmgd0zsikuzv

If applicable, I'd appreciate recommendations.

If not, I'll close this post after a few days.

I'll now review the configuration and start testing the client migration.

So, you won't be rid of me anytime soon :)

Happy to hear that the migration worked this time.

I can't comment the failure messages on the output, nevertheless since we can see "EMS Migration Successfully completed" and since there is no fatal error then for me I'd consider it done successfully.

If you want to be sure for your production, you can still open a ticket with these messages to get feedback from Fortinet TAC.

For production, I want to be sure I don't run into any vague issues.
I've created a ticket.
I'll let you know when they respond.

I ran into the same issue after upgrading FortiClientEMS from 7.4.3 to 7.4.4. The web interface now shows a 500 Internal Server Error.

Looking at the logs, I frequently see this error:

ERROR manager/socket_pool.go:212 Failed to create new socket connection: dial tcp 127.0.0.1:65432: connect: connection refused

Has anyone else encountered this after the 7.4.4 upgrade? Any ideas on how to fix it?

I just checked my logs, but besides numerous other errors, I still see the same socket errors in various logs.
Despite the errors, I can now access the console after my second migration test.
So I would check for other errors.
I think the default port should be 5432.

I have a ticket open with support regarding the numerous errors in various logs.
The only response so far has been to adjust the resources in my VM.
https://docs.fortinet.com/document/forticlient/7.4.3/ems-administration-guide/358374/system-requirements

I'm currently not having any issues with version 7.4.4, but this is a test environment with two endpoints.
I want to make sure the errors in the logs don't cause any vague issues in the near future when I start migrating to production.

Hi guys, I encounter the same issue but a fresh new install < 1 week.

I gave more info here: https://www.reddit.com/r/fortinet/comments/1rg3my9/ubuntu_et_forticlient_ems_745_error_500_connction/

Did you solve it by any chance ?

Thanks for your help !