...
Generic Platform Management and Application Management Health Check Messages
Component | Message displayed in the Cloud Services Portal | Potential reasons for the health check error | Possible corrective actions |
---|---|---|---|
Platform/Application Management | Disconnected |
| Firewall configuration:
Proxy configuration: Check whether the proxy used is functioning properly and allowing connections to BloxOne Cloud. |
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>
Service Name | Message displayed in the Cloud Services Portal | Potential reasons for the health check error | Possible corrective actions |
---|---|---|---|
blox.noa | Failed to revoke BloxOne Edge |
| Firewall configuration:
Proxy configuration: Check whether the proxy used is functioning properly and allowing connections to BloxOne Cloud. |
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.
| Wait at least five minutes after any interface configuration before checking online status of the host via the Cloud Services Portal. Route Table configuration
|
k3s-mgr-k3s-mgr | Failed to install Kubernetes cluster | Internal errors during the K3s installation process.
|
|
k3s-mgr-k3s-mgr | Kubernetes cluster is unhealthy | K3s cluster is unhealthy. Possible reasons:
| 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 |
| Verify and fix potential issues. |
scout | Failed to initialize BloxOne Edge |
| 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: <service name>:<message>
Component | Message displayed in the Cloud Services Portal | Potential reasons for the failed health check | Possible corrective actions |
---|---|---|---|
app-infra_config-service_1 | Unable to connect to BloxOne Cloud |
| Firewall configuration:
Proxy configuration: Check whether the proxy used is functioning properly and allowing connections to BloxOne Cloud. NIOS Grid 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:
|
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 host is not reachable. | N/A |
app-infra_app-monitor_1 | Onprem Monitor unhealthy. Err:8192 | Prometheus is not sending metrics to the host 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:
|
app-infra_host-controller_1 | Host 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 <duration> restarting failed container=dapr-sidecar-injector pod=<pod_name> | Internal dapr errors. | N/A |
app-infra_dapr-operator_1 | CrashLoopBackOff :back-off <duration> restarting failed container=dapr-operator pod=<pod_name> | ||
app-infra_mosquitto_1 | Dial tcp <IP:1883>: connect: connection refused | Default health check: TCP port (1883) is not reachable. | Check TCP port (1883) to ensure that it is reachable. |