Skip to content

Worker process interrupted #225

Open
Open
Worker process interrupted#225

Description

@rcholic
rcholic
opened on Oct 24, 2024

I use taskiq with ListQueueBroker (backed by reddis).
In the log, I see a lots of worker process interrupted:

2024-10-23 22:22:38.363 | INFO     | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Listening started.
2024-10-23 22:22:39.445 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Worker process interrupted.
2024-10-23 22:22:39.446 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Shutting down the broker.
2024-10-23 22:22:42.697 | INFO     | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Listening started.
2024-10-23 22:22:43.684 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Worker process interrupted.
2024-10-23 22:22:43.686 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Shutting down the broker.
2024-10-23 22:22:46.688 | INFO     | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Listening started.
2024-10-23 22:22:47.921 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Worker process interrupted.
2024-10-23 22:22:47.923 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Shutting down the broker.
2024-10-23 22:22:50.809 | INFO     | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Listening started.
2024-10-23 22:22:52.167 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Worker process interrupted.
2024-10-23 22:22:52.181 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Shutting down the broker.
2024-10-23 22:22:55.158 | INFO     | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Listening started.
2024-10-23 22:22:56.489 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Worker process interrupted.
2024-10-23 22:22:56.492 | WARNING  | trace_id=0 | span_id=0 | logging:callHandlers:1706 - Shutting down the broker.

Is there a way to keep the worker and broker keep running?

Activity

  1. s3rius commented on Oct 24, 2024

    @s3rius
    s3rius
    on Oct 24, 2024
    Owner

    Can you enable DEBUG logging to see where the error might be?

  2. rcholic commented on Oct 24, 2024

    @rcholic
    rcholic
    on Oct 24, 2024
    Author

    Can you enable DEBUG logging to see where the error might be?

    hmm, I do have following setting turned on for debug mode in settings, but I don't see errors that lead to the worker interruption issue. Anywhere elese I can enable DEBUG logging? thanks!

    log_level: LogLevel = LogLevel.DEBUG

  3. s3rius commented on Oct 24, 2024

    @s3rius
    s3rius
    on Oct 24, 2024
    Owner

    Can you supply taskiq worker cli with --log-level DEBUG argument?

    Like taskiq worker --log-level DEBUG ....

  4. rcholic commented on Oct 25, 2024

    @rcholic
    rcholic
    on Oct 25, 2024
    Author

    Can you supply taskiq worker cli with --log-level DEBUG argument?

    Like taskiq worker --log-level DEBUG ....

    I'm using docker-compose to start the worker like following:

      taskiq-worker:
    <<: *main_app
    labels: []
    command:
    - taskiq
    - worker
    - -fsd
    - my_app.tkq:broker

    to add log-level , is following correct?

      taskiq-worker:
    <<: *main_app
    labels: []
    command:
    - taskiq
    - worker
    - -fsd
    - --log-level DEBUG
    - my_app.tkq:broker

  5. s3rius commented on Oct 25, 2024

    @s3rius
    s3rius
    on Oct 25, 2024
    Owner

    Yes, should be correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions