You are seeing intermittent AMS Timeout No Response from a localhost alarm. You already performed resyncing, but it did not resolve the issue.
Timeout response from AMS is likely when AMS is "syncing" it's database with a replica node after a restart. Depending on the size of the DB, the sync process could take some time and during this period it is possible to get the error reported in the ticket. It does not necessarily indicate any issue.