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

30th
Nov 2018
MrJarnould
@MrJarnould
Nov 30 2018 00:02
Should I kill everything using '/usr/local/bin/remote_syslog'?
Thanks, viq!
alimhassam
@alimhassam
Nov 30 2018 00:17
@efidoman are you following instructions in this twiki page?
more specifically this sections
https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/update-your-rig.html#step-2-re-run-oref0-setup
says to run setup this way:
cd && ~/src/oref0/bin/oref0-setup.sh
is there issues where the setup script in the path is still on master while the setup script in ~/src/oref0/bin is updated to dev maybe?
fidoman
@efidoman
Nov 30 2018 01:51
@alimhassam - that definitely could have been the problem. I was not using absolute path. Your advice is very timely. I am just now going through the reflash process again and will be doing this process in about 30 minutes or so.
alimhassam
@alimhassam
Nov 30 2018 01:55
@efidoman also note that if you're doing a re-install, the dev branch of openaps.install.sh can now take a branch as an argument, so if you run openaps-install.sh dev it'll directly itnstall the dev branch
something like:
curl https://raw.githubusercontent.com/openaps/oref0/dev/bin/openaps-install.sh > /tmp/openaps-install.sh
bash /tmp/openaps-install.sh dev
fidoman
@efidoman
Nov 30 2018 01:57
even more timely - I was just looking in the docs for this part
fidoman
@efidoman
Nov 30 2018 10:52
@alimhassam - FYI - I used this method, but fortunately I checked before this install script started the interactive setup and found that it still was using master so I killed it and switched to the dev branch.
added 134 packages from 96 contributors in 143.784s
openaps installed
openaps 0.1.5
Cloning into 'oref0'...
remote: Enumerating objects: 18, done.
remote: Counting objects: 100% (18/18), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 16329 (delta 3), reused 3 (delta 2), pack-reused 16311
Receiving objects: 100% (16329/16329), 4.40 MiB | 380.00 KiB/s, done.
Resolving deltas: 100% (11345/11345), done.
Checking connectivity... done.
Press Enter to run oref0-setup with the current release (dev branch) of oref0,
or press ctrl-c to cancel.
Usage: oref0-setup.sh <--dir=directory> <--serial=pump_serial_#> [--tty=/dev/ttySOMETHING] [--max_iob=0] [--ns-host=https://mynightscout.herokuapp.com] [--api-secret=[myplaintextapisecret|token=subjectname-plaintexthashsecret] [--cgm=(G4-upload|G4-local-only|shareble|G5|MDT|xdrip)] [--bleserial=SM123456] [--blemac=FE:DC:BA:98:76:54] [--btmac=AB:CD:EF:01:23:45] [--enable='autotune'] [--radio_locale=(WW|US)] [--ww_ti_usb_reset=(yes|no)]

Start interactive setup? [Y]/n ^C
root@eddie1:~/src/oref0# git pull
Already up-to-date.
root@eddie1:~/src/oref0# git branch
* master
root@eddie1:~/src/oref0# git checkout dev
Branch dev set up to track remote branch dev from origin.
Switched to a new branch 'dev'
root@eddie1:~/src/oref0# git pull
Already up-to-date.
root@eddie1:~/src/oref0#
Now running interactive setup being very careful to watch everything closely
fidoman
@efidoman
Nov 30 2018 11:01
looks like a problem already
openaps-alias show: error: argument name: invalid choice: '*' (choose from )
/root/src/oref0/ already exists; pulling latest
Already up-to-date.
v8.14.0
Checking oref0 installation
└── oref0@0.6.2
No module named mmeowlink.vendors.mmeowlink
Installing latest mmeowlink
Downloading/unpacking mmeowlink
why is it using 0.6.2?
It asked me about using the go compiled release and I chose that option, but it is installing mmeowlink.
fidoman
@efidoman
Nov 30 2018 11:15
BTW - I have the complete oref0-setup.sh log if that helps. I did call the one in bin directly and it was the latest one because I chose the xdrip-js option and it had the go release compiled download option (which I chose).
root@eddie1:~/src/oref0/bin# ./oref0-setup.sh
Usage: oref0-setup.sh <--dir=directory> <--serial=pump_serial_#> [--tty=/dev/ttySOMETHING] [--max_iob=0] [--ns-host=https://mynightscout.herokuapp.com] [--api-secret=[myplaintextapisecret|token=subjectname-plaintexthashsecret] [--cgm=(G4-upload|G4-local-only|G4-go|G5|MDT|xdrip|xdrip-js)] [--bleserial=SM123456] [--blemac=FE:DC:BA:98:76:54] [--dexcom_tx_sn=12A34B] [--btmac=AB:CD:EF:01:23:45] [--enable='autotune'] [--radio_locale=(WW|US)] [--ww_ti_usb_reset=(yes|no)]
Start interactive setup? [Y]/n y
Would you like to [D]ownload released precompiled Go pump communication library or install an [U]nofficial (possibly untested) version.[D]/U D
Downloading latest precompiled Go pump binaries.
What kind of CGM would you like to configure for offline use? Options are:
G4-Go: will use and upload BGs from a plugged in or BLE-paired G4 receiver to Nightscout
G4-upload: will use and upload BGs from a plugged in G4 receiver to Nightscout
G4-local-only: will use BGs from a plugged in G4, but will *not* upload them
G5: will use BGs from a plugged in G5, but will *not* upload them (the G5 app usually does that)
G5-upload: will use and upload BGs from a plugged in G5 receiver to Nightscout
MDT: will use and upload BGs from an Enlite sensor paired to your pump
xdrip: will work with an xDrip receiver app on your Android phone
xdrip-js: will work directly with a Dexcom G5 transmitter and will upload to Nightscout
Note: no matter which option you choose, CGM data will also be downloaded from NS when available.

What kind of CGM would you like to configure?: xdrip-js
Ok, xdrip-js it is.
fidoman
@efidoman
Nov 30 2018 11:32
Well, it did try to download the go pump libraries and got an error and died.

Clearing retrieved apt packages to free space.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Downloading Go pump binaries from: https://github.com/ecc1/medtronic/releases/download/v2018.09.12/medtronic-386-spi.tar.xz
./
./openaps.jq
./cgmpage
./sniff
./setbasals
./historypage
./cgmupdate
./pumphistory
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Couldn't download and extract Go pump binaries
root@eddie1:~/src/oref0/bin#
It doesn't look like a network caused problem
root@eddie1:~/src/oref0/bin# ping google.com
PING google.com (172.217.4.14) 56(84) bytes of data.
64 bytes from atl14s80-in-f14.1e100.net (172.217.4.14): icmp_seq=1 ttl=54 time=75.1 ms
fidoman
@efidoman
Nov 30 2018 11:43
Starting over again, this time I will choose to build the medtronic go library from source
alimhassam
@alimhassam
Nov 30 2018 12:08
@efidoman did you run mom global-install after switching branch?
I'm sorry my suggestion yesterday. I just noticed the bug with the install script... Passing the dev branch doesn't get propagated to the git clone command.
fidoman
@efidoman
Nov 30 2018 12:13
I didn't run mom global-install. I will cancel the current install and try that now
alimhassam
@alimhassam
Nov 30 2018 12:13

in openaps-install.sh

mkdir -p ~/src; cd ~/src && git clone git://github.com/openaps/oref0.git || (cd oref0 && git checkout $BRANCH && git pull)

the || command here will only be executed if the clone fails

we should change || to a ;
fidoman
@efidoman
Nov 30 2018 12:14
you mean npm global install right
alimhassam
@alimhassam
Nov 30 2018 12:15
yes, would be good to also add a npm global install directly in that script
fidoman
@efidoman
Nov 30 2018 12:15
I thought there was one in there.
alimhassam
@alimhassam
Nov 30 2018 12:20
i usually just follow the instructions on the documentation here: https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/update-your-rig.html#alternative-step-1a-dev-to-get-on-dev-branch-to-test-even-more-recently-added-new-stuff
and it does say to run npm run global-install manually.
fidoman
@efidoman
Nov 30 2018 12:20
:+1:
alimhassam
@alimhassam
Nov 30 2018 12:20
but we might be able to automate this. There seems to be regular issues with switching to dev branch, so i wanted to make this easier.
fidoman
@efidoman
Nov 30 2018 12:22
I did run the global install manually like that the half a dozen other times I've tried this.
alimhassam
@alimhassam
Nov 30 2018 12:23
ok, i'm not 100% sure the issue is fully understood. Or maybe another issue.
hopefully it'll work this time!
fidoman
@efidoman
Nov 30 2018 12:26
Thanks - I'm hopeful this time.
global-install failed
npm ERR! path /home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev' -> '/home/.rootfs/usr/lib/node_modules/.staging/abbrev-fd397e54'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
fidoman
@efidoman
Nov 30 2018 12:31
I'm clearing out node_modules and trying again
npm version is 6.4.1
node version is v8.14.0
I cleared all node-modules globally using this command and it fixed it
npm ls -gp --depth=0 | awk -F/ '/node_modules/ && !/\/npm$/ {print $NF}' | xargs npm -g rm
now back to oref0-setup
fidoman
@efidoman
Nov 30 2018 12:39
BTW - the setup script does the global install as well
Installing latest oref0 from /root/src/oref0/

> oref0@0.7.0-dev global-install /root/src/oref0
> npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
fidoman
@efidoman
Nov 30 2018 12:50
it failed on the go library download source to compile stage. I'm trying again now using the download precompiled option
We really need to get runagain working. It is so much easier than doing interactive each time.
precompiled go binaries worked ... now the moment of truth.
fidoman
@efidoman
Nov 30 2018 13:07
It seems to be working, Logger has to feed it some glucose readings to be sure.
alimhassam
@alimhassam
Nov 30 2018 13:11
i think runagain was fixed in the latest dev
(to be confirmed)
Jon Cluck
@cluckj
Nov 30 2018 13:20
Oh wow that ||:laughing:
Me and @cascer1 were staring at that file for hours the other day and we missed it, great catch :smile:
fidoman
@efidoman
Nov 30 2018 13:27
All working now! whew. Thank you to all pitched in along the way. Now, if it were as easy to clone an edison as it is for RPI.
Jon Cluck
@cluckj
Nov 30 2018 13:36
:clap:
Cas Eliëns
@cascer1
Nov 30 2018 14:01
oof
openaps getting wrecked by a ||
fidoman
@efidoman
Nov 30 2018 14:25
well, only one iteration had that issue for me. The others may have had a user-error component.
Cas Eliëns
@cascer1
Nov 30 2018 14:36
I keep getting an issue where apparently the npm command can't be found. is it even installed on raspbian by default?
fidoman
@efidoman
Nov 30 2018 14:50
I don't think that it is. The dependencies are installed by the install script these days. You can do it manually as follows:
sudo apt-get install  npm
Now that everything's working again, I realize just exactly how much I missed fakemeter. All this work to finally get an upgrade to work was worth it for that feature alone. ;->
Cas Eliëns
@cascer1
Nov 30 2018 14:56
well obviously npm isn't getting installed by the install script because I keep not having it
I added apt-get instally -y npm to my own repository to see if that helps
Cas Eliëns
@cascer1
Nov 30 2018 15:13
nope
fidoman
@efidoman
Nov 30 2018 16:04
I suggest updating node. Instructions here on how to do that

For the edison/explorer board (jubilinux), the version of Node that ships with jubilinux is old (v0.10.something). Here are the instructions for updating the edison/explorer rig's Node:

sudo apt-get remove nodered -y
sudo apt-get remove nodejs nodejs-legacy -y
sudo apt-get remove npm -y # if you installed npm
sudo curl -sL https://deb.nodesource.com/setup_8.x | sudo bash -
sudo apt-get install nodejs -y

cd ~/src/Logger && npm rebuild # if Logger exists already and you are upgrading node from 6.x to 8.x
If you are using the RPI zero hat, the version of Node that ships with jubilinux also needs updating. Here are the instructions for updating the rpi zero hat's Node:

mkdir node && cd node
wget https://nodejs.org/dist/v8.10.0/node-v8.10.0-linux-armv6l.tar.xz
tar -xf node-v8.10.0-linux-armv6l.tar.xz
cd 6l
sudo cp -R
/usr/local/

add /usr/local/bin to PATH env variable in .bash_profile

node -v

should show 8.10.0 at this point

Cas Eliëns
@cascer1
Nov 30 2018 16:07
I'm already on node 8.11.1 though
also that setup doesn't work on arm architecture
according to some error I just got
fidoman
@efidoman
Nov 30 2018 16:11
Apologies ... you our beyond my ability to assist now.
Cas Eliëns
@cascer1
Nov 30 2018 16:13
sorry I'm a little cranky
Raymond Richmond
@PedanticAvenger
Nov 30 2018 16:33
Is there a features/operational differences chart anywhere for 0.6 branch vs 0.7 branch other than going through commit logs?
fidoman
@efidoman
Nov 30 2018 16:51
I'm not sure if there is a summary. The biggest change is obviously the completely rewritten pump comms.
Dana Lewis
@danamlewis
Nov 30 2018 17:25
@PedanticAvenger no, other than any notes that are currently in the dev to master pr (it's out of date, but there may be a few there )
Plus what @efidoman said
Raymond Richmond
@PedanticAvenger
Nov 30 2018 17:26
That was my suspicion as to the main diffs but wanted to know if anything else of note was wedged in as well.
Dana Lewis
@danamlewis
Nov 30 2018 17:32
I find it easiest to skim the commit list in the PR to see if anything else is in there. (That's what I'll do when we get around to updating the notes)
Dana Lewis
@danamlewis
Nov 30 2018 18:15
(and actually, if anyone wants to do a summary of the core changes, I'd be happy to add to the list at the top :D - here's an example of the high level stuff we include, you can see the previous release PRs such as openaps/oref0#816 as examples)
Raymond Richmond
@PedanticAvenger
Nov 30 2018 18:38
3500 commits. Even with scanning that will be "fun" :)
Dana Lewis
@danamlewis
Nov 30 2018 18:38
yep ;)
Raymond Richmond
@PedanticAvenger
Nov 30 2018 18:38
Might I propose a workflow change for the future? :P
Dana Lewis
@danamlewis
Nov 30 2018 18:39
if you have a suggestion for improving that, would love to hear.
Raymond Richmond
@PedanticAvenger
Nov 30 2018 18:39
Thinking about some form of tags we could scrape programatically to build a "whats new" and "whats changed" list.
Dana Lewis
@danamlewis
Nov 30 2018 18:39
usually, we add key things as we go along-ish, or get to a point like now where we sit down and comb through, usually when we get closer to testing for release. this ones a bit different as it's primarily radio re-write and bug fixes palooza
yea, that's hard though because the commits don't really indicate if it's a big change or a bug fix - and if a fix, a fix for something old or something fix related to the changes for the PR
Raymond Richmond
@PedanticAvenger
Nov 30 2018 18:41
Yeah, that would be the workflow change, when you PR, tag it with the issue number if it's a logged but, or generic "bugfix", or "new feature" etc.
logged bug rather
Could link each entry back to the PR for people to dive into details. I don't think anything that massively increases work for anyone actually contributing code would be truly valuable.
MrJarnould
@MrJarnould
Nov 30 2018 21:01

Install it then ;)

Hi @viq, thanks for your help yesterday. I successfully installed lsof. I ended up using cp -f for

root@edisonhost:~/remote_syslog# sudo cp ./remote_syslog /usr/local/bin
cp: cannot create regular file '/usr/local/bin/remote_syslog': Text file busy

Unfortunately I still don't see the pump-loop log. In fact, I now see double entries in Papertrail!
I've been trouble shooting online but can't figure it out.

Does this help? Should there be so many remote_syslog_linux_i386.tar.gzs?
root@edisonhost:~# ls
crontab.old.txt  myopenaps              remote_syslog_linux_i386.tar.gz.1  src
crontab.txt     remote_syslog              remote_syslog_linux_i386.tar.gz.2
kernel.config     remote_syslog_linux_i386.tar.gz  remote_syslog_linux_i386.tar.gz.3
I don't think cp -f fixed the underlying issue, or really replaced the file
And you get multiple files because it was downloaded multiple times
MrJarnould
@MrJarnould
Nov 30 2018 22:00
@viq Right. Should I kill all of these? I want to make sure I don't kill the wrong files.
root@edisonhost:~# lsof | grep remote_syslog
remote_sy   481             root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   483       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   484       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   485       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   501       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   502       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   513       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   514       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   517       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   518       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   519       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   520       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   521       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   530       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy   481   642       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953             root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27954       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27955       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27956       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27957       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27958       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27959       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27960       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27961       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27962       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27963       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27964       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27965       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27966       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27967       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 27978       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
remote_sy 27953 29347       root  txt       REG     179,10  9058451      31893 /home/.rootfs/usr/local/bin/remote_syslog
I guess at that point just pkill remote_syslog
jgslade
@jgslade
Nov 30 2018 22:42

Since my rig stopped connecting via bluetooth I got a usb bluetooth dongle, I am unable to do anything with it. All of the bluetoothctl commands are only sent to the built in device. The new devices is listed:

[NEW] Controller B8:27:EB:0F:1D:67 rigticus #1 [default]
[NEW] Controller 5C:F3:70:8C:4D:BA rigticus

But the built in controller is default and all commands will only control it. I have been searching for a fix for this, but all my results turn up connecting a game controller to a rpi, or a no default device error, and nothing in any of the links I have read is close to what I am experiencing.
How can I disable the built in bt controller, or change the default?
Thank you

