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

19th
Feb 2018
mariano42
@mariano42
Feb 19 2018 02:19
Apologies if I missed the resolution to this in the docs, but last night I lost power to my Edison and it must have corrupted something and it ended up putting my file system into read only mode. I have been googling and trying to figure out how to get it back to writeable, but nothing has worked yet. Does anyone have any ideas? Or could point me in the right direction?
Deweyoxberg
@Deweyoxberg
Feb 19 2018 03:06

@danamlewis : question please. What's the timeout threshold for communications? I don't believe the rig is re-attempting in one second and timing out a second time:

Feb 18 19:03:54 localhost Timed: out or other comms error - Received an error response Timeout - retrying: 1 of 3
Feb 18 19:03:54 localhost Timed: out or other comms error - Received an error response Timeout - retrying: 2 of 3
Feb 18 19:03:57 localhost Timed: out or other comms error - Received an error response Timeout - retrying: 3 of 3

Also this seems to be a very frequent error and really messing with looping reliably. Beyond battery/proximity/case material, what else can I look at?

Dana Lewis
@danamlewis
Feb 19 2018 03:27
Look at pump-loop.log (l)
Doug
@dougboss
Feb 19 2018 03:40

Well I'm not sure what kicked it off but Papertrail is working -
best guess is that, I found the troubleshooting section of PT website and ran these test log steps
$ touch /tmp/testfile
$ remote_syslog -d logsN.papertrailapp.com -p XXXXX -D /tmp/testfile

Somehow that kicked off the communication to PT - WOO fricken HOO

