My logs are filled with a "Bluetooth ... unknown connection handle..." entry, what might be wrong?

SirSkorpan · 03-31-2020, 02:41 PM

The first sign was a crash of my terminal and this message when ever I try to, for example list the content of a directory:

Code:

bash: cannot create temp file for here-document: No space left on device

and

Code:

df -h

shows that my root file system is 100% full. After some searching I find that these three files:

Code:

 
/var/log/kern.log
/var/log/syslog
/var/log/syslog.1

are 8.1+4.1+4.1=16.3G and have been filled by the following line for the last 2 days:

Code:

Mar 29 21:01:50 ubuntu kernel: [52962.228231] Bluetooth: hci0: SCO packet for unknown connection handle 0
.
.
.
Mar 31 15:59:46 ubuntu kernel: [182643.085514] Bluetooth: hci0: SCO packet for unknown connection handle 0
Mar 31 15:59:46 ubuntu kernel: [182643.085516] Bluetooth: hci0: SCO packet for unknown connection handle 0
Mar 31 15:59:46 ubuntu kernel: [182643.085517] Bluetooth: hci0: SCO packet for unknown connection handle 0
Mar 31 15:59:46 ubuntu kernel: [182643.085519] Bluetooth: hci0: SCO packet for unknown connection handle 1024
Mar 31 15:59:46 ubuntu kernel: [182643.085521] Bluetooth: hci0: SCO packet for unknown connection handle 48
Mar 31 15:59:46 ubuntu kernel: [182643.085523] Bluetooth: hci0: SCO packet for unknown connection handle 0
Mar 31 15:59:46 ubuntu kernel: [182643.085524] Bluetooth: hci0: SCO packet for unknown connection handle 0
Mar 31 15:59:46 ubuntu kernel: [182643.085526] Bluetooth: hci0: SCO packet for unknown connection handle 0

(over 99.99% of the lines in all files consists of this line)

I realize that it has something to do with the Bluetooth, but I'm at a loss as to what specific about the bluetooth is failing. I have my bluetooth head set connected almost all day but it seems to be working fine. Both input and output.

I use bluetoothctl to connect to my headset and pavucontrol to switch between headset mode (HSP/HFP) and hifi mode (A2DP sink). Other than that I don't interact or manage bluetooth. Don't have any other devices connected either.

My system is a fairly standard Ubuntu 18.04 installation, as far as I know I haven't installed or changed any advanced settings for bluetooth.

I guess these are the questions:

how do I find out what the log entry means?
how do I solve it so it doesn't appear?
Is there a way to limit the logs to a maximum size?

ondoho · 03-31-2020, 03:28 PM

Delete the logs.
Reboot.
Then (assuming they are filling up again) take another look at the error messages and start fixing it.
Here's a search for the error to get you started.

bazio101 · 03-31-2020, 03:44 PM

Make sure to configure logrotate to, first: rotate kern.log, as it seems that there is no config file for it in /etc/logrotate.d directory or any entry inside logrotate.conf file and second: change the way syslog is being rotated (4,1 Gb is too much).