You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/troubleshooting-and-faq/troubleshooting.md
+60
Original file line number
Diff line number
Diff line change
@@ -76,3 +76,63 @@ JindoFS:
76
76
> As you can see from above command and help message, option `--name` and `--namespace` specified the name and namespace of Alluxio Runtime respectively.
77
77
78
78
All the logs will be packed in a package under execution path.
79
+
80
+
## Debug Fuse Pod
81
+
82
+
If the application Pod is in the `ContainerCreating` or `Pending` state for a long time and cannot be created due to the CSI Plugin issue, it is usually caused by the state of the Fuse Pod in the same node is not correct. You can follow these steps to troubleshoot.
83
+
84
+
### Check Application Pods Events
85
+
86
+
The first step in debugging Fuse is to check the application Pod information. Use the following command to check the current status and recent events of the Pod.
87
+
88
+
```shell
89
+
kubectl describe pods ${POD_NAME}
90
+
```
91
+
92
+
Similar to the following information, but may not be identical, but all point to the reason for FailedMount.
93
+
94
+
```shell
95
+
kubectl describe po nginx-0
96
+
...
97
+
Events:
98
+
Type Reason Age From Message
99
+
---- ------ ---- ---- -------
100
+
Normal Scheduled 30s default-scheduler Successfully assigned default/nginx-0 to testnode
101
+
Warning FailedMount 1s kubelet MountVolume.MountDevice failed for volume "default-shared-data": rpc error: code = Unknown desc = fuse pod on node testnode is not ready
102
+
```
103
+
104
+
### Get the information of the Fuse Pod corresponding to this application Pod
105
+
106
+
At this point you need to check the status of the Fuse Pod of this node, first use the following command to get the information of the node where the current application Pod is located, the output corresponding to the NODE column is the node where the application Pod is located.
107
+
108
+
109
+
```shell
110
+
kubectl get pods ${POD_NAME} -owide
111
+
```
112
+
113
+
For example, the following node where Fuse Pod is located is testnode:
114
+
115
+
```shell
116
+
kubectl get pods nginx-0 -owide
117
+
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
You can follow the [Kubernetes documentation](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/) to troubleshoot the issue with this Fuse Pod.
0 commit comments