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
Shairport-sync failed to start #829
Comments
here is the status of the service
|
Hmm, that's curious alright. Could you edit the configuration file at
it would be very useful. There's more here. |
Closing this. Please feel free to open another issue if necessary. |
@mikebrady Mind reopening this? I think I've got a similar situation here. I'm using a rpi aswell.
Strangely enough, running it directly in the terminal without systemd seems to work just fine.
|
Thanks for the post. If you set the verbosity to 1, restart ( |
Absolutely.
journalctl -xe:
|
Thanks – that's all useful. It's really peculiar that Shairport Sync itself appears to be shutting itself down. Unfortunately, the early part of the log is missing, and some of it might be useful. I'd be looking for something like this:
Could you see if you could fish it out, please? You might have to search a bit further back through the logs. |
I don't really know where to find that. Should i try running with --daemon? |
No. If you use a command like this:
... it will log the last 300 lines of log entries ( |
edit: This all seems to have to do with #874 & #879. Probably just ignore this whole comment. It looks like this is fixed in the version of shairport-sync available in Debian/Raspbian Testing, but not the one in Debian/Raspbian Stable. For me, running shairport-sync installed through apt on a Raspberry Pi 4 with a fresh installation of Raspbian Lite (fully updated), I get this issue when configuring the I haven't tested to see if any other config variables give it trouble. (Log verbosity seems to work...)
This will repeat several times. When it does start successfully, the "free(): double free detected in tcache 2" line doesn't show up:
(I am aware this isn't the most recent version of shairport-sync, but it is the most recent version available on Raspbian Stable.) |
I’ve got the same issue when trying to override the |
Thanks for the post. That is a bug alright, and it has been fixed in recent versions of Shairport Sync. The version in Raspbian, unfortunately, still contains it. The updated version is now in Debian backports, so it'll be a matter of time before it becomes available in the Raspbian package system. Alternatively, you could build the latest version from here. Instructions are at INSTALL.md. If you do so, be sure to pay close attention to cleaning up before building and installing, as detailed on the page. |
Manually installing the latest version from master solved it. Thanks. :) |
Sadly still not updated. Is there a way to reach out to the repo maintainers and urge them to update due to it having a breaking bug? |
I encountered an issue similar to this and #874 where Shairport-sync would not start if I manually edited the name="" in the /etc/shairport-sync.conf file. I could however, start Shairport-sync manually with the --name= option and it was fine. My issue at least, was resolved by removing v3.2 found in the raspiOS repo and installing manually. |
This issue has been inactive for 60 days so will be closed 7 days from now. To prevent this, please remove the "stale" label or post a comment. |
I have a new install of shairport-sync. Currently when i run the service it is showing code=exited, status=1/Failure states failed with result 'exit-code'
I am trying to find out why this is not starting properly
The text was updated successfully, but these errors were encountered: