New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotify stops playing after a few songs #112

Open
BugRogers42 opened this Issue May 17, 2018 · 28 comments

Comments

Projects
None yet
@BugRogers42

BugRogers42 commented May 17, 2018

I'm using the android app to play music via a pi and you raspotify.
The Pi will be displayed as divice in the app and i can start the music. But after a few songs (can be 1, 2 or 10) it stops playing and the list of devices is sometimes empty, sometimes Raspotify is displayed as device but i can't connect. After restarting Raspotify it works again immediatly.
The Pi is cable-connected and I entered username/password in /etc/default/raspotify, but that doesn't work.

I know there are some similar issues but it is a very important one. Are you working on it?

regards

@Pepepito

This comment has been minimized.

Show comment
Hide comment
@Pepepito

Pepepito May 17, 2018

Hi, me too i have the same problem.
I wanted to open a new thread but I will answer here.

I tried to reinstall Raspbian and installing just Raspotify. It's doesn't work anymore.
Can connect (via Spotify Connect) at all and if i can connect, no music is played and i'm immedialty disconnected. Nothing is wrong with logins and service.
Few weeks ago it's work fine but since the last week no.

Pepepito commented May 17, 2018

Hi, me too i have the same problem.
I wanted to open a new thread but I will answer here.

I tried to reinstall Raspbian and installing just Raspotify. It's doesn't work anymore.
Can connect (via Spotify Connect) at all and if i can connect, no music is played and i'm immedialty disconnected. Nothing is wrong with logins and service.
Few weeks ago it's work fine but since the last week no.

@andy646362

This comment has been minimized.

Show comment
Hide comment
@andy646362

andy646362 May 17, 2018

Same problem here. This is my error:

* raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-05-17 19:36:52 CEST; 2s ago Process: 1848 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS) Process: 1845 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS) Main PID: 1852 (librespot) CGroup: /system.slice/raspotify.service-1852 /usr/bin/librespot --name raspotify (osmc) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-

May 17 19:36:52 osmc systemd[1]: Starting Raspotify...
May 17 19:36:52 osmc systemd[1]: Started Raspotify.
May 17 19:36:52 osmc librespot[1852]: INFO:librespot: librespot (raspotify) 59cff3d (2018-04-25). Built on 2018-04-30. Build ID: 7BHFeq2k
May 17 19:36:52 osmc librespot[1852]: WARN:mdns: Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
May 17 19:36:53 osmc librespot[1852]: INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-6k5g.ap.spotify.com:4070"
May 17 19:36:53 osmc librespot[1852]: thread 'main' panicked at 'Authentication failed with reason: BadCredentials', core/src/connection/mod.rs:93:21
May 17 19:36:53 osmc librespot[1852]: stack backtrace:
May 17 19:36:54 osmc librespot[1852]: 0: 0x9ec333 - std::sys::unix::backtrace::tracing:👿:unwind_backtrace::h4ef6490c84cef3d0
`

I'm thinking this is a problem with Spotify itself.

andy646362 commented May 17, 2018

Same problem here. This is my error:

* raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-05-17 19:36:52 CEST; 2s ago Process: 1848 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS) Process: 1845 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS) Main PID: 1852 (librespot) CGroup: /system.slice/raspotify.service-1852 /usr/bin/librespot --name raspotify (osmc) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-

May 17 19:36:52 osmc systemd[1]: Starting Raspotify...
May 17 19:36:52 osmc systemd[1]: Started Raspotify.
May 17 19:36:52 osmc librespot[1852]: INFO:librespot: librespot (raspotify) 59cff3d (2018-04-25). Built on 2018-04-30. Build ID: 7BHFeq2k
May 17 19:36:52 osmc librespot[1852]: WARN:mdns: Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
May 17 19:36:53 osmc librespot[1852]: INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-6k5g.ap.spotify.com:4070"
May 17 19:36:53 osmc librespot[1852]: thread 'main' panicked at 'Authentication failed with reason: BadCredentials', core/src/connection/mod.rs:93:21
May 17 19:36:53 osmc librespot[1852]: stack backtrace:
May 17 19:36:54 osmc librespot[1852]: 0: 0x9ec333 - std::sys::unix::backtrace::tracing:👿:unwind_backtrace::h4ef6490c84cef3d0
`

I'm thinking this is a problem with Spotify itself.

@gfro84

This comment has been minimized.

Show comment
Hide comment
@gfro84

gfro84 May 17, 2018

Update: My specific issue seems to be that of #114 and related to librespot.

I have an issue with similar effect.

`● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-05-17 21:40:03 BST; 2min 44s ago
Process: 574 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 572 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 578 (librespot)
CGroup: /system.slice/raspotify.service
└─578 /usr/bin/librespot --name RaPi_spotify --backend alsa --bitrate 320 --disable-audio-cache --initial-volume 65

May 17 21:40:03 osmc-Waldo librespot[578]: INFO:librespot: librespot (raspotify) 59cff3d (2018-04-25). Built on 2018-04-30. Build ID: 7BHFeq2k
May 17 21:40:03 osmc-Waldo librespot[578]: WARN:mdns: Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
May 17 21:41:55 osmc-Waldo librespot[578]: INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-ng9h.ap.spotify.com:4070"
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_core::session: Authenticated as "my_user_name" !
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_core::session: Country: "GB"
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Loading track "Malibu" with Spotify URI "spotify:track:1UZOjK1BwmwWU14Erba9CZ"
May 17 21:41:57 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Track "Malibu" loaded
May 17 21:42:46 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Loading track "Pick Up" with Spotify URI "spotify:track:3FKMngtZtIZCNKYexhGrVD"
May 17 21:42:47 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Track "Pick Up" loaded
osmc@osmc-Waldo:~$ service raspotify status
● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-05-17 21:43:47 BST; 3s ago
Process: 578 ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CACHE_ARGS $VOLUME_ARGS $OPTIONS (code=exited, status=101)
Process: 574 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 572 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 578 (code=exited, status=101)

May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Main process exited, code=exited, status=101/n/a
May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Unit entered failed state.
May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Failed with result 'exit-code'.
`

gfro84 commented May 17, 2018

Update: My specific issue seems to be that of #114 and related to librespot.

I have an issue with similar effect.

`● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-05-17 21:40:03 BST; 2min 44s ago
Process: 574 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 572 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 578 (librespot)
CGroup: /system.slice/raspotify.service
└─578 /usr/bin/librespot --name RaPi_spotify --backend alsa --bitrate 320 --disable-audio-cache --initial-volume 65

May 17 21:40:03 osmc-Waldo librespot[578]: INFO:librespot: librespot (raspotify) 59cff3d (2018-04-25). Built on 2018-04-30. Build ID: 7BHFeq2k
May 17 21:40:03 osmc-Waldo librespot[578]: WARN:mdns: Failed to register IPv6 receiver: Os { code: 19, kind: Other, message: "No such device" }
May 17 21:41:55 osmc-Waldo librespot[578]: INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-ng9h.ap.spotify.com:4070"
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_core::session: Authenticated as "my_user_name" !
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_core::session: Country: "GB"
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink
May 17 21:41:56 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Loading track "Malibu" with Spotify URI "spotify:track:1UZOjK1BwmwWU14Erba9CZ"
May 17 21:41:57 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Track "Malibu" loaded
May 17 21:42:46 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Loading track "Pick Up" with Spotify URI "spotify:track:3FKMngtZtIZCNKYexhGrVD"
May 17 21:42:47 osmc-Waldo librespot[578]: INFO:librespot_playback::player: Track "Pick Up" loaded
osmc@osmc-Waldo:~$ service raspotify status
● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-05-17 21:43:47 BST; 3s ago
Process: 578 ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CACHE_ARGS $VOLUME_ARGS $OPTIONS (code=exited, status=101)
Process: 574 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 572 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 578 (code=exited, status=101)

May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Main process exited, code=exited, status=101/n/a
May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Unit entered failed state.
May 17 21:43:47 osmc-Waldo systemd[1]: raspotify.service: Failed with result 'exit-code'.
`

@Pepepito

This comment has been minimized.

Show comment
Hide comment
@Pepepito

Pepepito May 18, 2018

I tried to use Raspotify and Spotifyd but nothing work. Both use Librespot so i launched this alone and he give me some errors. (Segmentation Fault)
I wanted to install his fork (https://github.com/librespot-org/librespot) but I do not know how to recover the repository and compile. If anyone knows how to do and test, it will be nice to keep up to date.

Pepepito commented May 18, 2018

I tried to use Raspotify and Spotifyd but nothing work. Both use Librespot so i launched this alone and he give me some errors. (Segmentation Fault)
I wanted to install his fork (https://github.com/librespot-org/librespot) but I do not know how to recover the repository and compile. If anyone knows how to do and test, it will be nice to keep up to date.

@dtcooper

This comment has been minimized.

Show comment
Hide comment
@dtcooper

dtcooper May 18, 2018

Owner

By chance are you attempting to play local files? The is as yet unsupported.

Owner

dtcooper commented May 18, 2018

By chance are you attempting to play local files? The is as yet unsupported.

@dtcooper

This comment has been minimized.

Show comment
Hide comment
@dtcooper

dtcooper May 18, 2018

Owner

@Heil-Pepito: I'm already using the librespot-org fork, but if you'd like to try building against a fork of librespot, try the instructions I laid out here. Thanks.

Owner

dtcooper commented May 18, 2018

@Heil-Pepito: I'm already using the librespot-org fork, but if you'd like to try building against a fork of librespot, try the instructions I laid out here. Thanks.

@Pepepito

This comment has been minimized.

Show comment
Hide comment
@Pepepito

Pepepito May 18, 2018

Thanks dtcooper, i've fixed my Librespot problem but the initial problem stay here.

Pepepito commented May 18, 2018

Thanks dtcooper, i've fixed my Librespot problem but the initial problem stay here.

@BugRogers42

This comment has been minimized.

Show comment
Hide comment
@BugRogers42

BugRogers42 May 19, 2018

2 days ago there was a new update of the andoid app. Now raspotify doesn't work anymore for me. In the app i can see the device for one second then it disappears again. When i restart raspotify it takes some time then the same effect happens again.

BugRogers42 commented May 19, 2018

2 days ago there was a new update of the andoid app. Now raspotify doesn't work anymore for me. In the app i can see the device for one second then it disappears again. When i restart raspotify it takes some time then the same effect happens again.

@JeremieRapin

This comment has been minimized.

Show comment
Hide comment
@JeremieRapin

JeremieRapin May 19, 2018

I have the same behavior and an ugly fix. Add a crontab entry which survey the raspotify's status.

Create a file watchdog.sh in /home/pi.
Then add an entry in /etc/crontab, as described in the script's comment .

Raspotify still crashing, but in the next minute, it is relaunch and music can be play again.

My 2 cents, ....

JeremieRapin commented May 19, 2018

I have the same behavior and an ugly fix. Add a crontab entry which survey the raspotify's status.

Create a file watchdog.sh in /home/pi.
Then add an entry in /etc/crontab, as described in the script's comment .

Raspotify still crashing, but in the next minute, it is relaunch and music can be play again.

My 2 cents, ....

@andy646362

This comment has been minimized.

Show comment
Hide comment
@andy646362

andy646362 May 19, 2018

@dtcooper My issue was resolved by the latest update, thanks!

andy646362 commented May 19, 2018

@dtcooper My issue was resolved by the latest update, thanks!

@ruitome

This comment has been minimized.

Show comment
Hide comment
@ruitome

ruitome May 19, 2018

I'm having the same issue as @BugRogers42. I can select the Pi in the spotify client, and if I want to change the volume level it crashes immediately. If I don't change anything it crashes a few seconds after playing. This is happening since 2 days ago.

ruitome commented May 19, 2018

I'm having the same issue as @BugRogers42. I can select the Pi in the spotify client, and if I want to change the volume level it crashes immediately. If I don't change anything it crashes a few seconds after playing. This is happening since 2 days ago.

@scarapunzi

This comment has been minimized.

Show comment
Hide comment
@scarapunzi

scarapunzi May 20, 2018

Same issue of @BugRogers42 here!

scarapunzi commented May 20, 2018

Same issue of @BugRogers42 here!

@gfro84

This comment has been minimized.

Show comment
Hide comment
@gfro84

gfro84 May 21, 2018

See #114 - update raspotify and you will be fixed

gfro84 commented May 21, 2018

See #114 - update raspotify and you will be fixed

@ruitome

This comment has been minimized.

Show comment
Hide comment
@ruitome

ruitome May 21, 2018

Thanks @gfro84! This worked for me :)

ruitome commented May 21, 2018

Thanks @gfro84! This worked for me :)

