-
Notifications
You must be signed in to change notification settings - Fork 634
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
ERROR does not kill process #241
Comments
Yes, this is still a problem. |
@wfraser You seem to be very fluent in all this multiprocess/multithreading task - could you try to solve this issue? Reproduction requires disconnection of broadband during playing - should be easy to reproduce on virtual machine. |
This is a well known bug, currently being tracked at #134. The problem is that it requires a significant rewrite of parts of librespot, and hence hasn't been fixed. Anyone is welcome to give it a go, in the meantime, closing this in favour of aforementioned issue. |
The scrpt parses parses raspotify's log line-by-line. If "ERROR" shows up, it reboots the system. The reason I need this, is described here librespot-org/librespot#241
I get
ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer"
but the process does not exit, so systemd does not restart it.
In the spotify client librespot will sometimes show up, sometimes not. If I select the speaker after the ERROR (if it shows in the client), the speaker eventually disappears from the client, and I have to manually restart the process on the server.
This might be a duplicate of #226, but this is not a panic, therefore I leave that decision up to someone who knos more than me.
Raspberry Pi 2 model B, running Arch Linux
The text was updated successfully, but these errors were encountered: