[PROBLEM] Spotify connect keeps dropping

[ksone]

@ksone

I haven't experienced this random drop out (yet, he says with his fingers crossed!).

*If* the symptom is that the librespot process disappears and if this is a randomly occurring event which isn't due to something like an out-of-memory problem, then it would seem a watchdog could be created to implement something like "if airplay renderer is enabled in moOde and if librespot process is missing, then restart librespot [not raspotify]". The restart must include all the parameters which Tim outlined in his port.

This is a horrible way to deal with the underlying problem. With the Spotify app on my iPad, I'd still have to reconnect to moOde once librespot restarted, but desperate times and all that. I for one am not going to try to debug a problem the librespot developers apparently haven't solved in 11 months. That's way beyond my pay grade.

Regards,
Kent

After a few days Librespot decided yet again on one of my pi's to stop working.
It was expected.. librespot just vanish.

I promised to give an update with what I could find.

"pgrep -l librespot" shows nothing and "systemctl status rc-local" shows that librespot disappears:

Code:

pi@radio:~ $ sudo systemctl status rc-local
● rc-local.service - /etc/rc.local Compatibility
   Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor preset: enabled)
  Drop-In: /lib/systemd/system/rc-local.service.d
           └─debian.conf
        /etc/systemd/system/rc-local.service.d
           └─ttyoutput.conf
   Active: active (running) since Fri 2018-11-30 16:13:08 CET; 5 days ago
   CGroup: /system.slice/rc-local.service
           ├─  463 /usr/bin/udisks-glue
           ├─  505 /usr/bin/php /var/www/command/worker.php
           ├─  819 sudo /usr/local/bin/shairport-sync -a Radio (Airplay) -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh -- -d hw:0
           ├─  828 /usr/local/bin/shairport-sync -a Radio (Airplay) -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh -- -d hw:0
           ├─ 1029 /bin/bash /var/www/command/watchdog.sh
           └─17488 sleep 6

Dec 05 22:15:11 radio sudo[17433]: pam_unix(sudo:session): session closed for user root
Dec 05 22:15:14 radio sudo[17442]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pgrep -l bluealsa-aplay
Dec 05 22:15:14 radio sudo[17442]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 05 22:15:14 radio sudo[17442]: pam_unix(sudo:session): session closed for user root
Dec 05 22:15:17 radio sudo[17462]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pgrep -l bluealsa-aplay
Dec 05 22:15:17 radio sudo[17462]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 05 22:15:17 radio sudo[17462]: pam_unix(sudo:session): session closed for user root
Dec 05 22:15:20 radio sudo[17478]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pgrep -l bluealsa-aplay
Dec 05 22:15:20 radio sudo[17478]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 05 22:15:20 radio sudo[17478]: pam_unix(sudo:session): session closed for user root

plenty of mem and root left
ROOT avail = 3.9G
MEM free = 206 MB

"h t t p://xx.xx.xx.xx/snd-config.php#spotify-restart" instantly fixes it.


Strange thing is that other Pi is still running without issues...(on another network) - its so bloody strange

Regards