Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Installation Issues

​
Pods Stuck in Pending

Symptoms: Pods remain in Pending state. Diagnosis: 
kubectl describe pod -n jitera <pod-name>
Common Causes and Solutions:
  1. Insufficient resources 
    # Check node resources
kubectl describe nodes | grep -A 5 "Allocated resources"
    Solution: Scale up nodes or reduce resource requests.
  2. PVC not bound 
    kubectl get pvc -n jitera
    Solution: Check storage class exists and has capacity.
  3. Node selector mismatch Solution: Verify node labels match pod selectors.

​
Pods in CrashLoopBackOff

Symptoms: Pods repeatedly crash and restart. Diagnosis: 
kubectl logs -n jitera <pod-name> --previous
kubectl describe pod -n jitera <pod-name>
Common Causes:
  1. Configuration error
    • Check environment variables
    • Verify secrets are correct
  2. Database connection failure 
    kubectl exec -n jitera <pod> -- nc -zv jitera-postgresql 5432
  3. Missing dependencies
    • Check init containers completed
    • Verify required services are running

​
ImagePullBackOff

Symptoms: Pod cannot pull container image. Diagnosis: 
kubectl describe pod -n jitera <pod-name> | grep -A 5 "Events"
Solutions:
  1. Check registry credentials 
    registryCredentials:
  server: jiteradockerimage.azurecr.io
  username: <correct-username>
  password: <correct-password>
  2. Verify secret exists 
    kubectl get secret -n jitera regcred
  3. Recreate secret 
    kubectl delete secret regcred -n jitera
helm upgrade jitera ./charts/jitera -f values.yaml -n jitera

​
Authentication Issues

​
Session Expired Too Quickly

Symptoms: Users logged out frequently. Solution: Check JWT configuration: 
jwt:
  secret: <must-be-64-characters>
  expiry: 86400  # 24 hours

​
Database Issues

​
Database Connection Failed

Symptoms: “Connection refused” or timeout errors. Diagnosis: 
# Check PostgreSQL pod
kubectl get pod -n jitera -l app.kubernetes.io/name=postgresql

# Test connection
kubectl exec -n jitera deploy/jitera-automation-rails -- nc -zv jitera-postgresql 5432
Solutions:
  1. Check database pod is running 
    kubectl logs -n jitera -l app.kubernetes.io/name=postgresql
  2. Verify credentials 
    kubectl get secret jitera-postgresql -n jitera -o yaml
  3. For external database: Verify network connectivity and credentials.

​
Migration Failed

Symptoms: “Migration error” or incomplete database schema. Diagnosis: 
kubectl exec -it -n jitera deploy/jitera-automation-rails -- rails db:migrate:status
Solution: 
# Retry migration
kubectl exec -it -n jitera deploy/jitera-automation-rails -- rails db:migrate

# If stuck, check for locks
kubectl exec -it -n jitera $PG_POD -- psql -U jitera -c "SELECT * FROM pg_locks WHERE NOT granted;"

​
Storage Issues

​
S3/Azure Storage Access Denied

Symptoms: “Access Denied” or “Forbidden” errors. Diagnosis: 
kubectl logs -n jitera -l app=jitera-automation-rails | grep -i storage
Solutions:
  1. Verify credentials 
    # Test AWS S3
aws s3 ls s3://your-bucket

# Test Azure
az storage container list --account-name your-account
  2. Check bucket/container names match configuration
  3. Verify IAM permissions include required actions

​
PVC Storage Full

Symptoms: “No space left on device” errors. Diagnosis: 
kubectl exec -n jitera <pod> -- df -h
Solutions:
  1. Expand PVC (if supported): 
    kubectl edit pvc <pvc-name> -n jitera
# Increase spec.resources.requests.storage
  2. Clean up old data
  3. Add additional storage

​
Performance Issues

​
Slow Response Times

Symptoms: Pages load slowly or timeout. Diagnosis: 
# Check resource usage
kubectl top pods -n jitera

# Check for throttling
kubectl describe pod -n jitera <pod> | grep -i throttl
Solutions:
  1. Increase resources 
    automation:
  resources:
    limits:
      cpu: 2
      memory: 4Gi
  2. Scale horizontally 
    automation:
  replicas: 3
  3. Check database performance

​
High Memory Usage

Symptoms: Pods OOMKilled. Diagnosis: 
kubectl describe pod -n jitera <pod> | grep -i oom
Solutions:
  1. Increase memory limits 
    automation:
  resources:
    limits:
      memory: 8Gi
  2. Check for memory leaks in logs
  3. Optimize workload distribution

​
Network Issues

​
Cannot Reach External Services

Symptoms: Timeout connecting to GitHub, AI providers, etc. Diagnosis: 
kubectl exec -n jitera <pod> -- curl -v https://api.github.com
Solutions:
  1. Check egress rules (network policies, firewalls)
  2. Verify DNS resolution 
    kubectl exec -n jitera <pod> -- nslookup api.github.com
  3. Check proxy configuration if required

​
Load Balancer Not Provisioned

Symptoms: Service stuck with no external IP. Diagnosis: 
kubectl describe svc -n jitera -l app.kubernetes.io/name=kong
Solutions:
  1. AWS: Check IAM permissions for load balancer creation
  2. Azure: Check Azure resource quotas
  3. On-premises: Verify MetalLB configuration

​
Certificate Issues

​
TLS Certificate Not Valid

Symptoms: Browser shows certificate warning. Diagnosis: 
# Check certificate
kubectl get certificate -n jitera
openssl s_client -connect app.example.com:443 -servername app.example.com
Solutions:
  1. cert-manager: Check issuer status 
    kubectl describe clusterissuer letsencrypt-prod
kubectl describe certificate -n jitera
  2. Manual certificate: Verify secret contains valid cert 
    kubectl get secret jitera-tls -n jitera -o yaml

​
AI Feature Issues

​
AI Not Responding

Symptoms: AI features timeout or return errors. Diagnosis: 
kubectl logs -n jitera -l app=jitera-ultron --tail=50
Solutions:
  1. Check API key is valid and has quota
  2. Verify connectivity to AI provider 
    kubectl exec -n jitera deploy/jitera-ultron -- curl https://api.openai.com/v1/models
  3. Check AI configuration in Helm values