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

7th
Apr 2019
Scott Leibrand
@scottleibrand
Apr 07 00:26
Just type wifi to watch that log in real time.
samueldemers2
@samueldemers2
Apr 07 00:42
Ill do that next time I have to leave my home Wi-Fi, ill probably get a clue what is going on. At least, rebooting the rig solve the problem.
samueldemers2
@samueldemers2
Apr 07 02:00
I gave it a try and here what the log returned
Starting oref0-online at Sat 6 Apr 22:00:07 EDT 2019.
Not renewing wlan0 IP due to recent connectivity failure:
-rw-r--r-- 1 root root 6 Apr 6 21:58 /tmp/bad_wifi
At Sat 6 Apr 22:00:10 EDT 2019 my wifi network name is Molly
At Sat 6 Apr 22:00:10 EDT 2019 my local wifi IP is: unassigned
At Sat 6 Apr 22:00:10 EDT 2019 my Bluetooth is connected to Pixel
At Sat 6 Apr 22:00:11 EDT 2019 my local Bluetooth IP is: 192.168.44.249
At Sat 6 Apr 22:00:12 EDT 2019 my public IP is: 104.163.180.18
At Sat 6 Apr 22:00:15 EDT 2019 my local hotspot is not running (and not enabled in preferences.json)
Finished oref0-online at Sat 6 Apr 22:00:18 EDT 2019.
It seem to detect there is a valid Wi-Fi (that is known) but it doesn't manage to connect
It doesnt get an ip adress
Ralsty12
@Ralsty12
Apr 07 02:10
@samueldemers2 Have you tried rebooting your router?
samueldemers2
@samueldemers2
Apr 07 02:24
Yes I did. I didn't went outside. I shut down my modem and my router 😅
The log is after i restarted everything
vsherbeck
@vsherbeck
Apr 07 08:45
I'm still having the "no module named spi-serial" error. @cluckj you said that it may be an incomplete installation ? thing is I've gone through all the steps of the installation like... half a dozen times now with the same result. I mean... should I reflash the card and start all the way over ?
Alfredo kachy
@kachytronico
Apr 07 09:15

Captura de pantalla 2019-04-07 a las 9.54.07.png Sorry, I've checked all times, everything by following the documents.

When I write: sudo remote_syslog
2019-04-07 09:18:27 CRITICAL remote_syslog.go:240 Failed to start server: No destination hostname specified
I'm using Jubilinux 0.3.0 and the dev branch.

Alfredo kachy
@kachytronico
Apr 07 09:21

Captura de pantalla 2019-04-04 a las 16.20.52.png
I also have problems with BT.
gets stuck in this step
sudo /usr/local/bin/bluetoothd --experimental &

I go ahead and everything else works. The problem is that from time to time it does not get connected and I get this error.
I fix it with : bluetoothctl
power off
power on
reboot

