Comtekk Dispatcher: Complete Setup & Quick Start Guide

Troubleshooting Common Comtekk Dispatcher Issues — Fast Fixes

Below are frequent Comtekk Dispatcher problems and concise, actionable fixes you can apply quickly.

1. Dispatcher won’t start

• Cause: Configuration file error or missing dependency.
• Fix:
  1. Check logs (dispatcher.log) for startup errors.
  2. Validate config file syntax (JSON/YAML) and required fields.
  3. Ensure required services (database, message broker) are running and reachable.
  4. Restart service after fixes:

     Code
     Copy CodeCopied
     sudo systemctl restart comtekk-dispatcher 

  5. If still failing, run dispatcher in foreground to see errors:

     Code
     Copy CodeCopied
     comtekk-dispatcher –config /path/to/config –debug 

2. Worker nodes not receiving jobs

• Cause: Network/connectivity, authentication, or queue misconfiguration.
• Fix:
  1. Verify network connectivity between dispatcher and worker nodes (ping/telnet on ports).
  2. Confirm worker registration in the dispatcher dashboard or via API.
  3. Check message broker queues (RabbitMQ/Kafka) for stuck messages and consumer counts.
  4. Verify credentials and TLS certificates haven’t expired.
  5. Restart worker service if necessary.

3. Jobs stuck in “pending” or “queued”

• Cause: Exhausted worker capacity, dead consumers, or rate limits.
• Fix:
  1. Inspect worker health and concurrency settings. Increase worker pool if capacity is insufficient.
  2. Clear or requeue stuck messages from the broker management UI.
  3. Look for rate-limit or throttling logs and adjust limits.
  4. If tasks are failing fast, enable retry/backoff settings to prevent queue clogging.

4. High latency or slow dispatching

• Cause: Resource contention, database slow queries, or insufficient scaling.
• Fix:
  1. Monitor CPU, memory, disk I/O on dispatcher and broker hosts.
  2. Optimize database queries referenced by dispatcher; add indexes if needed.
  3. Scale horizontally (add dispatcher instances) or vertically (increase instance size).
  4. Enable caching for frequent reads and tune broker prefetch/poll intervals.

5. Authentication/authorization failures

• Cause: Misconfigured auth provider, expired tokens, or wrong scopes.
• Fix:
  1. Verify authentication provider (LDAP/OAuth) connectivity and logs.
  2. Check token lifetimes and refresh flows. Renew credentials or rotate keys if expired.
  3. Confirm role/permission mappings in dispatcher config match user roles.

6. Incorrect job routing or priorities ignored

• Cause: Routing rules misconfiguration or priority settings