@Pepepito

This comment has been minimized.

Show comment
Hide comment
@Pepepito

Pepepito May 21, 2018

@dtcooper It's working now without problems but i can't confirm if it's solved by the update. In all cases, thanks for your help.

Pepepito commented May 21, 2018

@dtcooper It's working now without problems but i can't confirm if it's solved by the update. In all cases, thanks for your help.

@nomoreme

This comment has been minimized.

Show comment
Hide comment
@nomoreme

nomoreme May 28, 2018

Hi, I have the same problem described in the first post by @BugRogers42. I can see the Pi in the device list in app and sometimes I can start the music and after a few songs it stops, sometimes spotify won't connect to the Pi and the list became empty.
After a Pi restart (and some relaunch of the spotify app on my phone), everything works.

Everything is updated with sudo apt-get update && sudo apt-get upgrade.

Here's the log from sudo systemctl status raspotify:

● raspotify.service - Raspotify
   Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-05-27 16:11:16 UTC; 1 day 5h ago
  Process: 481 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
  Process: 470 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
 Main PID: 483 (librespot)
   CGroup: /system.slice/raspotify.service
           └─483 /usr/bin/librespot --name raspotify (raspberrypi) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-volume --initial-volume=

May 27 17:00:52 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Miracle" loaded
May 27 17:04:00 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "Cloud Nine" with Spotify URI "spotify:track:34nw5BCrCKN6nVrL4Zaong"
May 27 17:04:01 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Cloud Nine" loaded
May 27 17:07:53 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "One Kiss (with Dua Lipa)" with Spotify URI "spotify:track:7ef4DlsgrMEH11cDZd32M6"
May 27 17:07:55 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "One Kiss (with Dua Lipa)" loaded
May 27 17:11:29 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "Flames" with Spotify URI "spotify:track:33IOhptvC2Qoy2UhjiHXLV"
May 27 17:11:30 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Flames" loaded
May 27 17:14:45 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "You Owe Me" with Spotify URI "spotify:track:3ZBksMOUTbOTIgIwV0RaLg"
May 27 17:14:46 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "You Owe Me" loaded
May 27 17:17:57 raspberrypi librespot[483]: ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

Let me know if you need more debugging info.
And thanks for your help (and the amazing client... when it works is <3 )

nomoreme commented May 28, 2018

Hi, I have the same problem described in the first post by @BugRogers42. I can see the Pi in the device list in app and sometimes I can start the music and after a few songs it stops, sometimes spotify won't connect to the Pi and the list became empty.
After a Pi restart (and some relaunch of the spotify app on my phone), everything works.

Everything is updated with sudo apt-get update && sudo apt-get upgrade.

Here's the log from sudo systemctl status raspotify:

● raspotify.service - Raspotify
   Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-05-27 16:11:16 UTC; 1 day 5h ago
  Process: 481 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
  Process: 470 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
 Main PID: 483 (librespot)
   CGroup: /system.slice/raspotify.service
           └─483 /usr/bin/librespot --name raspotify (raspberrypi) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-volume --initial-volume=

