NoKeysError: nats: no keys found
error, but kv has keys
#686
Unanswered
kevinhikaruevans
asked this question in
Q&A
Replies: 1 comment 3 replies
-
Hi @kevinhikaruevans, What version of nats-server do you have? I had the same issue of |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm receiving this fluke 'no keys found' error. It's odd though because this rarely seems to happen and the other async tasks loaded the keys without issue.
But what's also strange is the kv store should definitely have keys in it. I can see them when using
nats kv ls
. Here's the code that I'm using:I would assume at the minimum, the
last_retrieved
key should definitely be in there.I'm using
nats-py
version2.8.0
with the nats:alpine (v2.11.1) Docker image. What would cause this error to occur? Should I be initializing this differently?Beta Was this translation helpful? Give feedback.
All reactions