-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebUI not loading Queues #296
Comments
I have the same issue, I ran flushall, but it didn't solve my issue either. |
Facing the same issue.. It momentarily shows the active task.. That's all I get.. There is no archive task coming in.. |
I looked at the call graph for the
Since the issue is the "bytes", then I guess more specifically here:
running asynqmon v0.7.2 This part of the code is asynq code (internal/rdb/inspect.go). All calls to |
any fix for this issue |
the redis connected but cannot get the queues |
@Psuta90 share logs from the asynqmon server. |
i try to scheduled task is success in terminal manualjobs is succes but in asynqmon is not showing the queues in the sidebar server is showing but i click is not working like previous picture |
"time":"2023-10-13T07:13:46.906285637Z","id":"","remote_ip":"172.18.0.1","host":"localhost:3005","method":"GET","uri":"/monitoring/tasks/api/queues/default/active_tasks?page=1&size=100","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36","status":500,"error":"","latency":491845,"latency_human":"491.845µs","bytes_in":0,"bytes_out":23} |
I also encountered the same issue. The asynqmon can connect to redis but unable to load queue data. I'm using asynq v0.24.1 and asynqmon v0.7.2. Here's the log from asynqmon
thanks |
Just want to give an update. my asynq and asynqmon setup works now after i run |
does not work for me. |
Hi 👋🏿,
I'm on running asynq: 0.23.0 and asynqmon: 0.7.1 in my production environment and I have been unable to access the Web UI, when this happened in the past running
flushall
in redis fixed it (got the idea from #149), but I can't afford to do that now as I am storing other things in redis.What do you think caused this (so I can prevent this from happening in the future) and how can I get it to work without clearing all the keys?
I attached a screenshot of the error. Thanks in advance.
The text was updated successfully, but these errors were encountered: