After upgrading to the latest Volumio 2.692 on my Raspberry Pi 4, the AirPlay suddenly stopped working. I logged into the console using the default volumio user account and checked out the status of the shairport-sync program. What I found is the following:
$ systemctl status shairport-sync
● shairport-sync.service - Shairport Sync - AirPlay Audio Receiver
Loaded: loaded (/lib/systemd/system/shairport-sync.service; static)
Active: failed (Result: exit-code) since Wed 2019-12-25 16:48:50 UTC; 6s ago
Process: 21262 ExecStart=/usr/local/bin/shairport-sync --configfile=/tmp/shairport-sync.conf (code=exited, status=216/GROUP)
Main PID: 21262 (code=exited, status=216/GROUP)
Dec 25 16:48:50 musicbox systemd[1]: Starting Shairport Sync - AirPlay Audio Receiver…
Dec 25 16:48:50 musicbox systemd[1]: Started Shairport Sync - AirPlay Audio Receiver.
Dec 25 16:48:50 musicbox systemd[1]: shairport-sync.service: main process exited, code=exited, status=216/GROUP
Dec 25 16:48:50 musicbox systemd[1]: Unit shairport-sync.service entered failed state.
Then I launched the shairport-sync program directly using the command line specified in /lib/systemd/system/shairport-sync.service:
$ /usr/local/bin/shairport-sync --configfile=/tmp/shairport-sync.conf
{“time”:1577293129587,“response”:“airplayActive Success”}{“time”:1577293129596,“response”:“startAirplayPlayback Success”}{“time”:1577293143143,“response”:“stopAirplayPlayback Success”}{“time”:1577293153176,“response”:“airplayInactive Success”}
Now the AirPlay worked again!
Therefore, it’s the problem of systemd that’s responsible for launching shairport-sync. The error message “status=216/GROUP” indicates the problem has something to do with user/group privileges. The systemd script of shairport-sync contains the following configuration:
[Service]
ExecStart=/usr/local/bin/shairport-sync --configfile=/tmp/shairport-sync.conf
User=shairport-sync
Group=shairport-sync
So there must be something wrong messed up in the user/group settings in this latest version.
Please kindly record this bug and have it fixed in next release. Many thanks!