May 27 17:00:52 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Miracle" loaded
May 27 17:04:00 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "Cloud Nine" with Spotify URI "spotify:track:34nw5BCrCKN6nVrL4Zaong"
May 27 17:04:01 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Cloud Nine" loaded
May 27 17:07:53 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "One Kiss (with Dua Lipa)" with Spotify URI "spotify:track:7ef4DlsgrMEH11cDZd32M6"
May 27 17:07:55 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "One Kiss (with Dua Lipa)" loaded
May 27 17:11:29 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "Flames" with Spotify URI "spotify:track:33IOhptvC2Qoy2UhjiHXLV"
May 27 17:11:30 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "Flames" loaded
May 27 17:14:45 raspberrypi librespot[483]: INFO:librespot_playback::player: Loading track "You Owe Me" with Spotify URI "spotify:track:3ZBksMOUTbOTIgIwV0RaLg"
May 27 17:14:46 raspberrypi librespot[483]: INFO:librespot_playback::player: Track "You Owe Me" loaded
May 27 17:17:57 raspberrypi librespot[483]: ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

Let me know if you need more debugging info.
And thanks for your help (and the amazing client... when it works is <3 )

@rodet

This comment has been minimized.

Show comment
Hide comment
@rodet

rodet May 31, 2018

I had a similar problem for a few weeks and was wondering what was happening. Yesterday my Raspberry went out of disk space. After making space again on the Raspberry (/var/logalone was taking 1.5GB), Raspotify is working now perfectly. I guess Raspotify has some minimum space requirement for caching files on the disk? Anyway, it's quick looking for how much space you still have on your device and trying to clean up a bit.
@dtcooper maybe something to add to the troubleshooting section?

rodet commented May 31, 2018

I had a similar problem for a few weeks and was wondering what was happening. Yesterday my Raspberry went out of disk space. After making space again on the Raspberry (/var/logalone was taking 1.5GB), Raspotify is working now perfectly. I guess Raspotify has some minimum space requirement for caching files on the disk? Anyway, it's quick looking for how much space you still have on your device and trying to clean up a bit.
@dtcooper maybe something to add to the troubleshooting section?

@dtcooper

This comment has been minimized.

Show comment
Hide comment
@dtcooper

dtcooper May 31, 2018

Owner

I'll take a look at what happens in /var/log. Could you folks check to see if your disk/SD card is full?

Owner

dtcooper commented May 31, 2018

I'll take a look at what happens in /var/log. Could you folks check to see if your disk/SD card is full?

@rodet

This comment has been minimized.

Show comment
Hide comment
@rodet

rodet May 31, 2018

Sorry for the misunderstanding... The size of the logs must have been from Raspbian overall, not from Raspotify (I assume)

rodet commented May 31, 2018

Sorry for the misunderstanding... The size of the logs must have been from Raspbian overall, not from Raspotify (I assume)

@nomoreme

This comment has been minimized.

Show comment
Hide comment
@nomoreme

nomoreme Jun 2, 2018

I don't think I have any space isuue:

Filesystem Size Used Avail Use% Mounted on
/dev/root 30G 3.0G 26G 11% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 8.0K 464M 1% /dev/shm
tmpfs 464M 6.2M 458M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 41M 22M 20M 53% /boot
/dev/sda1 299G 149G 150G 50% /mnt/passport
tmpfs 93M 0 93M 0% /run/user/1000

nomoreme commented Jun 2, 2018

I don't think I have any space isuue:

Filesystem Size Used Avail Use% Mounted on
/dev/root 30G 3.0G 26G 11% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 8.0K 464M 1% /dev/shm
tmpfs 464M 6.2M 458M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 41M 22M 20M 53% /boot
/dev/sda1 299G 149G 150G 50% /mnt/passport
tmpfs 93M 0 93M 0% /run/user/1000

@Rainee4563

This comment has been minimized.

Show comment
Hide comment
@Rainee4563

Rainee4563 Jun 9, 2018

I'm also having this problem this is what im getting when I do

sudo systemctl status raspotify

Main PID: 1458 (librespot) CPU: 1.209s CGroup: /system.slice/raspotify.service └─1458 /usr/bin/librespot --name raspotify (RaineePi) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-volum e --initial-volume=100 Jun 09 07:22:49 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:49 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:22:54 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:54 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:22:59 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:59 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:23:04 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:23:04 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:23:09 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:23:09 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed

Rainee4563 commented Jun 9, 2018

I'm also having this problem this is what im getting when I do

sudo systemctl status raspotify

Main PID: 1458 (librespot) CPU: 1.209s CGroup: /system.slice/raspotify.service └─1458 /usr/bin/librespot --name raspotify (RaineePi) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-volum e --initial-volume=100 Jun 09 07:22:49 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:49 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:22:54 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:54 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:22:59 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:22:59 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:23:04 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:23:04 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed Jun 09 07:23:09 RaineePi librespot[1458]: ERROR:librespot_playback::audio_backen d::alsa: Alsa error PCM open -16 Jun 09 07:23:09 RaineePi librespot[1458]: ERROR:librespot_playback::player: Coul d not start audio: Alsa error: PCM open failed

@BugRogers42

This comment has been minimized.

Show comment
Hide comment
@BugRogers42

BugRogers42 Jun 12, 2018

ok, so the last update fixed the problem for me. But a few days ago spotify released another update and now raspotify again disapears immediately in spotify. Also when i restart the service.

BugRogers42 commented Jun 12, 2018

ok, so the last update fixed the problem for me. But a few days ago spotify released another update and now raspotify again disapears immediately in spotify. Also when i restart the service.

@Rainee4563

This comment has been minimized.

Show comment
Hide comment
@Rainee4563

Rainee4563 Jun 12, 2018

I was able to fix it by installing it along side spotify web connect

Rainee4563 commented Jun 12, 2018

I was able to fix it by installing it along side spotify web connect

@teddycool

This comment has been minimized.

Show comment
Hide comment
@teddycool

teddycool Jul 27, 2018

Hi,
I have this problem as well on a fresh install of 2018-06-27-raspbian-stretch-lite on a raspberry pi 3.
I agree that this makes the raspotify allmost useless. It plays a couple of tracks and then disconnects.
A restart of the service solves the problem though.
I have not filled the sdcard, its alot of free space. I have played with the settings but for me it hasn't changed the behaivour.
In the future I will also use the spotify web api from python (spotipy) to show artist and track names on a display and maybe that solves the issue as it did for Rainee4563 .
In case I can contribute with logfiles or tests to help solve the prorblem, please let me know.

teddycool commented Jul 27, 2018

Hi,
I have this problem as well on a fresh install of 2018-06-27-raspbian-stretch-lite on a raspberry pi 3.
I agree that this makes the raspotify allmost useless. It plays a couple of tracks and then disconnects.
A restart of the service solves the problem though.
I have not filled the sdcard, its alot of free space. I have played with the settings but for me it hasn't changed the behaivour.
In the future I will also use the spotify web api from python (spotipy) to show artist and track names on a display and maybe that solves the issue as it did for Rainee4563 .
In case I can contribute with logfiles or tests to help solve the prorblem, please let me know.

@teddycool

This comment has been minimized.

Show comment
Hide comment
@teddycool

teddycool Aug 3, 2018