dmdfreak
@dmdfreak
Nov 30 2018 22:59
Just a curious question. How come someone hasn't made the app version of nightscout so the website wouldn't be required and we would have all the great information that nightscout gives us locally?
Not that I'm a programmer and could make it happen lol I wish I had that ability
Eric
@ecc1
Nov 30 2018 23:07
@jgslade Are you sure your rig's bluetooth is broken? It's much more likely a configuration issue, and that's unlikely to be solved by switching hardware. But, you can specify hciN to the hciconfig command, and you can use the "list" and "select" commands in bluetoothctl to select a specific controller.
jgslade
@jgslade
Nov 30 2018 23:08
It worked for a day, then stopped. No software changes took place during that time, it will connect the immediately disconnect
PCTamer
@PCTamer
Nov 30 2018 23:16
i am glad that it works off web site. more control and privacy for me.
Eric
@ecc1
Nov 30 2018 23:21
@jgslade if you use bluetoothctl, can you discover other devices like your phone, etc?
jgslade
@jgslade
Nov 30 2018 23:21
Yeah
I can connect to my phone with the built in BT controller, but it will immediately lose connection. I can connect to my phone with my laptop, and it will stay connected. I can't use bluetoothctl with the new adapter though, since the built in is the default, and I haven't been able to figure out how to change it.
Eric
@ecc1
Nov 30 2018 23:25
See above for how to change it. When you say connect to your phone, you mean as a BT hotspot? Or just in bluetoothctl?
Is this a Pi or Edison rig?
jgslade
@jgslade
Nov 30 2018 23:27
as a BT hotspot. It's a pi
Thank you
Eric
@ecc1
Nov 30 2018 23:30
I think the whole bt-pan script approach is pretty fragile, but there might be some info in your logs about what happens when it's losing the connection. I highly recommend using network-manager instead, which handles BT networking automatically, but it has a bit of a learning curve
jgslade
@jgslade
Nov 30 2018 23:32
I tried a few days ago, and I started getting kernel panics. Is there a way to install it so it doesn't auto start so I can configure the network before activating the service?
I think the kernel panics were because network manager started and killed my network connection so I lost my ssh shell
This is what happened with the usb dongle:
random: 7 urandom warning(s) missed due to ratelimiting[CHG] Device 20:39:56:DD:B7:97 Modalias: bluetooth:v000Fp1200d1436
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001103-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000112d-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: fafbdd20-83f0-4389-addf-917ac9dae5b2
[CHG] Device 20:39:56:DD:B7:97 ServicesResolved: yes
[CHG] Device 20:39:56:DD:B7:97 Paired: yes
[CHG] Device 20:39:56:DD:B7:97 ServicesResolved: no
[CHG] Device 20:39:56:DD:B7:97 Connected: no
jgslade
@jgslade
Nov 30 2018 23:41
journalctl shows this:
Nov 30 16:29:33 rigticus bluetoothd[18570]: a2dp-source profile connect failed for 20:39:56:DD:B7:97: Protocol not available
Nov 30 16:13:13 rigticus bluetoothd[18570]: a2dp-source profile connect failed for 20:39:56:DD:B7:97: Protocol not available
Nov 30 16:11:29 rigticus bluetoothd[18570]: a2dp-source profile connect failed for 20:39:56:DD:B7:97: Protocol not available
Nov 30 16:03:08 rigticus kernel: ---[ end trace ebb551a21a7f594b ]---
Nov 30 16:03:08 rigticus kernel: [<c003f518>] (kthread) from [<c000fe2c>] (ret_from_fork+0x14/0x28)
Nov 30 16:03:08 rigticus kernel: [<c003961c>] (worker_thread) from [<c003f518>] (kthread+0x120/0x15c)
Nov 30 16:03:08 rigticus kernel: [<c0039364>] (process_one_work) from [<c003961c>] (worker_thread+0x3c/0x544)
Nov 30 16:03:08 rigticus kernel: [<c03c5fd4>] (release_one_tty) from [<c0039364>] (process_one_work+0x11c/0x398)
Nov 30 16:03:08 rigticus kernel: [<bf073ee0>] (rfcomm_tty_cleanup [rfcomm]) from [<c03c5fd4>] (release_one_tty+0x3c/0x8c)
Nov 30 16:03:08 rigticus kernel: [<c03cdcb0>] (tty_port_put) from [<bf073ee0>] (rfcomm_tty_cleanup+0x78/0x7c [rfcomm])
Nov 30 16:03:08 rigticus kernel: [<c0021fc0>] (warn_slowpath_null) from [<c03cdcb0>] (tty_port_put+0xa4/0xac)
Nov 30 16:03:08 rigticus kernel: [<c0021ecc>] (__warn) from [<c0021fc0>] (warn_slowpath_null+0x30/0x38)
Nov 30 16:03:08 rigticus kernel: [<c0634c44>] (dump_stack) from [<c0021ecc>] (__warn+0xe4/0x10c)
Nov 30 16:03:08 rigticus kernel: [<c0013d40>] (show_stack) from [<c0634c44>] (dump_stack+0x20/0x28)
Nov 30 16:03:08 rigticus kernel: [<c0016420>] (unwind_backtrace) from [<c0013d40>] (show_stack+0x20/0x24)
Nov 30 16:03:08 rigticus kernel: Workqueue: events release_one_tty
Nov 30 16:03:08 rigticus kernel: Hardware name: BCM2835
Nov 30 16:03:08 rigticus kernel: CPU: 0 PID: 18814 Comm: kworker/0:1 Tainted: G         C      4.14.79+ #1159
Nov 30 16:03:08 rigticus kernel: Modules linked in: rfcomm cmac btusb btrtl btintel bnep hci_uart btbcm serdev bluetooth ecdh_generic spidev brcmfm
Nov 30 16:03:08 rigticus kernel: WARNING: CPU: 0 PID: 18814 at drivers/tty/tty_port.c:256 tty_port_put+0xa4/0xac
Nov 30 16:03:08 rigticus kernel: ------------[ cut here ]------------
Eric
@ecc1
Nov 30 2018 23:57
not sure about the kernel backtrace, but yes, switching to network-manager needs to be done with a USB-serial terminal connection to the Pi, since you lose your network connectivity while switching over. There's probably a way not to, but I haven't figured it out.
Do you have the latest raspbian system on your Pi (apt-get update and dist-upgrade ?)