Paul Dickens
@thebookins
Apr 07 10:31
@samueldemers2, @acember my colleague's wife has recently started using a pump and CGM; as I understand it she has sudden lows that require a hydrocortisone bolus. Question is whether the CGM interstitial delay makes the data too slow to act on. It may be that some kind of closed loop with automated bolusing makes sense here: the hydrocortisone is needed quickly and doesn't carry the same acute risks of insulin over-delivery.
samueldemers2
@samueldemers2
Apr 07 11:28
@kachytronico I seem to have a problem that is miroir to yours. My bluetooth connect really quicky and doesn't disconect when Wi-Fi is available again...
Jon Cluck
@cluckj
Apr 07 14:21
@vsherbeck yes
I think some of the bluetooth issues on jubilinux stretch are from master installing bluez-5.48, can the folks who are having those problems please do a bluetoothd --version?
Jon Cluck
@cluckj
Apr 07 14:32
@PieterGit the segfault with master installation might be something else, it builds with -DBUILDSWIGNODE=OFF: https://github.com/cluckj/oref0/blob/069201193c76fe78f91e4a7381218688142e1183/bin/oref0-setup.sh#L832
could be a versioning thing :\ MRAA_RELEASE="v1.7.0" that branch doesn't exist anymore
samueldemers2
@samueldemers2
Apr 07 15:27
For the bluetooth I got 5.43
samueldemers2
@samueldemers2
Apr 07 15:35
And it started yesterday after my fresh install (to activate pushover)
samueldemers2
@samueldemers2
Apr 07 15:41
And also im on a pi0 rig
Jon Cluck
@cluckj
Apr 07 15:54
okay, it's probably not the thing I'm thinking of causing it :)
samueldemers2
@samueldemers2
Apr 07 15:55
I might try to start over, wipe the sd card and run everything again
Jon Cluck
@cluckj
Apr 07 15:57
did you use oref0-runagain.sh when you reinstalled?
samueldemers2
@samueldemers2
Apr 07 16:01
No, I used cd && ~/src/oref0/bin/oref0-setup.sh
Jon Cluck
@cluckj
Apr 07 16:05
Not renewing wlan0 IP due to recent connectivity failure: -rw-r--r-- 1 root root 6 Apr 6 21:58 /tmp/bad_wifi
remove /tmp/bad_wifi and see if that helps
samueldemers2
@samueldemers2
Apr 07 16:10
You want me to run this line?
Jon Cluck
@cluckj
Apr 07 16:14
the bad wifi lockout is for an hour, so if you did reset your router it'd take an hour for it to try using wifi again
(on reboot, all the stuff in /tmp is erased; that might be why rebooting let you reconnect?)
Alfredo kachy
@kachytronico
Apr 07 16:23
@cluckj
Jubilinux 0.3.0 wiht dev. BT 5.43.
It connects and it works but sometimes it falls and I do not see why.
Jon Cluck
@cluckj
Apr 07 16:25
hello
samueldemers2
@samueldemers2
Apr 07 16:27
If your guess is good, this line would have to be run every time I connect to my phone by bluetooth
samueldemers2
@samueldemers2
Apr 07 16:34
The command didn't workout, but after about 10 try, the Wi-Fi connected back itself...
I dont see how it did....
Jon Cluck
@cluckj
Apr 07 16:35
might be something to do with your router then?
samueldemers2
@samueldemers2
Apr 07 16:41
I dont know. I havent changed anything but it might be getting old...
I tested again and it worked, again...
Jon Cluck
@cluckj
Apr 07 16:41
@kachytronico can you show more logs about the bluetooth failure (like systemctl status bluetooth)
samueldemers2
@samueldemers2
Apr 07 16:42
Ill keep your line close by, it might come handy sometimes
Jon Cluck
@cluckj
Apr 07 16:44
the router could have just needed a reboot to wipe ip leases etc.
Alfredo kachy
@kachytronico
Apr 07 16:57
systemctl status bluetooth

bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled Active: active (running) since Sun 2019-04-07 14:01:49 CEST; 4 Docs: man:bluetoothd(8)
Main PID: 1520 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─1520 /usr/lib/bluetooth/bluetoothd

Apr 07 18:50:52 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:50:52 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:50:53 edison bluetoothd[1520]: bnep0 connected
Apr 07 18:51:00 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:51:01 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:52:52 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:52:52 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:52:53 edison bluetoothd[1520]: bnep0 connected
Apr 07 18:53:01 edison bluetoothd[1520]: a2dp-source profile connApr 07 18:53:02 edison bluetoothd[1520]: a2dp-source profile conn

Jon Cluck
@cluckj
Apr 07 16:59
oh, I mean when it crashes :)
Alfredo kachy
@kachytronico
Apr 07 17:06

bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-04-07 19:02:08 CEST; 3min 38s ago
Docs: man:bluetoothd(8)
Process: 942 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
Main PID: 942 (code=exited, status=1/FAILURE)
Status: "Starting up"

Apr 07 19:02:08 edison systemd[1]: Starting Bluetooth service...
Apr 07 19:02:08 edison bluetoothd[942]: Bluetooth daemon 5.43
Apr 07 19:02:08 edison bluetoothd[942]: D-Bus setup failed: Name already in use
Apr 07 19:02:08 edison bluetoothd[942]: Unable to get on D-Bus
Apr 07 19:02:08 edison systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Apr 07 19:02:08 edison systemd[1]: Failed to start Bluetooth service.
lines 1-14/16 83%

