There are several reasons why this heartbeat error occurs. Below are some possible causes and their respective solutions:
Scenario 1. Error is caused by refused connection
The following description appears:
Level: Warning Event ID: 4011 Event: Failure to Contact Manager Description: Unable to contact Deep Security Manager at URL=dsm://dsmip:4120/ with IP=10.50.100.232 due to the following error: Connection refused
In such situation, Deep Security Agent (DSA) proactively rejects DSM's heartbeat. Do the procedure below to resolve the issue:
- Double-check the following configuration:
- DSA should still be managed by this DSM.
- There should be no permission issue in the local DSA.
- Port 4118 (for DSA) and port 4120 (for DSM) should be open.
- Reset and reactivate the DSA.
Scenario 2. Error is caused by connection timeout
The following description appears:
Level: Warning Event ID: 4011 Event: Failure to Contact Manager Description: Unable to contact Deep Security Manager at URL=dsm://dsmip:4120/ with IP=10.50.100.232 due to the following error: Connection Time Out
In this scenario, DSM sent a heartbeat request, but failed to receive a reply within the alloted time.
To resolve the issue:
- Make sure the network connectivity is working fine.
- Re-try sending a heartbeat.