Hello,
I’ve been using Volumio just for a bit and have an interesting setup. I have a rather large room for my home office. On one side of the room is my audio setup with Volumio chained in running on a Pi3. The opposite side of the room has my desk with a work laptop and my personal computer. I can’t run Tuneblade from my work laptop so I remote desktop into my Windows 10 personal desktop and use Tuneblade there to stream Google Music to Volumio.
This whole scenario works fine, for the most part. Every now and again something occurs and Tuneblade cannot connect or find Volumio.
Here’s what I found in the logs:
2019-12-10T14:41:22.728Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.730Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.731Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.732Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.733Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.734Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.735Z - info: Shairport-sync error: Error: Command failed: /usr/bin/sudo /usr/bin/killall shairport-sync
shairport-sync: no process found
2019-12-10T14:41:22.736Z - info: Shairport-Sync Stopped
2019-12-10T14:41:25.677Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:25.762Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:25.846Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:25.926Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:26.009Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:26.092Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:26.177Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:26.260Z - info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
2019-12-10T14:41:26.545Z - info: Shairport-Sync Started
2019-12-10T14:41:26.662Z - info: Shairport-Sync Started
2019-12-10T14:41:26.709Z - info: Shairport-Sync Started
2019-12-10T14:41:26.752Z - info: Shairport-Sync Started
2019-12-10T14:41:26.833Z - info: Shairport-Sync Started
2019-12-10T14:41:26.851Z - info: Shairport-Sync Started
2019-12-10T14:41:26.908Z - info: Shairport-sync error: Error: Command failed: sudo systemctl restart airplay
Job for airplay.service failed. See ‘systemctl status airplay.service’ and ‘journalctl -xn’ for details.
2019-12-10T14:41:26.916Z - info: Shairport-sync error: Error: Command failed: sudo systemctl restart airplay
Job for airplay.service failed. See ‘systemctl status airplay.service’ and ‘journalctl -xn’ for details.
2019-12-10T14:42:08.548Z - error: error
2019-12-10T14:42:58.551Z - error: error
2019-12-10T14:43:48.549Z - error: error
2019-12-10T14:44:38.552Z - error: error
2019-12-10T14:45:28.553Z - error: error
2019-12-10T14:46:18.555Z - error: error
I’ve tried manually restarting it but it doesn’t seem to work.