ct-Open-Source / ct-Open-Source/team-container
Nextcloud 500 error - where to start searching
- Dominant language
- HTML
- Stars
- 116
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the team container for several month now without any problem. Installed as vm-guest under esxi.
Last week we had a power failure. After reboot nextcloud isn't working anymore.
The instance seems to run:
kubectl get pods
NAME READY STATUS RESTARTS AGE
svclb-traefik-6zjzv 2/2 Running 42 263d
traefik-694bfcf5fd-s6phg 1/1 Running 21 263d
landingpage-7d68966c84-5rf8f 1/1 Running 21 263d
nextcloud-team-nextcloud-redis-69df94ccb9-j5lvf 1/1 Running 21 263d
nextcloud-team-nextcloud-db-76c6ccb6fc-jgnhs 1/1 Running 21 263d
nextcloud-team-nextcloud-nc-54b875ddd5-kgn7s 2/2 Running 43 263d
But if I want to access nextcloud with browser I receive
#########################################################
Interner Serverfehler
Der Server konnte die Anfrage nicht fertig stellen.
Sollte dies erneut auftreten, sende bitte die nachfolgenden technischen Einzelheiten an Deinen Server-Administrator.
Weitere Details können im Server-Protokoll gefunden werden.
Technische Details
Entfernte Adresse: 10.42.0.203
Anfragekennung: u2OsmDD1AM9cHeCk3kdx
#########################################################
Unfortunately I'm the administrator but I have no idea.......
In /var/log/pods/default_nextcloud-team-nextcloud-nc-54b875ddd5-kgn7s_d2c201aa-0e7f-4fb6-be4c-be964ab9d940/web
I found entries like this:
2021-01-24T22:33:39.36818601+01:00 stdout F 10.42.0.198 - kdxyz [24/Jan/2021:21:33:39 +0000] "GET /status.php HTTP/1.1" 500 425 "-" "Mozilla/5.0 (Windows) mirall/3.0.1stable-Win64 (build 20200828) (Nextcloud)"
Where can I start searching for this error?
thanks in advance!
Klaus Deiss
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the listed Kubernetes pods and inspect the Nextcloud container logs around the failing /status.php request, including the web log at /var/log/pods/.../web. Compare the pod state with the server-protocol details from the browser. Done means identifying the post-reboot failure and restoring successful Nextcloud access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100