-
Notifications
You must be signed in to change notification settings - Fork 88
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
MongoError - Topology was destroyed #442
Comments
Thanks for the report! It could be some kind of problem in the IOTA connection to DB or in the DB itself. Maybe the logs of the IOTA could provide some useful information to help debugging this issue (the log can be long and verbose... I'd suggest to look near the timestamp when the problem starts to happen). |
Here it is a message from the log when this error happens:
|
Which values do you have in your configuration for server.reconnectTries and server.reconnectInterval? Have you tried the advice of increasing them in order to see if the problem disappears? |
Where are these configurations ? Which is the involved component ? (iotAgent or Mongodb ?) |
It corresponds to the mongodb.retries and mongodb.retryTime in config.js or IOTA_MONGO_RETRIES IOTA_MONGO_RETRY_TIME env vars (depending on the configuration style you are using). The mongodb configuration is described in https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/installationguide.md:
|
Following your suggestion, I put 2 environment variables with these value: IOTA_MONGO_RETRIES=10 on the agent configuration, but the problem happens again. Do you know what can be the correct values to insert? I'm still using the version 1.5.0 |
This version is pretty old... Could you test with the newest one (1.12.0) please? |
Sometimes it happens that all calls to the agent don't work, The system returns this response
Restarting the agent the error disappears.
I'm using version 1.5.0
The text was updated successfully, but these errors were encountered: