When troubleshooting a down Portworx node, the first and most fundamental step is to verify the health of the underlying Kubernetes infrastructure. Portworx runs as a daemonset on Kubernetes nodes, and its health is directly dependent on the node's status. The command kubectl get node -o wide provides a cluster-wide overview, confirming if all nodes are in a Ready state and can schedule pods. If a Kubernetes node is NotReady, no application-level troubleshooting for Portworx on that node will succeed until the underlying node issue is resolved. This approach follows the standard bottom-up troubleshooting methodology, starting with the foundational layer (Kubernetes) before moving to the application layer (Portworx).

A. pxctl status to check the status of Portworx on the node.

This command checks the Portworx application status. It is a secondary step, as it will likely fail or provide misleading information if the underlying Kubernetes node is not healthy.

C. journalctl -u kubelet to identify the problem on the node.

This is a deep-dive diagnostic command to check kubelet logs. It is typically used after kubectl get node has identified a specific node as NotReady or unhealthy.

1. Portworx Enterprise Documentation

"Troubleshoot Portworx on Kubernetes": The official troubleshooting guide for Portworx on Kubernetes consistently uses kubectl commands as the initial step to assess the state of the environment. For instance

in the section "Portworx pods are not running

" the first action is to use kubectl get pods and kubectl describe pod

which presumes the Kubernetes nodes themselves are functional. Verifying node status with kubectl get nodes is the prerequisite step to ensure the scheduler can even attempt to place pods.

Source: Portworx Enterprise Documentation

Section: Monitor and Troubleshoot -> Troubleshoot Portworx -> Troubleshoot Portworx on Kubernetes.

2. Portworx Enterprise Documentation

"Prerequisites": All installation guides for Portworx on any Kubernetes distribution list a healthy

functional Kubernetes cluster as a primary prerequisite. A core indicator of a healthy cluster is that all nodes are in the Ready state. Therefore

checking this status is the logical first step in any troubleshooting scenario that might involve infrastructure failure.

Source: Portworx Enterprise Documentation

Section: Install and Configure -> Install Portworx -> Install Portworx on Kubernetes -> Prerequisites.