Modules update failed EES 7.1

[bbahes 29]

Hi!

Deploying EES 7.1 further to new clients. On latest we have problem:

Agent is connecting to ESMC:

 

 

[bbahes 29]

I don't know does this matter, but I've logged in as administrator on client PC and started module update manually:

Edited May 6, 2019 by bbahes

[Marcos 5,070]

There's basically no difference between automatic and manually triggered update. Should the problem persist:
- enable advanced update engine and network protection logging
- reproduce the update error
- disable logging
- gather logs with ELC.

[MartinK 378]

Please check also state of HTTP proxy is product is configured to use some for updates. There is a chance it is not working correctly.

[bbahes 29]

This was only on one new client. After I logged in as Administrator it downloaded module updates correctly.

Proxy policy is same for all clients in company. All others working fine.

[bbahes 29]

This is what I see in /var/log/httpd/error_log file:

 

[Mon May 06 09:16:32.930991 2019] [proxy_http:error] [pid 29607] (70007)The timeout specified has expired: [client 192.168.224.8:49679] AH01102: error reading status line from remote server update.eset.com:80
[Mon May 06 09:16:32.931042 2019] [proxy:error] [pid 29607] [client 192.168.224.8:49679] AH00898: Error reading from remote server returned by hxxp://update.eset.com/ep7-dll-rel-lb/mod_049_horusdb_4350/em049_64_l0.dll.nup
[Mon May 06 09:29:08.351585 2019] [proxy_http:error] [pid 4953] (70007)The timeout specified has expired: [client 192.168.224.8:50128] AH01102: error reading status line from remote server update.eset.com:80
[Mon May 06 09:29:08.351623 2019] [proxy:error] [pid 4953] [client 192.168.224.8:50128] AH00898: Error reading from remote server returned by hxxp://update.eset.com/ep7-dll-rel-stop1/mod_049_horusdb_4350/em049_64_l0.dll.nup

[Tue May 07 09:07:03.708265 2019] [proxy:error] [pid 4185] [client 192.168.224.8:49861] AH00898: DNS lookup failure for: i3.c.eset.com returned by hxxp://i3.c.eset.com:80/
 

192.168.224.8 was client that had problem with update on monday.

 

Also I see many (not too many) messages about DNS lookup failure. Is this something I should look on my side, ISP side? 

cat error_log | grep -o "DNS lookup failure" | wc -l
64