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
Versions of nats-server and affected client libraries used:
nats-server 2.9.14
nats-box 0.13.4
OS/Container environment:
Kubernetes with official Helm chart
Steps or code to reproduce the issue:
Tried reproducing this in a similar 3-node setup on Kubernetes, but sadly wasn't able to.
Normally, when doing a nats server report connections with a user under $SYS this command always successfully returns a report in the CLI. However, when running this with a non-$SYS account, this command may sometimes succeed, and other times it will lead into an error message in the CLI:
nats: error: server request failed, ensure the account used has system privileges and appropriate permissions
When running this command quite rapidly after each other, it sometimes will result in a panic. (Although I'm not quite sure if it's even related to running this quickly, or if it's a race condition.)
Defect
Versions of
nats-server
and affected client libraries used:OS/Container environment:
Steps or code to reproduce the issue:
Tried reproducing this in a similar 3-node setup on Kubernetes, but sadly wasn't able to.
Normally, when doing a
nats server report connections
with a user under$SYS
this command always successfully returns a report in the CLI. However, when running this with a non-$SYS
account, this command may sometimes succeed, and other times it will lead into an error message in the CLI:When running this command quite rapidly after each other, it sometimes will result in a panic. (Although I'm not quite sure if it's even related to running this quickly, or if it's a race condition.)
The following panic happened:
Expected result:
Consistently return data that can be shown in the CLI report.
Actual result:
May panic a server, making it restart.
The text was updated successfully, but these errors were encountered: