These are chat archives for nightscout/intend-to-bolus

1st
Jan 2019
mkericson
@mkericson
Jan 01 00:14
Anyone having issues with Dexcom Share? Never lost the server connection before but just did earlier today. Doesnt connect over cell or wifi. Thinking it may be a server issue on Dexcon side. Thoughts?
Jon Cluck
@cluckj
Jan 01 00:32
yes, others are reporting it too
Teamhrach
@Teamhrach
Jan 01 00:40
Hi, I tried to get looping to work on my Pi today without success. I ran the OpenAPS install process a few times with no joy. I've copied the log below. Has anyone any suggestions as to what I could try next?

Last login: Mon Dec 31 22:49:29 on ttys002
Tomass-MacBook-Pro:~ tomasmahony$ ssh root@tomaspi.local
^[[A^[[A

^C
Tomass-MacBook-Pro:~ tomasmahony$ ssh root@tomaspi.local
root@tomaspi.local's password:
Permission denied, please try again.
root@tomaspi.local's password:
Last login: Mon Dec 31 22:18:25 2018 from 192.168.1.100

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@tomaspi:~# l
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/root/myopenaps/monitor/edison-battery.json' }
Could not parse suggested.json: { Error: ENOENT: no such file or directory, open '/root/myopenaps/enact/suggested.json'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.<anonymous> (/root/src/openaps-menu/scripts/status.js:88:35)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/root/myopenaps/enact/suggested.json' }
Listening for 26s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon 31 Dec 23:04:05 GMT 2018
Listening for 26 s silence before mmtuning: Listening for 26s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon 31 Dec 23:04:33 GMT 2018
mmtune: "868.250", 3, -62
waiting for 4 second silence before continuing
Listening for 4s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon 31 Dec 23:05:43 GMT 2018
Done waiting for rigs with better signal.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon 31 Dec 23:05:43 GMT 2018
grep: monitor/temp_basal.json: No such file or directory
Updating HAT Display...
Could not parse profile.json: { Error: ENOENT: no such file or directory, open '/root/myopenaps/settings/profile.json'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.<anonymous> (/root/src/openaps-menu/scripts/status.js:45:33)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/root/myopenaps/settings/profile.json' }
Could not parse edison-battery.json: { Error: ENOENT: no such file or directory, open '/root/myopenaps/monitor/edison-battery.json'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.<anonymous> (/root/src/openaps-menu/scripts/status.js:51:38)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/root/myopenaps/monitor/edison-battery.json' }
Could not parse suggested.json: { Error: ENOENT: no such file or directory, open '/root/myopenaps/enact/suggested.json'
at Object.fs.openSync (fs.js:646:18)
at Object.

Martin Haeberli
@mhaeberli
Jan 01 02:36
I have an Edison rig that WAS running fine, but no longer starts bluetoothd - no changes made (kind of like a few months ago when I updated a similar rig). -where is bluetoothd started? - how to debug
Dana Lewis
@danamlewis
Jan 01 02:56
@Teamhrach what happens with the install - does it appear to truncate or did it successfully finish installing? asking because it seems to not have gotten everything finalized
Teamhrach
@Teamhrach
Jan 01 11:13
@danamlewis the install appears to work ok. I tried it again this morning but got the same outcome. I've reproduced the code below with various codes removed.
Teamhrach
@Teamhrach
Jan 01 11:23
@danamlewis I've just realised that I cannot copy a large log text file into this gitter forum. I will FB message you the log instead
Craig Brenner
@cbrenner
Jan 01 12:25

Dexcom had a severe server outage yesterday for several hours (worst apparently in their history). For those of us pushing/pulling NS data to/from the cloud for OpenAPS, we were basically in open loop/manual mode for most of the afternoon through to midnight. Unfortunately, some other issues seems to have been created after the Dexcom outage as I am now getting perpetual NS App crashes on Heroku I have tried to clean up the MongoDB database and have switched to a new/clean database. I have restarted the Dynos multiple times. I have redeployed the NS app several times. Nothing seems to stop the App from crashing. Here is the error:

"2019-01-01T12:13:12.515856+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2018-12-31T12:13+0000&find[carbs][$exists]=true" host=alexanderbrennercgmsite.herokuapp.com request_id=3d20a814-5f65-49b7-8304-5b76b1c619e4 fwd="24.17.201.47" dyno= connect= service= status=503 bytes= protocol=https"

Any thoughts? Can't use OpenAPS until this gets resolved and I have exhausted the limits of my knowledge.

live4sw
@live4sw
Jan 01 12:46
@cbrenner Does Dexcom.com resolve for you? I found that once I changed my DNS server from the default to one of Google public DNS servers (8.8.8.8 or 8.8.4.4), everything worked.
All of the missed entries filled back up
Craig Brenner
@cbrenner
Jan 01 12:50
@live4sw Yep, Dexcom.com resolves fine.
live4sw
@live4sw
Jan 01 12:50
That error looks like a problem resolving the address, so I'd want to be sure that Share is back up and running for you to try to isolate if it's something else.
Craig Brenner
@cbrenner
Jan 01 12:51
@live4sw Share is up and running. Dexcom app on my son's phone is connected to the server and I can use the follow App to monitor.
Teamhrach
@Teamhrach
Jan 01 12:53
Hi, I've been trying to get my Raspberry Pi Ri to report to Papertrail without success (my Edison rig runs fig). Please see coding below - it is apparent where I am going wrong?
Craig Brenner
@cbrenner
Jan 01 12:53
@live4sw Error is now a bit different ….. "2019-01-01T12:52:26.780312+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/socket.io/?EIO=3&transport=polling&t=MW9UEqS" host=alexanderbrennercgmsite.herokuapp.com request_id=c0ac22b9-66f2-4a4c-9eee-4072d81403ea fwd="24.17.201.47" dyno= connect= service= status=503 bytes= protocol=https "
Teamhrach
@Teamhrach
Jan 01 12:53
root@tomaspi:~#
root@tomaspi:~# tar xzf ./remote_syslog*.tar.gz
root@tomaspi:~#
root@tomaspi:~#
root@tomaspi:~# cd remote_syslog
root@tomaspi:~/remote_syslog#
root@tomaspi:~/remote_syslog# sudo cp ./remote_syslog /usr/local/bin
root@tomaspi:~/remote_syslog#
root@tomaspi:~/remote_syslog# vi /etc/log_files.yml
root@tomaspi:~/remote_syslog# sudo remote_syslog
2019-01-01 12:50:10 ERROR config_manager.go:208 Could not parse the config file: YAML error: line 11: did not find expected key
2019-01-01 12:50:10 CRITICAL config_manager.go:145 Failed to configure the application: Could not parse the config file: YAML error: line 11: did not find expected key
live4sw
@live4sw
Jan 01 12:54
I'm not sure beyond that, but it is very clear that lots of people are having Heroku problems too (see https://www.facebook.com/groups/cgminthecloud/). So I'd probably keep an eye on there also for now.
I just had the Share outage all night (until I manually changed DNS servers to one on which Dexcom could be resolved). Others are having Heroku issues also, though I'm not having any issue with mine.
Craig Brenner
@cbrenner
Jan 01 13:00
@live4sw You changed the DNS server on your home router?
live4sw
@live4sw
Jan 01 13:00
Yes. Manually changed it to Google's DNS server
And then within about 5 minutes everything was fine
I'll just stick with that, it's probably better than my ISP's server in general anyway
Craig Brenner
@cbrenner
Jan 01 13:04
Hmm, okay. I think mine is defaulted to xfinity's DNS server as that is my provider. Let me change it and see if that resolves although outside of the house, it will change to our cell provider's DNS so may revert to same problem
live4sw
@live4sw
Jan 01 13:16
Yeah, it seems likely that the problem (at least on Dexcom's side) is that there was a change in their servers' IP addresses and that it takes time to propagate across all the DNS servers, and that some update faster than others.
May or may not be related to the Heroku issue.
philipgo
@philipgo
Jan 01 17:30
I found it quite shocking that the Android Dexcom app would not even open during the server outage. It kept collecting in the background, but it would not have been possible to start a new sensor.
Martin Haeberli
@mhaeberli
Jan 01 20:40
@philipgo :+1:
I had to re-start my heroku dynos - a few times; seemed to help each time
Dustin McGee
@McGeeDustin_twitter
Jan 01 20:42
Hello everyone, I'm new here. Interested in diy closed loop set up. Question i have-is the RileyLink only work with i-phone not android? Is there a different option I should be looking at? Thanks for any info.
Dana Lewis
@danamlewis
Jan 01 21:52
@McGeeDustin_twitter yes, rileylink + iPhone and the Loop app/algorithm. There may be an option to use the rileylink with AndroidAPS in the future but no ETA on that. The other option is hardware for an OpenAPS rig, where it doesn’t matter what phone you use.
Brett
@burgertime14
Jan 01 21:54
Just rebuild my old Pi3 tank from scratch. Installed dev first and it did not copy mmtune to Go-mmtune, nor did the .bash_profile get updated with the aliases. Installed master, everything worked, reinstalled dev and now everything is golden. Just wanted to get it recorded, in case others experience the same thing.