Open galaviz-lip opened 4 years ago
Are there any errors on the uploader log screen on the phone?
Thanks Pogman for the reply. I tried yesterday to upload a picture, but Safari did not let me. I am trying it now with Chrome. I do not see any errors on the uploader (the picture was taken yesterday evening), turning the whole thing more puzzling. Thanks for your help!
Ok this looks like it could be a full mongo database. The limit is 500mb and can fill over time depending on pump type and features used. Nightscout will report a success when data is sent even in this situation.
Go into your NS website admin page and clean some of the old data out.
Thanks Pogman!
Sorry to have created a comment and probably closing it so rapidly. Yesterday, out of doubts, I had created an alternative NS site on my Heroku space, and after not being able to upload data, linked it to the same Atlas database. I could see on both sites the same data, but not upload any from the cell phone.
This morning, waiting for your suggestion (which most probably it was correct) I deleted the app I created yesterday, and suddenly it started to upload! I am not sure if my action liberated some space (it probably did), but the correlation with the repair is too strong.
Summary: I do not know what did I do to repair it, but it works now.
Again, thanks a lot for your support! And sorry for stealing some of your time.
Hello, I hav a similar issue with the uploader after migrate my mondodb to Atlas.
I update the nightscout app to 14.0.3 version, and then made the migration according to Mongo-Atlas web page instructions.
I made the changes adding the new VAR "MONGO_CONNECTION".
My nightscout site is available, the size of my DB is less than 100MB. But while I try to delete data as recommend above I receive an error message.
The error log of the 600 serie uploader shows this:
Any help?
Check out this guide direct from mLab and pay particular attention to the mongo string to set in heroku convig vars.
https://docs.mlab.com/how-to-migrate-nightscout-sandbox-heroku-addons-to-atlas/
It may help to join the "nightscout for medtronic" facebook group for help with transition problems.
The uploader log only knows what a nightscout server tells it and in your case all we get is the "internal server error" response,
Saludos. En mi caso, no se comunica con la bomba. Es la primera vez que conecto el Contour next link al móvil
@VanesaRL Can you please open a separate new issue with some more detailed information (messages from the pump, etc)? It looks like your problem has nothing to do with Atlas (this issue).
Your Environment
Brief Explanation of Issue
HI! I know a similar issue is closed, but now I have exactly the same problem after migrating to Atlas. My cell phone uploader cannot send any data the the DB. I can though upload svg values manually (and see them on the my NS site) using the script by: https://github.com/cjo20/ns-api-uploader
I am not sure what really happened with the uploader. Any help is certainly appreciated. Thanks!
Uploader Error Code
Do not know if there is an error. Here are the last lines from the Heroku CLI:
2020-09-03T21:02:44.941092+00:00 app[web.1]: got data-received event, requesting reload 2020-09-03T21:02:45.082527+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:read 2020-09-03T21:02:45.086667+00:00 heroku[router]: at=info method=GET path="/api/v1/treatments.json?find%5Bcreated_at%5D%5B%24gte%5D=2017&find%5Bcreated_at%5D%5B%24lte%5D=2020-09-02T20%3A57%3A10Z&find%5Bkey600%5D%5B%24regex%5D=ALARM&count=20" host=kiki-vigilante-last.herokuapp.com request_id=e9db5f84-85c8-40ea-8e8c-1506fcf35d0d fwd="82.154.141.140" dyno=web.1 connect=0ms service=7ms status=200 bytes=1318 protocol=https 2020-09-03T21:02:45.235428+00:00 heroku[router]: at=info method=DELETE path="/api/v1/treatments/5f4e8bee5987e50805f2cbc8" host=website.herokuapp.com request_id=434d67cc-ba36-436b-a923-3151add424cc fwd="82.154.141.140" dyno=web.1 connect=0ms service=3ms status=200 bytes=230 protocol=https 2020-09-03T21:02:45.235601+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:read 2020-09-03T21:02:45.235674+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:delete 2020-09-03T21:02:45.235900+00:00 app[web.1]: got data-received event, requesting reload 2020-09-03T21:02:45.392514+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:read 2020-09-03T21:02:45.392666+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:delete 2020-09-03T21:02:45.392936+00:00 app[web.1]: got data-received event, requesting reload 2020-09-03T21:02:45.393565+00:00 heroku[router]: at=info method=DELETE path="/api/v1/treatments/5f4e30845987e50805b05d95" host=website.herokuapp.com request_id=f97db33b-2608-469f-8d8e-dce68adf3c35 fwd="82.154.141.140" dyno=web.1 connect=0ms service=5ms status=200 bytes=230 protocol=https 2020-09-03T21:02:45.543530+00:00 heroku[router]: at=info method=DELETE path="/api/v1/treatments/5f4e19135987e508059e4259" host=website.herokuapp.com request_id=b2279bed-0fd6-4048-a441-07b3b29842e2 fwd="82.154.141.140" dyno=web.1 connect=0ms service=3ms status=200 bytes=230 protocol=https 2020-09-03T21:02:45.543680+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:read 2020-09-03T21:02:45.543756+00:00 app[web.1]: GRANTED: 82.154.141.140 api-secret api:treatments:delete 2020-09-03T21:02:45.543956+00:00 app[web.1]: got data-received event, requesting reload
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Severity Score
4