-
Notifications
You must be signed in to change notification settings - Fork 364
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
{"externalError":"connection-closed","methodArray":[{"find":[{}]},...,"level":"error","message":"[connection-error]"} #555
Comments
Hello @ashwatthb this means nosqlclient has lost the connection to MongoDB, did you encounter this again after refreshing collections? |
Hi @rsercano Thanks for your swift reply. Yes, I tried multiple times and the behaviour is same. We are running nosqlclient for around a year and there was no issues. I tried to reproduce by connecting to different databases, and the issue is same. |
Did you update the nosqlclient version ? |
I was running the version 4.0.0, after this issue tried upgrading to 4.0.1 both versions has the same behaviour. |
Can you please share nosqlclient logs by not giving the sensitive part @ashwatthb ? |
Please find the logs below
|
Interesting, I cant see a reason why it fails, I'll check this deeply thanks |
Hi @ashwatthb I suspect this's related with your MongoDB setup and connection, since we literally changed nothing on our side, could you please recheck, I couldn't find a proper reason actually. |
we are running nosqlclient on kubernetes cluster and we have this error while trying to execute query again statefulset.
on console i have this error:
[1007] Please refresh collections or re-connect, connection has been closed
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: