You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have manually deleted one of the key from redis DB to remove one of the task under archive state from queue. After doing this asynqmon metrics stopped working and Inspector methods aren't working to get info of tasks/queue.
The error I'm getting both for metrics and Inspector methods are as follows:
asynq UNKNOWN: UNKNOWN: redis eval error: ERR Error running script (call to f_0c80fc1868e3aae205155ae2017ce995a3a7cec0): @user_script:30: user_script:30: attempt to perform arithmetic on local 'bytes' (a boolean value)
To Reproduce
I've tried many ways to resolve this error:
Restarted the application to restart the asynq server and other instances.
Tried to manually insert the deleted key into redis DB again.
Tried moving some task to archive state and back to pending state again so that the lost keys can be recreated.
Nothing of these approaches worked. Since this issue was on production environment , i cannot flush all the redis DB data nor i cannot take any risky actions .
Has anyone else faced the same issue?
Can someone please tell me how do we resolve this issue?
The text was updated successfully, but these errors were encountered:
Describe the bug
I have manually deleted one of the key from redis DB to remove one of the task under archive state from queue. After doing this asynqmon metrics stopped working and Inspector methods aren't working to get info of tasks/queue.
The error I'm getting both for metrics and Inspector methods are as follows:
asynq UNKNOWN: UNKNOWN: redis eval error: ERR Error running script (call to f_0c80fc1868e3aae205155ae2017ce995a3a7cec0): @user_script:30: user_script:30: attempt to perform arithmetic on local 'bytes' (a boolean value)
To Reproduce
I've tried many ways to resolve this error:
Nothing of these approaches worked. Since this issue was on production environment , i cannot flush all the redis DB data nor i cannot take any risky actions .
Has anyone else faced the same issue?
Can someone please tell me how do we resolve this issue?
The text was updated successfully, but these errors were encountered: