Max2Play Home › Forums › Max2Play Add-ons › Bluetooh-Speaker not starting – bluealsa-service failed code=exited, status=127
- This topic has 8 replies, 3 voices, and was last updated 4 years, 10 months ago by fsarrias premium.
-
Posted in: Max2Play Add-ons
-
1. Dezember 2019 at 1:03 #47649
Hello
I want to stream music from my Android phone to a Raspi4+HifiBerry DAC+ connected to my music equipment through Bluetooth with max2play 2.51 installed.
I succesfully installed the bluetooth add-on in max2play.
I succesfully paired my phone with max2play through bluetooth.
But when I try to start Bluetooth-Speaker it gives me an error and the streaming does not work, the debugging info is:#### Bluetooth Installation ####
#### Bluetooth Dongle ####
hci0: Type: Primary Bus: UART
BD Address: DC:A6:32:0E:42:8A ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:48913 acl:25 sco:0 events:2966 errors:0
TX bytes:126221 acl:24 sco:0 commands:2920 errors:0#### BLUEALSA ERROR ####
● bluealsa.service – Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio)
Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2019-11-30 23:56:18 CET; 2s ago
Process: 8684 ExecStartPre=/bin/rm -Rf /var/run/bluealsa (code=exited, status=0/SUCCESS)
Process: 8685 ExecStartPre=/usr/bin/killall bluetoothd (code=exited, status=0/SUCCESS)
Process: 8686 ExecStartPre=/bin/systemctl start sys-subsystem-bluetooth-devices-hci0.device (code=exited, status=0/SUCCESS)
Process: 8687 ExecStartPre=/bin/hciconfig hci0 down (code=exited, status=0/SUCCESS)
Process: 8688 ExecStartPre=/bin/systemctl start bluetooth (code=exited, status=0/SUCCESS)
Process: 8690 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS)
Process: 8691 ExecStart=/usr/bin/bluealsa -p a2dp-sink -p a2dp-source (code=exited, status=127)
Main PID: 8691 (code=exited, status=127)Nov 30 23:56:18 max2play systemd[1]: bluealsa.service: Failed with result ‚exit-code‘.
#### BLUEALSA RUNNING ####
0It seems I have the same problem as another german user here: https://www.max2play.com/en/forums/topic/bluetooth-mit-raspberry-pi-4/
I get also the same library not found error in the SYSLOG:Dec 1 00:38:33 max2play bluealsa[5586]: /usr/bin/bluealsa: error while loading shared libraries: libsbc.so.1: cannot open shared object file: No such file or directory
Please any help will be very valuable
Best regards- This topic was modified 4 years, 11 months ago by fsarrias.
6. Dezember 2019 at 12:05 #47690Hi fsarrias,
We are looking into this issue. Which version is your Pi4 and what other features of Max2Play do you use?
6. Dezember 2019 at 19:11 #47707Hi Heiner
It is a 1x HiFiBerry DAC+ bundle Pi 4 bought on 4th november 2019 so I assume is the latest one, shall I run any command to give you more detailed info?
I only have the Spotify Connect module installed.
Best
7. Dezember 2019 at 13:48 #47713Seems to be the same issue I encountered. apt-get update needs to be run and the new stable distribution has to be accepted. This is not the case in your images.
7. Dezember 2019 at 23:54 #47714I already run version 2.51 which is the latest stable release
11. Dezember 2019 at 13:17 #47745Hi fsarrias,
Alex means the apt-get update in the Raspberry Settings. There’s a button for it at the end of the page.
11. Dezember 2019 at 22:57 #47755Hello
I have reinstalled max2play from scratch, update it, intalled only the bluetooth module, done apt-get update + apt-get upgrade and the bluealsa module does not work:#### Bluetooth Installation ####
#### Bluetooth Dongle ####
hci0: Type: Primary Bus: UART
BD Address: DC:A6:32:0E:42:8A ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:7822 acl:0 sco:0 events:486 errors:0
TX bytes:20354 acl:0 sco:0 commands:486 errors:0#### BLUEALSA ERROR ####
● bluealsa.service – Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio)
Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2019-12-11 21:52:16 CET; 2s ago
Process: 2011 ExecStartPre=/bin/rm -Rf /var/run/bluealsa (code=exited, status=0/SUCCESS)
Process: 2012 ExecStartPre=/usr/bin/killall bluetoothd (code=exited, status=0/SUCCESS)
Process: 2013 ExecStartPre=/bin/systemctl start sys-subsystem-bluetooth-devices-hci0.device (code=exited, status=0/SUCCESS)
Process: 2014 ExecStartPre=/bin/hciconfig hci0 down (code=exited, status=0/SUCCESS)
Process: 2015 ExecStartPre=/bin/systemctl start bluetooth (code=exited, status=0/SUCCESS)
Process: 2017 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS)
Process: 2018 ExecStart=/usr/bin/bluealsa -p a2dp-sink -p a2dp-source (code=exited, status=127)
Main PID: 2018 (code=exited, status=127)#### BLUEALSA RUNNING ####
0/var/log/syslog
Dec 11 21:56:22 max2play systemd[1]: Started Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio).
Dec 11 21:56:22 max2play bluealsa[2952]: /usr/bin/bluealsa: error while loading shared libraries: libsbc.so.1: cannot open shared object file: No such file or directory
Dec 11 21:56:22 max2play systemd[1]: Started „Bluetooth speaker for Bluealsa“.
Dec 11 21:56:22 max2play systemd[1]: bluealsa.service: Main process exited, code=exited, status=127/n/a
Dec 11 21:56:22 max2play systemd[1]: bluealsa.service: Failed with result ‚exit-code‘.
Dec 11 21:56:22 max2play bluealsa-aplay[2953]: /usr/bin/bluealsa-aplay: ../../utils/../src/shared/ctl-client.c:105: Connecting to socket: /var/run/bluealsa/hci0
Dec 11 21:56:22 max2play bluealsa-aplay[2953]: /usr/bin/bluealsa-aplay: BlueALSA connection failed: No such file or directory
Dec 11 21:56:22 max2play systemd[1]: bluealsa_aplay.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 21:56:22 max2play systemd[1]: bluealsa_aplay.service: Failed with result ‚exit-code‘.
Dec 11 21:56:23 max2play systemd[1]: bluealsa_aplay.service: Service RestartSec=100ms expired, scheduling restart.
Dec 11 21:56:23 max2play systemd[1]: bluealsa_aplay.service: Scheduled restart job, restart counter is at 25.
Dec 11 21:56:23 max2play systemd[1]: Stopped „Bluetooth speaker for Bluealsa“. -
You must be logged in to reply to this topic.