-
Notifications
You must be signed in to change notification settings - Fork 466
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 metadata log errors in snapserver #891
Comments
Just tried updating to Snapserver 0.25.0 from https://github.com/badaix/snapcast/releases/tag/v0.25.0, and compiled/installed Shairport-sync 3.3.8 from sources. Still getting the exact same metadata log errors. Also was just keeping an eye on the logs when connecting/playing music through Shairport-sync from my phone, and the messages went away as soon as I started playing, since then there was some amount of metadata. Even after I disconnected, the messages didn't return. So looks like when it's first starting up, if nothing connects to the Airplay endpoint(s), it assumes because nothing has come in yet, there's no metadata and keeps checking and erroring. Not sure how, if possible, to fix this so it doesn't fill up any log files. |
This exact behavior is commented in the source: // For some reason, EOF is returned until the first metadata is written to the pipe.
// If shairport-sync has not finished setting up the pipe, bad file descriptor is returned.
LOG(INFO, LOG_TAG) << "Waiting for metadata, retrying in 2500ms\n";
wait(pipe_open_timer_, 2500ms, [this] { pipeReadLine(); }); Whoever uses Shairpoint with metadata will eventually get rid of this message, so I don't think that the log severity must be lowered. |
I would request the log severity be lowered after all- I mostly use other sources than shairport so my logs get spammed up pretty good until eventually someone listens to something over airplay. |
I would also like to see this log severity changed. |
@capocasa @mill1000 I’ve had the same issue and now I’m using this configuration in
Suppresses all INFO-level messages, but only those from Airplay. Since I rarely use Airplay, that’s a good compromise for me. Maybe it works for you as well. |
Nice trick! 👍 |
Could be fixed in v0.28.0-beta.1 with fcac07b As I don't have a Shairportsync setup running, I didn't test it. |
@mill1000 @capocasa @Drizzt321 @MJochim |
I've been running 0.28.1 for a few days now. It looks to be working OK. I have noticed that
|
Thanks for testing @mill1000, good catch, there could indeed be more than one instance of the airplay stream. Should be fixed now. |
Fixed in version 0.28.0 |
Similar to #672, I'm seeing metadata read errors from shairport-sync
And I just keep getting the last message continuously. Tried with only a single airplay source defined, same thing.
My /etc/snapserver.conf
Unlike in #672, I'm not seeing the
HAS_EXPAT not defined
issue, so things seem good there. And the shairport-sync is compiled with the metadata, and in shairport config I have metadata enabled/etc/shairport-sync.conf
And when I run the shairport-sync manually with the verbosity turned on, based on a ps listing from when snapserver is up and running, how it started one of the inputs.
Environment details
The text was updated successfully, but these errors were encountered: