[GH-ISSUE #311] I can’t view the specific status of the task operation these days. What is the reason? #2155

Closed
opened 2026-03-15 19:26:18 +03:00 by kerem · 5 comments
Owner

Originally created by @LINJINTIANDE on GitHub (Aug 13, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/311

Originally assigned to: @hibiken on GitHub.

I can’t view the specific status of the task operation these days. What is the reason?
As long as there is running in the queue, you cannot see the data running redis
image
image

Originally created by @LINJINTIANDE on GitHub (Aug 13, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/311 Originally assigned to: @hibiken on GitHub. I can’t view the specific status of the task operation these days. What is the reason? As long as there is running in the queue, you cannot see the data running redis ![image](https://user-images.githubusercontent.com/42436479/129318089-db2711a3-8413-4370-9868-31e878c2d6fb.png) ![image](https://user-images.githubusercontent.com/42436479/129322427-762dbe17-32f1-4875-be93-bc59cb224f11.png)
kerem 2026-03-15 19:26:18 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@hibiken commented on GitHub (Aug 14, 2021):

Hi @LINJINTIANDE, thank you for opening this issue.

Which version of asynq package and asynqmon are you using?
This may be version compatibility issue.

<!-- gh-comment-id:898807090 --> @hibiken commented on GitHub (Aug 14, 2021): Hi @LINJINTIANDE, thank you for opening this issue. Which version of asynq package and asynqmon are you using? This may be version compatibility issue.
Author
Owner

@LINJINTIANDE commented on GitHub (Aug 14, 2021):

ansyq v0.17.1 ,asynqmon is the latest version

<!-- gh-comment-id:898895988 --> @LINJINTIANDE commented on GitHub (Aug 14, 2021): ansyq v0.17.1 ,asynqmon is the latest version
Author
Owner

@LINJINTIANDE commented on GitHub (Aug 14, 2021):

Upgrade asynq v0.18.3, check the queue details, the following error occurred
image
image

<!-- gh-comment-id:898899653 --> @LINJINTIANDE commented on GitHub (Aug 14, 2021): Upgrade asynq v0.18.3, check the queue details, the following error occurred ![image](https://user-images.githubusercontent.com/42436479/129449043-31c267b1-8091-41bd-9ced-ce15a1a089a3.png) ![image](https://user-images.githubusercontent.com/42436479/129449053-21e1f80a-154d-40a1-933d-212e02a3eaa7.png)
Author
Owner

@hibiken commented on GitHub (Aug 14, 2021):

I see. This has come up a number of times; asynq 0.17.x is compatible with asynqmon 0.1.x.
(If you are using docker, I'd suggest you pin the version number of the image).

When you upgrade from asynq 0.17 to 0.18, did you follow the guide at https://github.com/hibiken/asynq/wiki/Version-Upgrade-Guide-(from-0.17-to-0.18)?

<!-- gh-comment-id:898905138 --> @hibiken commented on GitHub (Aug 14, 2021): I see. This has come up a number of times; asynq 0.17.x is compatible with asynqmon 0.1.x. (If you are using docker, I'd suggest you pin the version number of the image). When you upgrade from asynq 0.17 to 0.18, did you follow the guide at https://github.com/hibiken/asynq/wiki/Version-Upgrade-Guide-(from-0.17-to-0.18)?
Author
Owner

@LINJINTIANDE commented on GitHub (Aug 14, 2021):

Upgrade to asynq v0.18.3 is normal, thank you for your reply

<!-- gh-comment-id:898905703 --> @LINJINTIANDE commented on GitHub (Aug 14, 2021): Upgrade to asynq v0.18.3 is normal, thank you for your reply
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#2155
No description provided.