The following section outlines common errors that might be encountered when using BlueCat Server Update Services. If errors occur, check the /var/log/syslog file on the DNS/DHCP Server for the following messages:
| Error Message | Cause/Resolution |
|---|---|
"Connection was closed, Retrying..." |
When adding a DNS/DHCP Server to a batch, the status appears as BAD due to a connection issue. If this occurs, check the local DNS/DHCP Server firewall rules and ensure that the IP address of BlueCat Server Update Services is allowed to communicate on the ports listed in Prerequisites. |
[Errno -3] Temporary failure in name
resolution |
Verify that the IP address of BlueCat Server Update Services is correct. If you are using a hostname, the DNS/DHCP Server must be able to resolve the DNS FQDN. |
Get Batches Error: NotFoundError(404,
'index_not_found_exception', 'no such index [batch], batch,
index_or_alias) |
BlueCat Batch Update Services did not completely initialize before you attempted to access the BlueCat Batch Update Service UI. You must stop the current BlueCat Batch Update Services container, delete the container, and install a new container. For more information on installing the container, refer to Installing BlueCat Server Update Services. If the problem persists, contact BlueCat Customer Care. |
Fetched Unmanaged Servers fail:
ConnectionError(<urllib3.connection.HTTPConnection object at
0x7f2745162898>: Failed to establish a new connection: [Errno 111]
Connection refused) caused by:
NewConnectionError(<urllib3.connection.HTTPConnection object at
0x7f2745162898>: Failed to establish a new connection: [Errno 111]
Connection refused) |
Occurs when the network is misconfigured and the elasticsearch container cannot connect with BlueCat Gateway. Verify that your docker network configuration settings are correctly configured based on the recommended settings. If the problem persists, contact BlueCat Customer Care. |
Cannot apply patch or update |
If you receive an error message in the BlueCat Batch Update Services UI indicating that the patch or update failed to apply, check the /var/log/update.log file on the affected DNS/DHCP Server. |