Timed out: PatchAgent did not respond in the permitted time interval.
When deploying big patches that take a lot of time to install, like service packs, .NET Framework updates, new Internet Explorer releases, etc. it is possible to reach a timeout. This is a normal function of GFI LanGuard remediation jobs. The patch agent service sends back status messages for each patch deployed (starting, finished, result). After each message, the GFI LanGuard server resets a timeout timer. If the timer reaches the timeout interval configured or the deployment timeout has expired, it displays the Timed Out message and allows the deployment thread to be used by the next machine.
Another possible reason for the error above is failed communications. To verify whether this is the case, check whether an agent can communicate with the LanGuard server IP on port 1072, for example, using the Netstat utility or telnet. If the port isn't responding, the firewall or any security devices on the network need to be re-configured to allow TCP/IP traffic on port 1072 to the LanGuard server.
Ensure HTTP Communications Are Not Blocked
If the Diagnosis revealed communication blocks to server port 1072, review and ensure that necessary firewall exclusions are in place.
Increase the Deployment Timeout
If the Diagnosis confirmed that the firewall was allowing traffic on port 1072, increase the Deployment Timeout setting.
- Go to the GFI LanGuard Console and select Remediate.
- Choose the computers/groups to patch on the left pane and select the patch(es) desired to be sent.
- Click the Remediate... button.
- Select the Advanced Options hyperlink.
NOTE: You may also select the third listed Customize hyperlink, then click Advanced.
- Increment the value for Deployment Timeout then click OK.
- Click OK to run the Remediation job with selected patches and increased timeout.
Watch the remediation job progress and verify that the Timed Out error message is gone.
If the issue persists, increase the Timeout even more.