--- title: "Health Check Messages for Servers" canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/184583875/Health%20Check%20Messages%20for%20Servers" format: markdown --- The following tables describe potential health check messages for NIOS-X servers that can be displayed on the Infoblox Portal. Infoblox recommends corrective actions you can take to mitigate some of the health check errors. ## Generic Platform Management and Application Management Health Check Messages | **Component** | **Message displayed in the Infoblox Portal** | **Potential reasons for the health check error** | **Possible corrective actions** | | --- | --- | --- | --- | | Platform/Application Management | Disconnected | 1. Lack of network connectivity on the NIOS-X server. 2. One of the following firewall configuration happened on the NIOS-X server: - Port 443 blocked - TLS v1.2 or v1.3 blocked - Infoblox cloud IPs blocked 3. Failed to connect to HTTPS proxy 4. High CPU usage on the NIOS-X server 5. High Memory usage on the NIOS-X server 6. Improper NIOS-X server configuration | **Firewall configuration: **
- Check whether outgoing connections from the NIOS-X server to the Infoblox platform using port 443 are allowed on the firewall. - Check whether outgoing connections from the NIOS-X server to the Infoblox platform using TLS v1.2 and TLS v1.3 are working.
**Proxy configuration:**
Check whether the proxy used is functioning properly and allowing connections to the Infoblox platform. | | Application Management | Application Tunnel is Inactive | | Platform Management | Offline | When any service failed to start. | N/A | | Application Management | Error | ## Platform Management Health Check Messages Note that all health check messages follow this syntax: *:*  | **Service Name** | **Message displayed in the Infoblox Portal** | **Potential reasons for the health check error** | **Possible corrective actions** | | --- | --- | --- | --- | | blox.noa | Failed to revoke BloxOne Edge | 1. Lack of network connectivity on the NIOS-X server. 2. One of the following firewall configuration happened on the NIOS-X server: - Port 443 blocked - TLS v1.2 or v1.3 blocked - Infoblox cloud IPs blocked 3. Failed to connect to HTTPS proxy 4. High CPU usage on the NIOS-X server 5. High Memory usage on the NIOS-X server | **Firewall configuration: **
- Check whether outgoing connections from the NIOS-X server to the Infoblox platform using port 443 are allowed on the firewall. - Check whether outgoing connections from the NIOS-X server to BlocxOne Cloud using TLS v1.2 and TLS v1.3 are working.
**Proxy configuration:**
Check whether the proxy used is functioning properly and allowing connections to the Infoblox platform. | | blox.noa | Unable to connect to BloxOne Cloud | | blox.noa | Failed to revoke BloxOne Edge | | blox.noa | Failed to register to BloxOne Cloud | | blox.noa | Failed to activate BloxOne Edge | | keepalived_keepalived_1 | Keepalived node is unhealthy | | bootstrap-service | Disconnected from the Bootstrap Controller | | bootstrap-node-controller | OnPrem is Offline | One or more of the following caused connectivity loss on new interface configuration.
- Gateway mis-configuration or deletion. - Failure to allocate IP address (via dynamic IP allocation). - Change in metric for gateway results in network connectivity loss. | Wait at least five minutes after any interface configuration before checking online status of the NIOS-X server via the Infoblox Portal.
**Route Table configuration**
- Try to access the NIOS-X server via serial console. - Check the route table default gateway content. | | k3s-mgr-k3s-mgr | Failed to install Kubernetes cluster | Internal errors during the K3s installation process.
- Pre-checks might have failed. - System failed to meet the minimum resource requirements. | - Check to see if there are enough system resources for K3s installation: [https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/) - Check to see if there is IP overlapping with K3s CIDRs: [https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/#networking](https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/#networking) or Docker Bridge IP. | | k3s-mgr-k3s-mgr | Kubernetes cluster is unhealthy | K3s cluster is unhealthy. Possible reasons:
- High CPU usage on the NIOS-X server. - High memory usage on the  NIOS-X server. | Take care of the CPU and/or memory usage. | | bootstrap-node-controller | Internal server error: <*particular reason*> | | platform-firewall | IP Tables and Chains not initialized | - Some IP tables were locked. - Internal NIOS-X server errors. - IP table chains were broken. | Verify and fix potential issues. | | scout | Failed to initialize BloxOne Edge | - CPU throttle. - High memory usage. - Failure in getting network interfaces on the NIOS-X server. | Verify and fix potential issues. | | scout | Failed to setup BloxOne Edge | ## Application Management Health Check Messages Note that all health check messages follow this syntax: *:* | **Component** | **Message displayed in the Infoblox Portal** | **Potential reasons for the failed health check** | **Possible corrective actions** | | --- | --- | --- | --- | | app-infra_config-service_1 | Unable to connect to BloxOne Cloud | 1. Lack of network connectivity on the NIOS-X server. 2. One of the following firewall configuration happened on the NIOS-X server: - Port 443 blocked - TLS v1.2 or v1.3 blocked - Infoblox cloud IPs blocked 3. Failed to connect to HTTPS proxy 4. High CPU usage on the NIOS-X server 5. High Memory usage on the NIOS-X server 6. For the NIOS Grid, failed to synchronize with the Infoblox platform | **Firewall configuration: **
- Check whether outgoing connections from the NIOS-X server to the Infoblox platform using port 443 are allowed on the firewall. - Check whether outgoing connections from the NIOS-X server to the Infoblox platform using TLS v1.2 and TLS v1.3 are working.
**Proxy configuration:**
Check whether the proxy used is functioning properly and allowing connections to the Infoblox platform.
**NIOS Grid configuration**:
- Check whether the IPAM federation on the NIOS Grid is properly configured. - Check whether the outgoing connections from the NIOS Grid to the Infoblox platform is allowed and properly configured. - Check the NIOS Grid Connector configuration. | | app-infra_health-reporter_1 | Failed to sync NIOS Grid Infra to BloxOne Cloud | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:1 | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:2 | | app-infra_message-agent_1 | Failed to connect to Message Controller | | app-infra_app-logger_1 | Unable to connect to Bloxone Cloud | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:3 | This error is a summary of Onprem Monitor unhealthy. Err: 1 and Err: 2 when app-infra_app-monitor_1 experiences multiple issues simultaneously. | See potential reasons and possible corrective actions for the following components:
- Onprem Monitor unhealthy. Err:1 - Onprem Monitor unhealthy. Err:2 | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:16 | Unable to establish a connection to subscribe from the event runtime. | N/A | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:32 | Unable to publish to the event runtime. | N/A | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:64 | Formatting errors during marshaling/compression. | N/A | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:4096 | Prometheus running on the NIOS-X server is not reachable. | N/A | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:8192 | Prometheus is not sending metrics to the NIOS-X server monitor. | N/A | | app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:12288 | This error is a summary of Onprem Monitor unhealthy. Err: 4096 and Err: 8192 when app-infra_app-monitor_1 experiences multiple issues simultaneously. | See potential reasons for the following components:
- Onprem Monitor unhealthy. Err:4096 - Onprem Monitor unhealthy. Err:8192 | | app-infra_NIOS-X server-controller_1 | NIOS-X server controller is unhealthy | Internal k3s/docker errors. | N/A | | app-infra_admission-controller_1 | Failed to admit pods. | Internal errors. | N/A | | app-infra_message-agent_1 | Error in Messaging Service | Daprd sidecar is down. | N.A | | app-infra_dapr-sidecar-injector_1 | CrashLoopBackOff :back-off restarting failed container=dapr-sidecar-injector pod= | Internal dapr errors. | N/A | | app-infra_dapr-operator_1 | CrashLoopBackOff :back-off  restarting failed container=dapr-operator pod= | | app-infra_mosquitto_1 | Dial tcp : connect: connection refused | Default health check: TCP port (1883) is not reachable. | Check TCP port (1883) to ensure that it is reachable. |