[GH-ISSUE #327] 500 (Internal Server Error): Redis cluster on Azure Redis enterprise returns 500 when calling queues endpoint #444

New issue

Open

opened 2026-03-07 22:15:30 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 22:15:30 +03:00

Owner

Originally created by @dinson on GitHub (May 16, 2024).
Original GitHub issue: https://github.com/hibiken/asynqmon/issues/327

I tried connecting asynqmon with Azure Redis enterprise cluster. Calling the queues endpoint results in 500 Internal Server Error with the following API response:

Request
curl --location 'http://127.0.0.1:8080/monitoring/api/queues'

API Response
UNKNOWN: redis eval error: ERR Error running script (call to f_0c80fc1868e3aae205155ae2017ce995a3a7cec0): @user_script:19: @user_script: 19: This Redis command is not allowed from scripts

Additional Info
Cluster: Enabled
TLS: Enabled
Redis Go Client version: v9
Azure Redis Cluster version: 6.0.17

PS: The same code works when connecting to Azure Redis cache without cluster enabled (with TLS).

Originally created by @dinson on GitHub (May 16, 2024). Original GitHub issue: https://github.com/hibiken/asynqmon/issues/327 I tried connecting asynqmon with Azure Redis enterprise cluster. Calling the `queues` endpoint results in `500 Internal Server Error` with the following API response: **Request** `curl --location 'http://127.0.0.1:8080/monitoring/api/queues' ` **API Response** `UNKNOWN: redis eval error: ERR Error running script (call to f_0c80fc1868e3aae205155ae2017ce995a3a7cec0): @user_script:19: @user_script: 19: This Redis command is not allowed from scripts` **Additional Info** Cluster: Enabled TLS: Enabled Redis Go Client version: v9 Azure Redis Cluster version: 6.0.17 PS: The same code works when connecting to Azure Redis cache without cluster enabled (with TLS).

kerem commented

2026-03-07 22:15:30 +03:00

Author

Owner

@dinson commented on GitHub (May 16, 2024):

Digging in revealed that this line is triggering the error in asynqmon code:

Line github.com/hibiken/asynq/internal/rdb/inspect.go #L340

res, err := memoryUsageCmd.Run(context.Background(), r.client, keys, argv...).Result()

@dinson commented on GitHub (May 16, 2024): Digging in revealed that this line is triggering the error in asynqmon code: Line github.com/hibiken/asynq/internal/rdb/inspect.go #L340 `res, err := memoryUsageCmd.Run(context.Background(), r.client, keys, argv...).Result()`

kerem commented

2026-03-07 22:15:30 +03:00

Author

Owner

@ajoga commented on GitHub (Oct 30, 2025):

Same on AWS Elasticache (redis-oss) for http://127.0.0.1:8080/api/queues using the default permissions with docker.io/hibiken/asynqmon@sha256:ac80bcffd2f9da20d15a8512fc96287e91e13558ad8718df367f0a0e0d0eda81:

UNKNOWN: UNKNOWN: redis eval error: ERR This Redis command is not allowed from script script: 0c80fc1868e3aae205155ae2017ce995a3a7cec0, on @user_script:19.

@ajoga commented on GitHub (Oct 30, 2025): Same on AWS Elasticache (redis-oss) for `http://127.0.0.1:8080/api/queues` using the default permissions with `docker.io/hibiken/asynqmon@sha256:ac80bcffd2f9da20d15a8512fc96287e91e13558ad8718df367f0a0e0d0eda81`: > UNKNOWN: UNKNOWN: redis eval error: ERR This Redis command is not allowed from script script: 0c80fc1868e3aae205155ae2017ce995a3a7cec0, on @user_script:19.