Alfredo kachy
@kachytronico
Apr 07 17:31
root@edison:~# sudo killall bluetoothd
bluetoothd: no process found
root@edison:~# sudo /usr/local/bin/bluetoothd --experimental &
[1] 9430
root@edison:~# sudo: /usr/local/bin/bluetoothd: command not found
With the master branch, this didn’t happen before. With dev the process doesn’t finish. I follow the following steps
And it’s works for a time.
Alfredo kachy
@kachytronico
Apr 07 17:36
What can I do?
Jon Cluck
@cluckj
Apr 07 17:37
can you skip the killall bluetoothd and the bluetoothd --experimental & steps?
those instructions are for if you have manually compiled bluetoothd (which dev on jubilinux 0.3.0 does not do)
reboot your rig and start with the bluetoothctl command
Alfredo kachy
@kachytronico
Apr 07 17:42
I did it. I don’t know who I am I need to a star
Last login: Sun Apr 7 19:25:43 2019 from 172.20.10.1
root@edison:~# bluetoothctl
[bluetooth]# power off
No default controller available
[bluetooth]#
Jon Cluck
@cluckj
Apr 07 17:43
systemctl start bluetooth
Alfredo kachy
@kachytronico
Apr 07 17:44
Ok thanks
I am in the street with a mobile. Sorry.
root@edison:~# systemctl start bluetooth
Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
Alfredo kachy
@kachytronico
Apr 07 17:55

root@edison:~# journalctl -xe
Apr 07 19:53:07 edison sudo[838]: pam_unix(sudo:session): sessionApr 07 19:53:07 edison sudo[1926]: pam_unix(sudo:session): sessioApr 07 19:53:07 edison sudo[1929]: root : TTY=unknown ; PWD=/Apr 07 19:53:07 edison sudo[1929]: pam_unix(sudo:session): sessioApr 07 19:53:07 edison bluetoothd[1942]: Bluetooth daemon 5.43
Apr 07 19:53:07 edison sudo[1941]: root : TTY=unknown ; PWD=/Apr 07 19:53:07 edison bluetoothd[1942]: Starting SDP server
Apr 07 19:53:07 edison sudo[1941]: pam_unix(sudo:session): sessioApr 07 19:53:07 edison sudo[1941]: pam_unix(sudo:session): sessioApr 07 19:53:07 edison dbus[208]: [system] Activating via systemdApr 07 19:53:07 edison bluetoothd[1942]: Bluetooth management intApr 07 19:53:07 edison systemd[1]: Couldn't stat device /dev/pts/Apr 07 19:53:07 edison systemd[1]: Starting Hostname Service...
-- Subject: Unit systemd-hostnamed.service has begun start-up
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit systemd-hostnamed.service has begun starting up.
Apr 07 19:53:08 edison dbus[208]: [system] Successfully activatedApr 07 19:53:08 edison systemd[1]: Started Hostname Service.
-- Subject: Unit systemd-hostnamed.service has finished start-up
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit systemd-hostnamed.service has finished starting up.

-- The start-up result is done.
Apr 07 19:53:30 edison sudo[2293]: root : TTY=unknown ; PWD=/Apr 07 19:53:30 edison sudo[2293]: pam_unix(sudo:session): sessio

