Skip to content

Commit 85f9ded

Browse files
gbartolinimnencia
authored andcommitted
docs: more review
Signed-off-by: Gabriele Bartolini <[email protected]>
1 parent 02ca263 commit 85f9ded

File tree

1 file changed

+50
-14
lines changed

1 file changed

+50
-14
lines changed

web/docs/troubleshooting.md

Lines changed: 50 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -104,22 +104,58 @@ kubectl logs -n <namespace> <cluster-pod-name> -c plugin-barman-cloud --previous
104104

105105
When a backup fails, follow these steps in order:
106106

107-
1. **Check backup status**: `kubectl get backups.postgresql.cnpg.io -n <namespace>`
108-
2. **Get error details and target pod**:
109-
```bash
110-
kubectl describe backups.postgresql.cnpg.io -n <namespace> <backup-name>
111-
# Or extract just the target pod name
112-
kubectl get backups.postgresql.cnpg.io -n <namespace> <backup-name> -o jsonpath='{.status.instanceID.podName}'
107+
1. **Check backup status**:
108+
109+
```sh
110+
kubectl get backups.postgresql.cnpg.io -n <namespace>
113111
```
114-
3. **Check the specific target pod's sidecar logs**:
115-
```bash
116-
TARGET_POD=$(kubectl get backups.postgresql.cnpg.io -n <namespace> <backup-name> -o jsonpath='{.status.instanceID.podName}')
117-
kubectl logs -n <namespace> $TARGET_POD -c plugin-barman-cloud --tail=100 | grep -E "ERROR|FATAL|panic"
112+
2. **Get error details and target pod**:
113+
114+
```sh
115+
kubectl describe backups.postgresql.cnpg.io \
116+
-n <namespace> <backup-name>
117+
118+
kubectl get backups.postgresql.cnpg.io \
119+
-n <namespace> <backup-name> \
120+
-o jsonpath='{.status.instanceID.podName}'
121+
```
122+
3. **Check the target pod’s sidecar logs**:
123+
124+
```sh
125+
TARGET_POD=$(kubectl get backups.postgresql.cnpg.io \
126+
-n <namespace> <backup-name> \
127+
-o jsonpath='{.status.instanceID.podName}')
128+
129+
kubectl logs \
130+
-n <namespace> $TARGET_POD -c plugin-barman-cloud
131+
--tail=100 | grep -E "ERROR|FATAL|panic"
132+
```
133+
4. **Check cluster events**:
134+
135+
```sh
136+
kubectl get events -n <namespace> \
137+
--field-selector involvedObject.name=<cluster-name> \
138+
--sort-by='.lastTimestamp'
139+
```
140+
5. **Verify plugin is running**:
141+
142+
```sh
143+
kubectl get pods \
144+
-n cnpg-system -l app.kubernetes.io/name=barman-cloud
145+
```
146+
6. **Check operator logs**:
147+
148+
```sh
149+
kubectl logs \
150+
-n cnpg-system deployment/cnpg-controller-manager \
151+
--tail=100 | grep -i "backup\|plugin"
152+
```
153+
7. **Check plugin manager logs**:
154+
155+
```sh
156+
kubectl logs \
157+
-n cnpg-system deployment/barman-cloud --tail=100
118158
```
119-
4. **Check cluster events**: `kubectl get events -n <namespace> --field-selector involvedObject.name=<cluster-name> --sort-by='.lastTimestamp'`
120-
5. **Verify plugin is running**: `kubectl get pods -n cnpg-system -l app.kubernetes.io/name=barman-cloud`
121-
6. **Check operator logs**: `kubectl logs -n cnpg-system deployment/cnpg-controller-manager --tail=100 | grep -i "backup\|plugin"`
122-
7. **Check plugin manager logs**: `kubectl logs -n cnpg-system deployment/barman-cloud --tail=100`
123159

124160
#### Backup job fails immediately
125161

0 commit comments

Comments
 (0)