Complete gids voor het oplossen van problemen in PMA v2.
Gebruik dit diagram om snel het juiste oplossingspad te vinden:
Symptomen:
just start SERVICE geeft errorDiagnose:
# Check container status
just status SERVICE
# Bekijk logs
just logs SERVICE
# Gedetailleerde diagnose
just health SERVICE --diagnose
Oplossingen:
| Oorzaak | Oplossing |
|---|---|
| Port al in gebruik | lsof -i :PORT en stop conflicterende service |
| Ontbrekende env vars | Check .env bestand |
| Volume permissions | sudo chown -R 1000:1000 volume/ |
| OOM killed | Verhoog memory limit in compose |
| Missing dependencies | just start dependency services eerst |
Voorbeeld fix:
# Port conflict oplossen
lsof -i :9114
# Output: ruby 12345 user ... (LISTEN)
# Stop conflicterende process
kill 12345
# Of: wijzig port in .env
echo "REDMINE_PORT=9115" >> .env
# Herstart
just restart redmine
Diagnose:
# Check restart count
docker inspect asd-SERVICE --format='{{.RestartCount}}'
# Check laatste exit
docker inspect asd-SERVICE --format='{{.State.ExitCode}}'
# Bekijk events
docker events --filter container=asd-SERVICE --since 1h
Common Exit Codes:
| Code | Betekenis | Actie |
|---|---|---|
| 0 | Normale exit | Check why service stopped |
| 1 | Application error | Check application logs |
| 137 | OOM killed | Increase memory limit |
| 139 | Segfault | Check for corrupt data |
| 143 | SIGTERM | Normal shutdown |
Diagnose:
# Check of container draait
docker ps | grep SERVICE
# Check of port luistert
ss -tlnp | grep PORT
# Test lokale connectivity
curl -v http://localhost:PORT
# Check Docker network
docker network inspect asd-network
Oplossingen:
# Service zit niet in network
docker network connect asd-network asd-SERVICE
# Firewall blokkeert
sudo ufw allow PORT/tcp
# DNS resolutie binnen Docker
# Gebruik container naam ipv localhost
curl http://asd-SERVICE:PORT
Diagnose:
# Check tunnel status
just mcp-asd net
# Check Cloudflare tunnel
just mcp-asd tunnel
Oplossingen:
# Reset tunnel connections
just mcp-asd net-reset
# Herstart tunnel service
just restart cloudflared
Diagnose:
# Check SSO configuratie
just sso-check SERVICE
# Test OAuth flow
just sso-test SERVICE
# Check Authentik status
just status authentik
just logs authentik
Common Issues:
| Probleem | Oorzaak | Oplossing |
|---|---|---|
| Redirect loop | Verkeerde callback URL | Check OAuth redirect URI |
| Invalid client | Client ID mismatch | Regenereer OAuth credentials |
| Token expired | Session timeout | Herstart browser, clear cookies |
| User not found | User niet in Authentik | Maak user aan in Authentik |
Voorbeeld fix:
# Check OAuth configuratie
just info authentik # Get admin URL
# In Authentik:
# 1. Applications > [Service]
# 2. Check Redirect URIs
# 3. Verify Client ID/Secret
# Update service configuratie
just sso-add SERVICE --reconfigure
# Reset admin wachtwoord (service-specifiek)
just SERVICE reset-password admin
# Check credentials
just info SERVICE # Toont default credentials
Diagnose:
# Check database container
docker ps | grep db
# Test database connectivity
docker exec -it asd-SERVICE-db psql -U user -d database -c "SELECT 1"
# Check database logs
docker logs asd-SERVICE-db --tail 100
Oplossingen:
# Database container niet running
just start SERVICE-db
# Connection refused
# Check POSTGRES_HOST in service config
# Moet 'asd-SERVICE-db' zijn, niet 'localhost'
# Authentication failed
# Check POSTGRES_PASSWORD in .env
Diagnose:
# Check database integrity (PostgreSQL)
docker exec -it asd-SERVICE-db psql -U user -d database -c "SELECT 1"
# Check disk space
df -h
Oplossingen:
# Restore van backup
just restore SERVICE
# Of: database recreate (DATA LOSS!)
just SERVICE reset-database
# Basic logs
just logs SERVICE
# Follow logs
just logs SERVICE -f
# Laatste N regels
just logs SERVICE --tail=500
# Zoek in logs
just logs SERVICE 2>&1 | grep ERROR
# Alle container logs
docker logs asd-SERVICE --since 1h
Sommige services ondersteunen debug mode:
# n8n debug mode
N8N_LOG_LEVEL=debug just start n8n
# Redmine debug
RAILS_ENV=development just start redmine
# Open shell in container
docker exec -it asd-SERVICE /bin/bash
# Of voor Alpine-based containers
docker exec -it asd-SERVICE /bin/sh
Diagnose:
# Check container resources
docker stats
# Check host resources
free -h
htop
Oplossingen:
# Restart service (clear memory)
just restart SERVICE
# Increase container memory limit
# Edit docker-compose.yml:
# deploy:
# resources:
# limits:
# memory: 2G
# Prune unused Docker resources
docker system prune -a
# Check disk usage
df -h
# Check Docker disk usage
docker system df
# Cleanup
docker system prune -a
docker volume prune
# Check backup sizes
du -sh backups/*
# WAARSCHUWING: Dit verwijdert alle data!
# 1. Backup maken
just backup SERVICE
# 2. Stop service
just stop SERVICE
# 3. Verwijder volumes
docker volume rm $(docker volume ls -q | grep SERVICE)
# 4. Herinstalleer
just package install SERVICE
# Bij complete failure
# 1. Check wat nog werkt
just health --diagnose
# 2. Restore ecosystem backup
just restore ecosystem
# 3. Start services
just start all
# 4. Verify
just health
Escaleer naar senior support als:
# Verzamel diagnostische info
just health --diagnose > /tmp/health.txt
docker ps -a > /tmp/containers.txt
docker logs asd-SERVICE > /tmp/logs.txt 2>&1
df -h > /tmp/disk.txt
free -h > /tmp/memory.txt
# Maak support bundle
tar -czf support-bundle.tar.gz /tmp/*.txt
| Probleem | Quick Fix |
|---|---|
| Service down | just restart SERVICE |
| Port conflict | lsof -i :PORT en stop process |
| DB connection | Check container naam in config |
| SSO fail | just sso-check SERVICE |
| Out of memory | docker system prune -a |
| Permissions | sudo chown -R 1000:1000 volume/ |
just health --diagnose # Full diagnostics
just status SERVICE # Service status
just logs SERVICE -f # Live logs
docker stats # Resource usage
docker system df # Disk usage