Deweyoxberg
@Deweyoxberg
Feb 19 2018 03:47
@danamlewis : Can you be more specific please? 1) How am I looking at said log and 2) what am I looking for
(@dougboss glad you got it working! I don't use papertrail so not a lot of troubleshooting help but if you think that's likely a common error for others, might be worth PRing a note about it into the docs)
Doug
@dougboss
Feb 19 2018 03:52
@danamlewis logs have stopped again ...Im looking a little deeper - ill see what I find - logs have stopped again ... Funny thing is the insulin part is working - its the logs that arent. Am Im in IT - I should know logs ...
Edit - looks like a reboot got them going again ... Im less than 24 hours in this... I see if I can find more details of what my error was so I can share if it makes sense... THANKS again.
Dana Lewis
@danamlewis
Feb 19 2018 03:57
:+1:
Deweyoxberg
@Deweyoxberg
Feb 19 2018 04:02
@danamlewis : Ok, so the log runs through a bunch of success messages for RileyLink, then does an mmtune, finds a signal, then says unsuccessful pump loop. There's a delay of about 5 seconds, then the loop starts again, runs through the whole sequence again. Preflight is fine, then there's some errors about accessing /tmp/pump_loop_completed (no such file), then an error about refresh_old_umphistory_24h, then the cycle repeats with RileyLink again.
It does this repeatedly and doesn't go anywhere.
Rebooting the rig works for about two minutes then back to the problem.
Dana Lewis
@danamlewis
Feb 19 2018 04:04
Please paste some of the logs. Often there's some clues there we can spot about what might be wrong. Summarizing will leave the key parts out.
Deweyoxberg
@Deweyoxberg
Feb 19 2018 04:04
uh... okay, they're screenshots as the rig is on the other side of the planet but here goes :P
image.png
^ there we go
Goes through all of that then repeats the riley bit. over and over.
Not knowing anything, I've always wondered why this rileylink business needs to do its thing 8,9 even 10 times in a row. isn't once enough? :)
Dana Lewis
@danamlewis
Feb 19 2018 04:20
The refresh valueerror: needs values to unpack, means it hasn't gotten a good pump read. That error should self resolve with the next good read.
Deweyoxberg
@Deweyoxberg
Feb 19 2018 04:21
That's what I'm trying to get at: We're not getting reads from the pump.
Keeps timing out.
But there's no reason for it. And for the log to say timed out twice in the same second, did it even try?
Deweyoxberg
@Deweyoxberg
Feb 19 2018 04:49
manual mmtune spits back right away with a signal. looks good there.
image.png
Scott Leibrand
@scottleibrand
Feb 19 2018 04:59
Is this a brand new pump? Does it have any temp basals or boluses yet?
Deweyoxberg
@Deweyoxberg
Feb 19 2018 05:00
Not a brand new pump, have looped successfully before, has both basals and boluses.
the communication problem crops up from time to time. Some days, no issue. Other days, hell.
Scott Leibrand
@scottleibrand
Feb 19 2018 05:05
Have you tried reflashing radio chip with ccprog, and reseating the Edison on the EB?
Deweyoxberg
@Deweyoxberg
Feb 19 2018 05:11
brain's shot for now, going to get some sleep. tackle it again tomorrow. Rebooted it for now as a hail mary, unlikely to fix the issue. Considering wiping the rig and reflashing.
Scott Leibrand
@scottleibrand
Feb 19 2018 05:11
Have you tried reseating the Edison on the EB? Or running ccprog?
Deweyoxberg
@Deweyoxberg
Feb 19 2018 05:12
Reseating no, was something Im considering along with the flash. ccprog: what is that?
Scott Leibrand
@scottleibrand
Feb 19 2018 05:18
There’s an entire troubleshooting section in the docs you should read.
Dana Lewis
@danamlewis
Feb 19 2018 05:21
Yea. Ccprog is 3 quick commands. But I would try reseating first.
Deweyoxberg
@Deweyoxberg
Feb 19 2018 05:21
ok; will give it a go in the morning.
Thank you both :)
Dana Lewis
@danamlewis
Feb 19 2018 05:24
:+1:
mariano42
@mariano42
Feb 19 2018 15:19
Any Linux experts have any suggestions on how to get my file system out of read only mode? Fsck
Sorry, premature send. Fsck finds a dirty bit but I have no idea how to fix it. Mounting and remounting didn't work either
Scott Leibrand
@scottleibrand
Feb 19 2018 16:06
Would it be easier to just reflash the rig?
mariano42
@mariano42
Feb 19 2018 16:24
I was hoping to avoid that, but it seems as if that's my only option at this point. Dang!
thisistw
@thisistw
Feb 19 2018 16:52
Any help appreciated: rig stopped looping and I believe it has run out of space? I have tried the troubleshooting guide, but can't install ncdu and "df -h" returns:
Filesystem Size Used Avail Use% Mounted on
/dev/root 1.4G 1.4G 0 100% /
devtmpfs 480M 0 480M 0% /dev
tmpfs 481M 0 481M 0% /dev/shm
tmpfs 481M 13M 468M 3% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 481M 0 481M 0% /sys/fs/cgroup
tmpfs 481M 16K 481M 1% /tmp
/dev/mmcblk0p7 32M 5.1M 27M 16% /boot
/dev/mmcblk0p10 1.3G 805M 487M 63% /home
tmpfs 97M 0 97M 0% /run/user/0
I tried "logrotate -f /etc/logrotate.conf" but I get an error creating output file
benjaminbake
@benjaminbake
Feb 19 2018 17:14
I have tried re-installing oref0 and running the setup fresh as well as re flashing the the radio.
I discovered if I am actively pressing buttons when the mmtune takes place in log that I get a good radio signal. However if the pump is left alone I get the 0,-99 error. Ive never had a working rig but I spoke with the past pump owner who confirmed he was able to loop with this pump. Any ideas before I scrap this project?
Dana Lewis
@danamlewis
Feb 19 2018 17:22
@benjaminbake have you double checked to make sure you've got the right region for the pump in setup? (E.g. If it's a North America pump vs a ww pump?)
benjaminbake
@benjaminbake
Feb 19 2018 17:22
yes

Starting basal-only pump-loop at Mon Feb 19 11:17:02 CST 2018:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory: mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
grep: monitor/temp_basal.json: No such file or directory
Error, retrying
pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.684", 5, -57 No wait required.

Starting basal-only pump-loop at Mon Feb 19 11:20:44 CST 2018:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory: IndexError: bytearray index out of range
grep: monitor/temp_basal.json: No such file or directory
Error, retrying
pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.636", 0, -99 waiting for 78 second silence before continuing

