Skip to content

First Steps

Troubleshooting Steps for Service or Saga-Worker

When encountering issues with a service or Saga-Worker, follow these systematic steps to diagnose and resolve the problem effectively:

Check Service or Saga-Worker Status

Start by verifying if the Service or Saga-Worker is running as expected. If not, proceed with the following steps:

Log and Configuration Examination

  1. Check Logs and Configuration:
  2. Review logs for any errors or anomalies that might indicate why the service is not running.
  3. Ensure that the configuration settings are correctly set up and aligned with the service requirements.

Logging Level Adjustment

For deeper insights into the issue, consider increasing the log level to Debug or Trace:

  1. Adjust Log Level:
  2. Increase log verbosity to Debug or Trace to gather more detailed information.

Credentials Verification

  1. Verify Credentials:
  2. Double-check credentials used by third-party components to prevent authentication issues.
  3. Look out for "not authorized - 401" messages in logs as indicators of authentication failures.

Health-Endpoints Analysis

  1. Check Health-Endpoints:
  2. Utilize health-endpoints to assess the overall system health.
    • Verify the existence and accessibility of critical components like databases (e.g., ArangDb, Postgres) through state endpoints.
    • Ensure that the correct credentials are used for accessing these components.

Log Analysis

  1. Review Logs for Context:
  2. Analyze logs for additional context, errors, or warnings related to the issue.

Queue Inspection

  1. Inspect Message Queues:
  2. Check for error messages or stalled processes in message queues, especially in asynchronous communication scenarios.

By following these steps in a methodical manner, you can efficiently troubleshoot and resolve issues affecting your service or Saga-Worker, minimizing downtime and ensuring smooth operation.