-
Notifications
You must be signed in to change notification settings - Fork 446
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 Problem: (AirplayStream) Error opening metadata pipe #672
Comments
By the way: Everything else works fine |
hello! I have same issue |
Looks like it has been build without this expat support? |
i compiled shairport-sync from source with commands referred in snapcast docs |
Ok, but I'm talking about snapcast. Expat is an XML library, I guess that shairport sync provides meta information in XML format |
snapcast I installed from the Debian package |
The development snapshot is now built with expat: |
Used the release package snapserver_0.20.0-1_armhf.deb |
Can you please test the development snapshot linked above? |
I cleaned everything up and then used the 0.21 development release but it did not create any config files. Now everything is there but the error still exists. Repeating
|
What config file is missing?
Did you compile Shairport-sync with the |
still have same issue with 0.21 i compiled Shairport-sync with this command:
|
Yes |
Does the 0.21 still print this log line?:
|
Here is a full reproduction. I'm on a Raspberry Pi 3b with Raspbian Buster.
Now let's get a fresh shairport-sync binary.
With shairport-sync being set up. I take the 0.21 deb and install it.
No config files
Start the server just like that
|
So the expat warning disappeared, one problem solved. code: pipePath_ = "/tmp/shairmeta." + cpt::to_string(getpid()) + "." + cpt::to_string(port_);
params_ = params_wo_port_ + " \"--metadata-pipename=" + pipePath_ + "\" --port=" + cpt::to_string(port_); This |
no reponse, closing |
I'm running into this same error message:
I'm running v0.22.0-1 from the debian build along with shairport-sync v3.3.5 from buster-backports. Everything works fine, you just get the error reported. It also looks like snapserver isn't cleaning up old fifo's on close either as is seen below: ps output showing the processes
shairmeta files in /tmp
|
Just tried it out: compiled and configured
so everything is fine: snapserver launches |
Snapserver will now delete the pipe on exit |
I had a related error yesterday while trying to compile the
For completeness, the enabled code (https://github.com/badaix/snapcast/blob/master/server/streamreader/airplay_stream.hpp):
|
I have this issue with Debian packages on 0.26 |
You need to call
see fdcdf8e |
For some reason I get a repetitive message saying
[Error] (AirplayStream) Error opening metadata pipe, retrying in 500ms. Error: assign: Bad file descriptor
although meta data support seems to be enabled by shairport.System: Raspbian Buster
snapserver output
Two thing that fell into my eye.
[Info] (AirplayStream) Metadata support not enabled (HAS_EXPAT not defined)
and of course the actual error
[Error] (AirplayStream) Error opening metadata pipe, retrying in 500ms. Error: assign: Bad file descriptor
I did a
ps
to see with what parameters shairport-synv was started. I then started it separately with-vvv
parameter and got this output.command:
/usr/local/bin/shairport-sync --name=Multiroom --output=stdout --use-stderr --get-coverart --metadata-pipename=/tmp/shairmeta.23645.5000 --port=5000 -vvv
output:
shairport-sync had been built with
./configure --with-stdout --with-avahi --with-ssl=openssl --with-metadata --with-pipe
like in issue #622/usr/local/etc/shairport-sync.conf
is emptyand
/etc/shairport-sync.conf
is a copy of/etc/shairport-sync.conf.sample
and in its original state./etc/snapserver.conf
has the following changesstream = airplay:///shairport-sync?name=Airplay&devicename=Multiroom
and
codec = ogg
Looks all more or less fine to me. What can be wrong?
The text was updated successfully, but these errors were encountered: