Shairport Sync not working on Raspberry Pi 3

Guggele · 12 October 2016 06:28

Hello from Swiss

i bought a Raspberry Pi 3 and installed Shairport from the dietpi-software.

After reboot i don`t see the Shairport on my Airplay on iPhone iPad and my Mac.

What did i wrong.

Regard Guggele

Fourdee · 12 October 2016 13:40

Hi,

Thanks for reporting this, I’ll take a look and run some tests, you can track the issue and its progress here: https://github.com/Fourdee/DietPi/issues/552

Guggele · 12 October 2016 14:48

Thanks a lot for the quick information.

Regard Joerg

Guggele · 12 October 2016 14:56

I am again. If i reboot i get the follow info…
root@DietPi:~# reboot

Broadcast message from systemd-journald@DietPi (Wed 2016-10-12 14:55:17 UTC):

shairport-sync[1037]: avahi client failure

Connection to 192.168.178.2 closed by remote host.
Connection to 192.168.178.2 closed.

Don`t know if it will help you

Fourdee · 12 October 2016 15:17

shairport-sync[1037]: avahi client failure

Hi Joerg,

Ah, yes this will help.

I’d like to get some information on your system and logs, can you do the following please:

Reboot your RPi 3.
Attempt to use AirPlay on any of your Apple products. This is so we can trigger the issue.
Create and send a bug report, by following the instructions here: https://dietpi.com/forum/t/send-dietpi-a-bug-report/421/1

Guggele · 12 October 2016 18:08

I did it but there is no change to see Shairport on any of my Devices.

The Rev for the Report: 8d48c3f0-ec2a-49dd-a165-0f3d2bbb6aa9-0

Joerg

Fourdee · 13 October 2016 15:57

Hi,

Thanks for sending the report. The shairport process appears to be running correctly.

Lets try enabling dbus option for avahi, as per this solution: http://www.cubieforums.com/index.php/topic,1021.msg6161.html?PHPSESSID=nvel2tsb3t6te5tch6si4vq791#msg6161

sed -i "/enable-dbus=/c\enable-dbus=yes" /etc/avahi/avahi-daemon.conf
systemctl restart avahi-daemon
dietpi-services restart

Failing that, we would need to enable logging and find out if there are any errors in both Shairport-Sync and Avahi-Daemon, please run the following commands:

apt-get install -y rsyslog
echo -e "log_verbosity = 2;" >> /etc/shairport-sync.conf
systemctl restart avahi-daemon
dietpi-services restart

Attempt a AirPlay connection, then please paste results of the following command:

cat /var/log/syslog | grep shairport

And

cat /var/log/syslog | grep avahi-daemon

Guggele · 14 October 2016 09:09

Attempt a AirPlay connection, then please paste results of the following command:

cat /var/log/syslog | grep shairport

root@DietPi:~# cat /var/log/syslog | grep shairport
Oct 14 11:05:31 DietPi shairport-sync[6866]: avahi client failure
Oct 14 11:05:57 DietPi shairport-sync[8542]: startup
root@DietPi:~#

cat /var/log/syslog | grep avahi-daemon

root@DietPi:~# cat /var/log/syslog | grep avahi-daemon
Oct 14 11:05:31 DietPi avahi-daemon[6661]: Got SIGTERM, quitting.
Oct 14 11:05:31 DietPi avahi-daemon[6661]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::ba27:ebff:fe24:1349.
Oct 14 11:05:31 DietPi avahi-daemon[6661]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.2.
Oct 14 11:05:31 DietPi avahi-daemon[6661]: avahi-daemon 0.6.31 exiting.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Found user ‘avahi’ (UID 107) and group ‘avahi’ (GID 112).
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Successfully dropped root privileges.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: avahi-daemon 0.6.31 starting up.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Process 6661 died: No such process; trying to remove PID file. (/var/run/avahi-daemon//pid)
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Successfully called chroot().
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Successfully dropped remaining capabilities.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: No service file found in /etc/avahi/services.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ba27:ebff:fe24:1349.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: New relevant interface eth0.IPv6 for mDNS.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.2.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: New relevant interface eth0.IPv4 for mDNS.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Network interface enumeration completed.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Registering new address record for fe80::ba27:ebff:fe24:1349 on eth0.*.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Registering new address record for 192.168.178.2 on eth0.IPv4.
Oct 14 11:05:31 DietPi avahi-daemon[8336]: Registering HINFO record with values ‘ARMV7L’/‘LINUX’.
Oct 14 11:05:32 DietPi avahi-daemon[8336]: Server startup complete. Host name is DietPi.local. Local service cookie is 1290922409.
root@DietPi:~#

Fourdee · 14 October 2016 16:12

Hi thanks for the results.

Oct 14 11:05:31 DietPi shairport-sync[6866]: avahi client failure
Oct 14 11:05:31 DietPi avahi-daemon[6661]: Got SIGTERM, quitting.

Not sure what happened there, either Shairport sync terminated avahi, or avahi terminated itself.

Oct 14 11:05:32 DietPi avahi-daemon[8336]: Server startup complete. Host name is DietPi.local. Local service cookie is 1290922409.

The second startup seems fine under the new process.

Notes:
avahi is getting terminated, automatic restart, terminated by shairport-sync? not sure of source yet.

Scoindy · 30 October 2016 05:44

Hi Guggele,

I’ve been helping Fourdee with this issue and although shairport-sync works perfectly on my system I have been able to replicate what you are experiencing by forcing my pi into a particular state after startup.

We have a couple of ideas about root cause but we need a bit more information from you to get to the bottom of it.

I notice from the previous posts that you installed rsyslog and provided the syslog entries written by the avahi-daemon process but I’d like to have a look at the entire syslog file as well as a couple of other pieces of information.
Could you please reboot your system, check again that shairport still isn’t working, then upload the entire syslog (/var/log/syslog) as an attachment in a response to this post.

Also, could you please provide the output from the following commands:

ifconfig -a
ps -efa f

Finally, we’d just like to rule out any network connectivity issues between your iOS device and your pi. The easiest way to so this is to download a free app from the appstore called called Network Ping Lite.
Start the app once installed and select Ping from the list of tasks on the first screen. On the next screen enter the IP address or your pi (displayed on each login or provided by the ifconfig command above) and hit the start button:

Let us know if the output you see in the grey box is similar to my screenshot or if instead you see Request timeout messages.

Cheers.