Jon Cluck
@cluckj
Apr 07 18:03
the status bluetooth command will tell you more specific stuff about bluetooth failing (but I bet it's the same D-bus error as before)
Alfredo kachy
@kachytronico
Apr 07 18:26
And you know how to solve it?
I reinstall from the beginning?
Or from where?
Jon Cluck
@cluckj
Apr 07 18:33
it means there's something else starting bluetooth
ps ax | grep blue can show you
Alfredo kachy
@kachytronico
Apr 07 18:43
root@edison:~# ps ax | grep blue 7625 ? S 0:00 sudo /usr/sbin/bluetoothd 7626 ? S 0:00 tee -a /var/log/openaps/bluetoothd.log 7638 ? S 0:00 /usr/sbin/bluetoothd 7872 pts/0 S+ 0:00 grep blue
Jon Cluck
@cluckj
Apr 07 18:46
looks like it's running already? see if bluetoothctl is working now
Alfredo kachy
@kachytronico
Apr 07 18:50
Captura de pantalla 2019-04-07 a las 20.49.20.png
It does not work
Jon Cluck
@cluckj
Apr 07 18:51
is there anything interesting in /var/log/openaps/bluetoothd.log?
that failure is from bluetoothd already being started by openaps
Alfredo kachy
@kachytronico
Apr 07 18:55
D-Bus setup failed: Name already in use
D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Jon Cluck
@cluckj
Apr 07 18:56
oy
try systemctl disable bluetooth
then rebooting, and then bluetoothctl
looks like there's a weird conflict between systemd starting bluetooth and openaps starting bluetooth :\
Alfredo kachy
@kachytronico
Apr 07 19:04
Now it works.
Do I have to configure the BT tethering?
Jon Cluck
@cluckj
Apr 07 19:04
yep
Alfredo kachy
@kachytronico
Apr 07 19:06
But I missed the part where before it got stuck, right?
killall bluetoothd and the bluetoothd --experimental & steps?
says it's already paired with the device.
Then what do I do?
I forget it from the mobile and I'll pair it again?
Jon Cluck
@cluckj
Apr 07 19:09
hmm, revise it to: killall bluetoothd bluetoothd &
oh, that's good :)
see if the bt-pan step works
Alfredo kachy
@kachytronico
Apr 07 19:16
bt-pan step it does not work
sorry, Yes
Let's cross our fingers so that it does not fail again
Alfredo kachy
@kachytronico
Apr 07 19:22
In short, the only thing we have done is: systemctl disable bluetooth
killall bluetoothd
bluetoothd &
then reconfigure Bluetooth tethering
@cluckj
Thanks a thousand
Jon Cluck
@cluckj
Apr 07 19:24
yep, I'm keeping notes too :)
no problem! glad it's working!!
Alfredo kachy
@kachytronico
Apr 07 19:25
I do not want to abuse .... I still have the error of papertrail.
root@edison:~# cd remote_syslog root@edison:~/remote_syslog# root@edison:~/remote_syslog# sudo cp ./remote_syslog /usr/local/bin root@edison:~/remote_syslog# vi /etc/log_files.yml root@edison:~/remote_syslog# sudo remote_syslog 2019-04-04 19:29:05 CRITICAL remote_syslog.go:244 Failed to start server: No destination hostname specified
Jon Cluck
@cluckj
Apr 07 19:26
don't worry about that, I'd just be afk if I didn't have time to help
Alfredo kachy
@kachytronico
Apr 07 19:29
I am worried. You do an incredible job.
I try to solve it by reading but this time I have not succeeded. My knowledge is very limited in linux.
Jon Cluck
@cluckj
Apr 07 19:33
I'm not a papertrail user so we might have to muddle through some stuff :)
that error looks like a configuration issue
Alan
@Alzibiff
Apr 07 19:37
47585133.png
Jon Cluck
@cluckj
Apr 07 19:50
@kachytronico double check your /etc/log_files.yml
Alfredo kachy
@kachytronico
Apr 07 20:52
Sorry, can it have something to do with it now that does not let me connect to the device by shh with the name hostname?
ssh root@edison.local it does not work
ssh root@192.168.1.49yes
Alfredo kachy
@kachytronico
Apr 07 21:04
Can I change the name again?
myedisonhostname=<thehostname-you-want>
echo $myedisonhostname > /etc/hostname
sed -r -i"" "s/localhost( jubilinux)?$/localhost $myedisonhostname/" /etc/hosts
This will work in this branch too?
Eric
@ecc1
Apr 07 21:12

if the problem is other machines not recognizing your rig's hostname, the issue probably involves the part of your network infrastructure (probably your router) that is responsible for name resolution (DNS). And if you're relying on "foo.local" names, that usually involves mDNS (avahi on Linux, bonjour on MacOS I think)

TLDR: If you change the hostname on your rig, other hosts won't see it until your rig re-acquires an IP address from your router (simplest way is to reboot the rig)

Alfredo kachy
@kachytronico
Apr 07 21:28
@ecc1 I have the rig with ip fixed with the mac address. Previously the rig had another name and with this update I changed it. That may be the problem. Thank you. I'm going to make some change.
Alfredo kachy
@kachytronico
Apr 07 21:52
I downloaded the papertrail configuration several times and now it gives me problems.
root@edison:~# tar xzf ./remote_syslog*.tar.gz
tar: remote_syslog/remote_syslog: Cannot open: File exists
tar: Exiting with failure status due to previous errors
Alfredo kachy
@kachytronico
Apr 07 22:01
I have also tried to download the V.20 from remote_syslog2
still the same
Eric
@ecc1
Apr 07 23:01
you can either remove the previous remote_syslog contents before un-tarring, or call tar with the --overwrite option