Page 1 of 1

WAPT 1.7 Enterprise CentOS Timout windows update

Published: August 1, 2019 - 10:20
by PierreC
Hello,
we are a new enterprise user and are experiencing frequent timeouts in the console, with the error message displayed in blue in the WUA section.
Is this negligible or indicative of a problem?
Here is a common error in our clients' logs:
`bsocket connect params: HTTPSConnectionPool(host='padme', port=443): Read timed out. (read timeout=30.0)
2019-08-01 08:43:52,927 CRITICAL Error merging Packages from https://padme/wapt into db: ReadTimeout: HTTPSConnectionPool(host='padme', port=443): Read timed out.` (read timeout=10.0)
2019-08-01 08:44:02,953 CRITICAL Error merging Packages from https://padme/wapt-host into db: ReadTimeout: HTTPSConnectionPool(host='padme', port=443): Read timed out. (read timeout=10.0)
Get packages index

Re: WAPT 1.7 Enterprise CentOS Timout windows update

Published: August 1, 2019 - 10:43
by sfonteneau
This doesn't necessarily have to be related to wua.

Code: Select all

bsocket connect params: HTTPSConnectionPool(host='padme', port=443): Read timed out. (read timeout=30.0)
This means the client can no longer connect to the server via WebSocket. It therefore times out. (Network error?)

The blue Wua logo could mean something else. (scan in progress, last scan failed..., error downloading wsusscn2.cab...) We need to see what the last retrieved inventory indicates.