---

name: debugging description: Use when troubleshooting host service connectivity, debugging data loading issues, investigating progress tracking problems, diagnosing environment or configuration issues, or checking Grafana dashboards.

Debugging Common Issues

Load this skill when:

• Troubleshooting host service connectivity
• Debugging data loading issues
• Investigating progress tracking problems
• Diagnosing environment or configuration issues

For distributed tracing and Jaeger queries, use the observability skill instead.

---

Debugging Priority

1. Check Grafana dashboards — Quick visual diagnostics
2. Query Jaeger — For operation-specific issues (see observability skill)
3. Check logs — Only if observability doesn't have the answer

---

Grafana Dashboards (First Stop)

URL: http://localhost:3000

Quick Checks

• "Is it working?" → System Overview: Healthy Services count
• "Why is it slow?" → System Overview: P95 Latency panel
• "Workers missing?" → Worker Status: Healthy Workers and Health Matrix
• "Operations failing?" → Operations: Success Rate and Status Distribution

Dashboard files: deploy/shared/grafana/dashboards/

---

Host Services Not Working

Check if services are running

Copylsof -i :5001  # IB Host Service
lsof -i :5002  # Training Host Service

Test connectivity from Docker

Copydocker exec ktrdr-backend curl http://host.docker.internal:5001/health
docker exec ktrdr-backend curl http://host.docker.internal:5002/health

Check logs

Copytail -f ib-host-service/logs/ib-host-service.log
tail -f training-host-service/logs/training-host-service.log

Common issues

---

Environment Variable Issues

Check what's set in Docker container

Copydocker exec ktrdr-backend env | grep -E "(IB|TRAINING)"

Common problems

• USE_IB_HOST_SERVICE not set → Falls back to local (wrong in Docker)
• URL wrong → Connection failures
• Service not started → Timeouts

Required environment for Docker

CopyUSE_IB_HOST_SERVICE=true
IB_HOST_SERVICE_URL=http://host.docker.internal:5001

---

Progress Not Updating

Check in this order:

1. Is OperationsService being used?

   • File: ktrdr/api/services/operations_service.py
   • The operation must be registered with register_operation()

2. Is progress callback being passed?

   • ServiceOrchestrator methods need progress callback
   • Check the calling code passes callback

3. Is GenericProgressManager updating?

   • Progress updates happen through the manager
   • Check update_progress() is being called

4. Is cancellation token triggered?

   • Cancelled operations stop updating
   • Check token.is_cancelled()

---

Data Loading Issues

Common root causes

1. IB Gateway not running (port 4002)

   Copylsof -i :4002
   

2. IB Host Service not started

   Copycurl http://localhost:5001/health
   

3. Symbol format incorrect

   • Use IB format: AAPL not AAPL.US

4. Date range outside available data

   • Check IB has data for the requested range

5. Timeframe not supported

   • IB supports specific timeframes only

Debug data flow

Copy# Check if data exists locally
ktrdr data get-range AAPL 1d

# Test IB connection
ktrdr ib test-connection

# Check IB status
ktrdr ib check-status

---

Workers Not Registering

Check registered workers

Copycurl http://localhost:8000/api/v1/workers | jq

Common issues

Worker logs

Copydocker-compose logs -f backtest-worker
docker-compose logs -f training-worker

---

Async/Await Issues

"Function not working in async context"

Wrong — Wrap in try/except and return None:

Copytry:
    result = await something()
except:
    return None  # Hides the real problem

Right — Ensure proper async/await chain:

Copy# Check the entire call chain is async
async def caller():
    result = await async_function()  # Must be awaited
    return result

Common async mistakes

• Forgetting await on async functions
• Mixing sync and async code incorrectly
• Not using asyncio.to_thread() for blocking operations

---

Test Failures

Unit tests failing

Copy# Run with verbose output
make test-unit PYTEST_ARGS="-v"

# Run single test
uv run pytest tests/path/to/test.py::test_name -v

Integration tests failing

Copy# Check services are running
docker-compose ps

# Run with output
make test-integration PYTEST_ARGS="-v -s"

Common test issues

• Missing fixtures → Check conftest.py
• Database state → Tests may need isolation
• Async issues → Ensure @pytest.mark.asyncio decorator

---

Quick Diagnostic Commands

Copy# Check all services
docker-compose ps

# Check backend health
curl http://localhost:8000/health | jq

# Check workers
curl http://localhost:8000/api/v1/workers | jq

# Check operations
curl http://localhost:8000/api/v1/operations | jq

# Check recent logs
docker-compose logs --tail=100 backend

# Check resource usage
docker stats --no-stream