first mmtune I was pressing the up arrow repeatedly. 2nd mmtune I left pump alone.
Scott Leibrand
@scottleibrand
Feb 19 2018 17:25
there was someone else who reported that "mmtune only works when pressing pump buttons" behavior, but I don't recall what they ended up figuring out about it.
Dana Lewis
@danamlewis
Feb 19 2018 17:36
Is mysentry turned on, do you have a remote id set in the pump (even 11111)?
benjaminbake
@benjaminbake
Feb 19 2018 17:40
What is mysentry? In utilities I have remote options, on, with 3 IDs 000000, 123456, 999999.
@scottleibrand I was able to see your discussion with someone back in sept 2016 but didn't see any resolution.
katie disimone
@Kdisimone
Feb 19 2018 17:52
@benjaminbake is on a 512 @danamlewis
Sorry…late to the convo
Scott Leibrand
@scottleibrand
Feb 19 2018 18:07
@benjaminbake who was that with?
benjaminbake
@benjaminbake
Feb 19 2018 18:08
@garykidd
Scott Leibrand
@scottleibrand
Feb 19 2018 18:30
I think he still hangs out here occasionally, so hopefully he’ll chime in.
benjaminbake
@benjaminbake
Feb 19 2018 18:59
ok, Ill shoot him a message on facebook as well. If it comes to getting a new/different pump, which model do you recommend? It seems the 712 is the black sheep.
Tim Street
@tim2000s
Feb 19 2018 19:08
INStalling Dev and getting this issue. Any ideas?
Setting up bluez (5.23-2+deb8u1) ...
Job for bluetooth.service failed. See 'systemctl status bluetooth.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript bluetooth, action "restart" failed.
dpkg: error processing package bluez (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bluezE: Sub-process /usr/bin/dpkg returned an error code (1)
Couldn't install hostapd dnsmasq
Eric
@ecc1
Feb 19 2018 19:10
@benjaminbake 522/722 in good condition, because all versions can loop, or a 523/723 unicorn (firmware <= 2.4)
Scott Leibrand
@scottleibrand
Feb 19 2018 19:11
@benjaminbake the x12 is the hardest to set up. x15 and x22 are essentially identical for looping. x23 requires verifying compatible firmware, but is otherwise identical to x22 for OpenAPS. the MySentry capabilities of x23 are used by Loop if available (to save battery), but not by OpenAPS.
benjaminbake
@benjaminbake
Feb 19 2018 19:12
@Kdisimone too late to put our names in for a x22 on facebook?
Scott Leibrand
@scottleibrand
Feb 19 2018 19:16
she said she'd reuse the same list the next time she gets one, so never too late?
katie disimone
@Kdisimone
Feb 19 2018 19:32
@benjaminbake not too late at all. I’ve only pulled the first name and he’s “confirming” but it’s been 24 hours so I’m about to move onto second person and let them pick if I don’t hear soon. And the pot of names will sit and be reused next time too
Tim Street
@tim2000s
Feb 19 2018 19:34
@scottleibrand Any ideas on that bluez hostapd issue?
Looks like it's trying to install an old version of bluez when 5.48 is already installed.
Dana Lewis
@danamlewis
Feb 19 2018 19:43
Ah thanks @Kdisimone. @benjaminbake I would maybe also try installing dev - I think there may be a few other x12 modifications there if I'm remembering correctly
Scott Leibrand
@scottleibrand
Feb 19 2018 19:44
@tim2000s not offhand
Tim Street
@tim2000s
Feb 19 2018 19:45
Okay - just looking through, this is the full log details:
Checking for BT Mac, BT Peb or Shareble
Checking bluez installation
bluez version 5.48 already installed
Installing prerequisites and configs for local-only hotspot
Reading package lists... Done
Building dependency tree       
Reading state information... Done
dnsmasq is already the newest version.
hostapd is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up bluez (5.23-2+deb8u1) ...
Job for bluetooth.service failed. See 'systemctl status bluetooth.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript bluetooth, action "restart" failed.
dpkg: error processing package bluez (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bluez
E: Sub-process /usr/bin/dpkg returned an error code (1)
Couldn't install hostapd dnsmasq
It seems to be related to the local hotspot set up. Odd that it's trying to install and earlier version of bluez.
Jon Cluck
@cluckj
Feb 19 2018 21:03
argh, forgot to put my name in :-o
tazitoo
@tazitoo
Feb 19 2018 22:27
@mariano42 - have you tried running 'fsck -y' to automatically fix (or at least attempt to) error it finds? It might avoid having to reflash...
garykidd
@garykidd
Feb 19 2018 23:45
@benjaminbake @scottleibrand Yup....I did have that issue when mmtune only worked when pressing the buttons on my 712 pump....@scottleibrand was further correct in that it wasn't that the button needed to be pressed to work as much as it was that fingers needed to be placed on the pump button. I spent a lot of time trying to modify different parameters in mmtune...unfortunately couldn't get anything to work without at least touching the button...I ultimately just secured another insulin pump.... a 723. I wonder if you could experiment with some type of antenna around pump. sorry not more helpful.