Skip to content

Commit cc5bd1d

Browse files
ajaydevtron123ajay0prakarsh-dt
authored
DOC: added problem solutions in troubleshoot guide (devtron-labs#1574)
* added more problem solutions in troubleshoot guide * Update devtron-troubleshoot.md Co-authored-by: 123ajay0 <123ajay0@gmail.com> Co-authored-by: Prakarsh <71125043+prakarsh-dt@users.noreply.github.com>
1 parent c9d1052 commit cc5bd1d

1 file changed

Lines changed: 89 additions & 0 deletions

File tree

docs/FAQs/devtron-troubleshoot.md

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,3 +164,92 @@ Then delete postgresql pod so that it can fetch the updated images:
164164
kubectl delete pod -n devtroncd postgresql-postgresql-0
165165
```
166166
You can also delete other pods which are in crashloop after postgresql is up and running so that they can restart and connect to postgresql and Devtron will be up and running again in a few moments.
167+
168+
#### 10. Unable to fetch the latest commit and not able to trigger auto build.
169+
170+
To solve this, bounce the git-sensor-0 pod.
171+
```
172+
kubectl delete pod -n devtroncd git-sensor-0
173+
```
174+
#### 11. If you have restricted devtron-service to be accessible on certain IPs only and SSO login isn’t working
175+
176+
Whitelist the NAT-gateway IPs of the cluster (There can be multiple NAT-gateways if your cluster is multi-AZ)
177+
178+
#### 12. If CPU metrics are not showing but memory metrics are visible in graphs.
179+
180+
Do the following:-
181+
182+
1. Go to Grafana and Login with the credentials.
183+
2. Edit the CPU graphs and remove `image!=””` from the query.
184+
3. Save the dashboard.
185+
186+
CPU metrics should start showing up in a while.
187+
188+
#### 13. If user not able to upload a file more than specific size.
189+
190+
`Please use below annotation in ingress`
191+
```
192+
nginx.ingress.kubernetes.io/proxy-body-size: 100m
193+
```
194+
`Note:- `Where m is is MiB.
195+
196+
#### 14. If AWS Load balancer controller is unable to provision ALB and getting message in alb controller as unauthorized, attach these IAM policy to the nodegroup IAM Role.
197+
198+
[IAM policy](https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.3.1/docs/install/iam_policy.json)
199+
200+
#### 15. When app metrics is not coming on grafana and devtron dashboard, set the value of the following parameter as false in kube prometheus stack values.
201+
202+
```
203+
serviceMonitorSelectorNilUsesHelmValues: false
204+
```
205+
#### 16. Unable to deploy metrics-server using chart on devtron
206+
207+
To solve
208+
209+
Disable certificate validation by passing `--kubelet-insecure-tls` argument to metrics server chart.
210+
211+
#### 17. Unable to delete a database from postgres
212+
`Description of issue`
213+
214+
ERROR: database `<db-name>` is being accessed by other users
215+
216+
DETAIL: There is 1 other session using the database.
217+
218+
You have to terminate the connections to the database first, for that you can use the command.
219+
```
220+
SELECT pg_terminate_backend(pg_stat_activity.pid) FROM pg_stat_activity WHERE pg_stat_activity.datname = 'TARGET_DB';
221+
```
222+
Then run the command to delete database - `drop databases <db-name>`
223+
224+
#### 18. Unable to login with the auth password (argocd server)
225+
226+
`Debug`
227+
228+
Run the command for Admin Credentials and use it for login in dashboard
229+
230+
`kubectl -n devtroncd get secret devtron-secret -o jsonpath='{.data.ACD_PASSWORD}' | base64 -d`
231+
232+
If you are getting an error message of “invalid username or password”, follow the solution to solve it.
233+
234+
`Solution`
235+
236+
Run `kubectl get secret -n devtroncd` and then edit the `argocd-secret`, remove both the admin.password lines.
237+
238+
Run `kubectl delete po your-argocd-server-pod -n devtroncd`, it will create a new pod after deletion and reset your admin password. Re-run the command for admin credentials again to get the new password.
239+
240+
#### 19. After installing Devtron using helm, getting the admin password does not work.(if using windows)
241+
242+
`Debug`
243+
244+
'base64' is not recognized as an internal or external command, operable program or batch file.
245+
246+
`Solution`
247+
248+
The first way to debug is either install base64 encode and decode into your windows machine and use the appropriate cmd to get the admin password.
249+
250+
The other way is to get the password in the encoded form using the cmd
251+
252+
`kubectl -n devtroncd get secret devtron-secret -o jsonpath='{.data.ACD_PASSWORD}'`, further decode it into plaintext using an online [encoder decoder](https://www.base64decode.org/).
253+
254+
255+

0 commit comments

Comments
 (0)