Nightscout Issues

The free Nightscout we use also depends on a free database from mLab. The free database only has so much room...500 MB to be specific. After a period of time (it will vary, but usually on the order of months), your mLab database could reach its free limits. When that happens, your NS site may stop showing data properly. For example, you may notice your Share Bridge will not pull data and your site will be “stale”.

The good news? Loop can still run just fine until you repair your mLab database. The bad news? You just won’t be able to remotely monitor Loop through NS until you clear up some storage space in mLab.

Repair Process

Go to your Nightscout site's settings (the three horizontal bars in the upper right of your Nightscout site) and open your Admin Tools for the site. Click on the buttons to "Delete all documents" in your Clean Mongo status database section of the Admin Tools. For good measure, also click on the buttons for removing future items as well.

Now that you cleared out some database space, we can now make the database more efficient by "repairing" the database.

To begin the repair process, click on the mlab link in your Heroku site control panel.

Then click on the Tools tab in the screen that opens. Click on the commands button and then select the repairDatabase from the dropdown menu of available commands. At the bottom of the screen, select the Run Command button.

After a short time, you should get a return message of "ok" at the bottom of the command menu box. If you failed to clear out your Mongo status database before running this command, you will likely not get a successful repair and instead your pointer wheel will just keep spinning. Make sure you first clean out the database section as described above with your Nightscout Admin Tools.

You can verify that your database housekeeping was successful by returning to your NS site and waiting for the next Loop upload. You should see all your information back in with the next Loop run.