@dar-kod Wow, good job! Any other tips that all of us should be aware of?? I guess you followed Guide to Migrating a Sandbox Heroku Add-on to Atlas?
Yes, I followed that instruction. But I found also that I have to input
Heroku app -> Settings -> "Config Vars" MONGO_CONNECTION with value:
mongodb+srv://clustername:<password>@heroku-cnjm1bzt.q1dxj.mongodb.net/<dbname>?retryWrites=true&w=majority
<password> and <dbname> have to be replaced with that from cloud.mongodb.com -> "Project settings" -> "Database Access".
@dar-kod Did you do the Test Migration stage? In the instructions, it says to use the mongo shell to test the connection string which they include in the popup Test Migration stage. I used
./mongo mongodb+srv://<username>:<password>@<clustername>.mqupg.azure.mongodb.net/<database>?retryWrites=true&w=majority replacing the <...> with my configuration, but I get 'No matches for <connection string>' . I'm sure I am using the correct parameters. Any idea?
@dar-kod Sorry, resolved! Missing quotes around the connection string in the the mongo command. Hwr, I guess I am using the wrong username because mongo returns
user is not allowed to do action [getLog] on [admin.] Anyway, making progress!
As of 5pm PDT today, my wife's nightscout site on Herokuapp.com is reporting "DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor" and the connection to mongoDB is not starting. I just now upgraded to the latest "master" branch, restarted dynos, and it's still not working. Any ideas?
Hi community, i'm in trouble with mongodb atlas. Yesterday I migrated with success from Mlab to MongoAtlas without problems. During the night the cluster stop working and now I'm not able to connect. On the web interface the primary host has a warning and is not accessible. What I can to avoid to lose all the data before terminate the instance?
Is this a good place to ask about the nightscout .js internals? I have installed my own mongodb and my own nightscout using node.js and everything seems to be working fine. I get "Listening on port 80" and no errors upon startup, but when I try connecting to the site, it just resets the connection. I'd like to turn on some internal debugging/logging so I can see what's happening. I searched all through the code and docs, but can't find reference anything. Anyone know?
Is there any directions from the community?
Marta, I followed this condensed guide: https://wolke.rueth.info/index.php/s/NjjgCF9rdbiWNbX#pdfviewer and it worked for me. Its the same guide that miki linked to, just smaller.
@miki3421 can I jump in here? I was attempting to migrate from sandbox to atlas and had an internet crash. I'm now stuck not looping. I'm trying to learn if my rig needs to be pointed in a different direction or... my old NS site is now read only and I'm not sure what to do. Mlab said I made it to step # 10 in the migration guide... sorry for being so slow on this.. I'm usually low maintenance!
hi @cobalt027 ...I've just gone over your guide and it illustrates where I messed up...I'm going to retry... thanks for taking the time to do the guide!
@solomonT1 from what app are you getting the error? I'm confused as to where your problem lies. perhaps a screenshot to illustrate?
Hmm. I have no idea how to test connectivity. I tried. Downloaded mongo shell on my computer, extracted it, opened it... And a small window appeared briefly on the screen, then it disappeared and I never figured out what it was, where it went, or how to use it once I did happen to locate it. Am I the only noob who feels a little bit abandoned by the devs here? I have yet to even receive any notifications about Any Of This, from Anyone. Thank goodness I just happened to wander onto mlab yesterday...
@nicoleloop I guess you're at section D step 7 of these instructions - https://docs.mlab.com/how-to-migrate-sandbox-heroku-addons-to-atlas/?fbclid=IwAR1hhkMok4XqFdu6SXi1uJMhjycO39nwNzrJal-0OZvMSAXseFqoZOPuwlI
If so mongo shell runs in a shell - windows command prompt or powershell, linux terminal etc.
I then ran the following command in the shell (windows powershell) .\mongosh.exe "mongodb+srv://<username>:<password>@<node>/<database>?retryWrites=true&w=majority" - the bit in quotes is the connection string provided in your migration process
you can then enter something like the following commands to check you have a connection
ent = db.getCollection("entries")
ent.countDocuments()
this should return the number of documents in your blood glucose collection and shows you have connectivity...
good luck...
If so mongo shell runs in a shell - windows command prompt or powershell, linux terminal etc.
I then ran the following command in the shell (windows powershell) .\mongosh.exe "mongodb+srv://<username>:<password>@<node>/<database>?retryWrites=true&w=majority" - the bit in quotes is the connection string provided in your migration process
you can then enter something like the following commands to check you have a connection
ent = db.getCollection("entries")
ent.countDocuments()
this should return the number of documents in your blood glucose collection and shows you have connectivity...
good luck...
@cameronrenwick depending on the instructions you used did you do the connection test (section D step 7 in the ones I followed) this will prove your atlas connection string...
@cameronrenwick cluster name is displayed on the 'Clusters' screen, there was nothing I can remember to stop the cluster being named the same as the db so you could be fine, I just try never to give two things the same name as I'm easily confused!!
It's OK to do the connection test with mongo shell at any time - I've just rerun mine to check in exactly the same way as I did before.
You can get confirmation of your connection string by clicking the connect button just below the cluster name on the Clusters screen...
It's OK to do the connection test with mongo shell at any time - I've just rerun mine to check in exactly the same way as I did before.
You can get confirmation of your connection string by clicking the connect button just below the cluster name on the Clusters screen...
@cameronrenwick mine has a node of <5 random chars>.azure.mongodb.net - the one you posted is missing the azure but you may have selected a different hosting option to me...