nats stream not found

[psandhu79]

From the go client app i am seeing the following message

nats: stream not found

From the server debug logs I see these messages

[64] 2022/07/06 15:50:09.641384 [DBG] 127.0.0.6:52529 - cid:83 - Client connection created
65
[64] 2022/07/06 15:50:09.662080 [DBG] 127.0.0.6:52529 - cid:83 - "v1.13.0:go" - Client connection closed: Client Closed
64
[64] 2022/07/06 15:50:17.698137 [DBG] 127.0.0.6:40551 - cid:84 - Client connection created
63
[64] 2022/07/06 15:50:17.735794 [DBG] 127.0.0.6:40551 - cid:84 - "v1.13.0:go" - Client connection closed: Client Closed
62
[78] 2022/07/06 15:50:18.092139 [DBG] 127.0.0.6:55219 - cid:220 - "v1.14.0:go" - Client Ping Timer
61
[78] 2022/07/06 15:50:18.092180 [DBG] 127.0.0.6:55219 - cid:220 - "v1.14.0:go" - Delaying PING due to client activity 0s ago

I have around 40 services i guess around 30-35 connect properly and a couple do not , but cannot understand why

[psandhu79]

Including a image of the nats jetstream dashboard

[caleblloyd]

what version of nats-server? If it is <2.8.4 can you try upgrading to the latest?

[psandhu79]

@caleblloyd is it nats:2.8.4-alpine3.15

[caleblloyd]

if you run the nats CLI against it, and do nats stream info on the streams that flaky in the app, does it work?

if you are running the official helm chart you can enable the nats-box pod, which has the nats CLI.

try targeting each server in the cluster independently to see if it is a problem with a particular server

[caleblloyd]

Closing due to age of issue; if experiencing in current versions please open a new issue.