[GH-ISSUE #149] need log more info when http status 500 #731

Closed
opened 2026-03-15 21:22:32 +03:00 by kerem · 5 comments
Owner

Originally created by @qiuyuzhou on GitHub (Aug 26, 2021).
Original GitHub issue: https://github.com/hibiken/asynqmon/issues/149

"GET /api/queues HTTP/1.1" 500 214

asynq: 0.18.4
asynqmon: 0.2.2

Originally created by @qiuyuzhou on GitHub (Aug 26, 2021). Original GitHub issue: https://github.com/hibiken/asynqmon/issues/149 ``` "GET /api/queues HTTP/1.1" 500 214 ``` asynq: 0.18.4 asynqmon: 0.2.2
kerem closed this issue 2026-03-15 21:22:37 +03:00
Author
Owner

@qiuyuzhou commented on GitHub (Aug 26, 2021):

image

Sections Severs, Schedulers, Redis work well.

<!-- gh-comment-id:906064854 --> @qiuyuzhou commented on GitHub (Aug 26, 2021): ![image](https://user-images.githubusercontent.com/2310221/130895891-ff781666-e928-491b-8bbb-6acf10f68ed4.png) Sections `Severs`, `Schedulers`, `Redis` work well.
Author
Owner

@qiuyuzhou commented on GitHub (Aug 26, 2021):

Upgrade asynq from 0.15.0 to 0.18.4 recently.

<!-- gh-comment-id:906074209 --> @qiuyuzhou commented on GitHub (Aug 26, 2021): Upgrade asynq from 0.15.0 to 0.18.4 recently.
Author
Owner

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

Hi @qiuyuzhou, thank you for opening an issue!
Since we are still in v0, we sometimes make breaking changes without a major version bump.
Please check the releases page (https://github.com/hibiken/asynq/releases) whenever you update. I always make sure to include what's changed and guide to update if needed.

You should be able to go from 0.15.x to 0.17.x easily. Once you confirmed that things are working in v0.17.x then please follow this update guide at https://github.com/hibiken/asynq/wiki/Version-Upgrade-Guide-(from-0.17-to-0.18).

Let me know if you run into any issues!

<!-- gh-comment-id:906381353 --> @hibiken commented on GitHub (Aug 26, 2021): Hi @qiuyuzhou, thank you for opening an issue! Since we are still in v0, we sometimes make breaking changes without a major version bump. Please check the releases page (https://github.com/hibiken/asynq/releases) whenever you update. I always make sure to include what's changed and guide to update if needed. You should be able to go from 0.15.x to 0.17.x easily. Once you confirmed that things are working in v0.17.x then please follow this update guide at https://github.com/hibiken/asynq/wiki/Version-Upgrade-Guide-(from-0.17-to-0.18). Let me know if you run into any issues!
Author
Owner

@qiuyuzhou commented on GitHub (Aug 26, 2021):

Thanks.

I have upgraded asynq client and server to v0.18.4 before migrate the data. This would cause dirty data for migration?

❯ asynq migrate -n 3
(error): Server(s) still running. Please ensure that no asynq servers are running when runnning migrate command.
❯ asynq migrate -n 3
error: Failed to get stats: UNKNOWN: UNKNOWN: redis eval error: ERR Error running script (call to f_d2725d6f7a40c52b2534b2526b30a74d28fe023e): @user_script:30: user_script:30: attempt to perform arithmetic on local 'bytes' (a boolean value)
*** Please report this issue at https://github.com/hibiken/asynq/issues ***
<!-- gh-comment-id:906716991 --> @qiuyuzhou commented on GitHub (Aug 26, 2021): Thanks. I have upgraded asynq client and server to v0.18.4 before migrate the data. This would cause dirty data for migration? ``` ❯ asynq migrate -n 3 (error): Server(s) still running. Please ensure that no asynq servers are running when runnning migrate command. ❯ asynq migrate -n 3 error: Failed to get stats: UNKNOWN: UNKNOWN: redis eval error: ERR Error running script (call to f_d2725d6f7a40c52b2534b2526b30a74d28fe023e): @user_script:30: user_script:30: attempt to perform arithmetic on local 'bytes' (a boolean value) *** Please report this issue at https://github.com/hibiken/asynq/issues *** ```
Author
Owner

@qiuyuzhou commented on GitHub (Aug 26, 2021):

Thanks again.

I have run flushdb

<!-- gh-comment-id:906755536 --> @qiuyuzhou commented on GitHub (Aug 26, 2021): Thanks again. I have run `flushdb`
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/asynqmon#731
No description provided.