In the log it hints about a spotify problem (reset by peer) but this is not the case since I have several spotify connect units in the same network that works perfecly for hours and hours (volumio with spotify connect on the same type of pi is one example). However I would like to use Raspotify instead since it's a service running in the background without any 'fuzz' or extras... But maybe it dosn't like Motorhead... ;-)
Jul 28 07:51:22 spotipi librespot[498]: INFO:librespot_core::session: Country: "SE"
Jul 29 17:21:07 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Cat Scratch Fever" with Spotify URI "spotify:track:1uH06nM0HEsbCqvdaqzwa5"
Jul 29 17:21:09 spotipi librespot[498]: INFO:librespot_playback::player: Track "Cat Scratch Fever" loaded
Jul 29 17:22:23 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Killed by Death" with Spotify URI "spotify:track:4W2CRPuOl8wN3aR7QmOmQE"
Jul 29 17:22:25 spotipi librespot[498]: INFO:librespot_playback::player: Track "Killed by Death" loaded
Jul 29 17:23:15 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Electricity" with Spotify URI "spotify:track:1KYfhcM7K7Ahs6opoG4cd0"
Jul 29 17:23:17 spotipi librespot[498]: INFO:librespot_playback::player: Track "Electricity" loaded
Jul 29 17:25:33 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Evil Eye" with Spotify URI "spotify:track:1jsZ5wEBDUioHIWvOmHP4g"
Jul 29 17:25:35 spotipi librespot[498]: INFO:librespot_playback::player: Track "Evil Eye" loaded
Jul 29 17:27:55 spotipi librespot[498]: ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

teddycool commented Aug 3, 2018

In the log it hints about a spotify problem (reset by peer) but this is not the case since I have several spotify connect units in the same network that works perfecly for hours and hours (volumio with spotify connect on the same type of pi is one example). However I would like to use Raspotify instead since it's a service running in the background without any 'fuzz' or extras... But maybe it dosn't like Motorhead... ;-)
Jul 28 07:51:22 spotipi librespot[498]: INFO:librespot_core::session: Country: "SE"
Jul 29 17:21:07 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Cat Scratch Fever" with Spotify URI "spotify:track:1uH06nM0HEsbCqvdaqzwa5"
Jul 29 17:21:09 spotipi librespot[498]: INFO:librespot_playback::player: Track "Cat Scratch Fever" loaded
Jul 29 17:22:23 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Killed by Death" with Spotify URI "spotify:track:4W2CRPuOl8wN3aR7QmOmQE"
Jul 29 17:22:25 spotipi librespot[498]: INFO:librespot_playback::player: Track "Killed by Death" loaded
Jul 29 17:23:15 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Electricity" with Spotify URI "spotify:track:1KYfhcM7K7Ahs6opoG4cd0"
Jul 29 17:23:17 spotipi librespot[498]: INFO:librespot_playback::player: Track "Electricity" loaded
Jul 29 17:25:33 spotipi librespot[498]: INFO:librespot_playback::player: Loading track "Evil Eye" with Spotify URI "spotify:track:1jsZ5wEBDUioHIWvOmHP4g"
Jul 29 17:25:35 spotipi librespot[498]: INFO:librespot_playback::player: Track "Evil Eye" loaded
Jul 29 17:27:55 spotipi librespot[498]: ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

@abrakadabra2k

This comment has been minimized.

Show comment
Hide comment
@abrakadabra2k

abrakadabra2k Sep 12, 2018

Any update on this issue? I am seeing the same behavior on the most recent moobe built. (and also on volumio, by the way. Connecting to a chrome cast works perfectly, on the other hand)

abrakadabra2k commented Sep 12, 2018

Any update on this issue? I am seeing the same behavior on the most recent moobe built. (and also on volumio, by the way. Connecting to a chrome cast works perfectly, on the other hand)

@romainp

This comment has been minimized.

Show comment
Hide comment
@romainp

romainp Sep 25, 2018

Same error. Stops playing after a couple songs.

Sep 25 20:26:33 raspberrypi librespot[1025]: WARN:mdns::fsm: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }

romainp commented Sep 25, 2018

Same error. Stops playing after a couple songs.

Sep 25 20:26:33 raspberrypi librespot[1025]: WARN:mdns::fsm: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }

@romainp

This comment has been minimized.

Show comment
Hide comment
@romainp

romainp Oct 1, 2018

removing pulseaudio solved the issue for me! Working great now, love it!

romainp commented Oct 1, 2018

removing pulseaudio solved the issue for me! Working great now, love it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment