List of alerts and corrective actions
This page lists all the alerts generated by the Weka system, along with possible actions to take.
Name
Description
Actions
AdminDefaultPassword
The admin password is still set to the factory default.
Change the admin user password to ensure only authorized users can access the cluster.
AgentNotRunning
The Weka local control agent is not running on a host.
Restart the agent with service weka-agent start.
ApproachingClientsUnavailability
Approaching the maximum amount of clients that can connect with the current cluster resources.
Make sure all backhand servers are up or expand the cluster with more backend servers.
AutoRemoveTimeoutTooLow
Stateless Client auto-remove timeout too low.
Remount the host with a higher auto-remove timeout value.
BackendNumaBalancingEnabled
A host has automatic NUMA balancing enabled, which can negatively impact performance.
To disable the NUMA balancing, on the backend host, run echo 0 > /proc/sys/kernel/numa_balancing.
BackendVersionsMismatch
There are mismatching versions of backend servers in the cluster.
Upgrade all the backend servers to match the cluster's version.
BondInterfaceCompromised
The host is configured to work with a highly available network, but has lost the connectivity redundancy. A single network failure can disconnect the host from the cluster, which will result in the unavailability of data to the host (in case of a client host) or data protection reduced redundancy (in case of a backend host).
To resolve the issue, check the network configuration, cables, and NICs.
BucketHasNoQuorum
Too many compute nodes are down, causing the bucket compute resource to be unavailable.
Check that the compute nodes and their hosts are up and running and fully connected. If the issue is not resolved, contact the Customer Success Team.
BucketUnresponsive
A compute resource has failed, causing system unavailability.
Check that the compute nodes and their hosts are up and running and fully connected. If the issue is not resolved, contact the Customer Success Team.
ChokingDetected
High congestion level detected in the cluster.
For more information, see System Congestion.
ClientNumaBalancingEnabled
A host has automatic NUMA balancing enabled which can negatively impact performance.
To disable the NUMA balancing, on the client host, run echo 0 > /proc/sys/kernel/numa_balancing.
ClientVersionsMismatch
There are clients with a version that does not match the cluster version. Some features may not be available until all the clients are upgraded.
Upgrade clients to be in the same version as the cluster by locally running weka local upgrade.
ClockSkew
The clock of a host is skewed in relation to the cluster leader, with a time difference more than the permitted maximum of 30 seconds.
Make sure NTP is configured correctly on the hosts and that their dates are synchronized.
CloudHealth
A host cannot upload events to the Weka cloud.
Check the host has Internet connectivity and is connected to the Weka cloud as explained in the Weka Support Cloud section.
CloudStatsError
Statistics upload to Weka cloud failed.
Check the host has Internet connectivity and is connected to the Weka cloud as explained in the Weka Support Cloud section.
ClusterInitializationError
The cluster has encountered an error while initializing.
Fix the underlying problem causing the error to successfully start IO operations.
ClusterIsUpgrading
Cluster is upgrading.
If the upgrade doesn't finish normally, contact the Weka support for assistance.
CPUFrequentStarvation
CPU frequent starvation detected in the last minute.
Check the relevant hosts logs for potential hardware problems or core allocation issues.
CPUStarvation
Weka processes are experiencing long CPU stalls.
Check the relevant hosts logs for potential hardware problems.
Copy link