Closed dasl- closed 10 months ago
Thanks for the report. The log looks to show a new connection (Connection 12) attempting to supplant an existing one (Connection 4), but then it terminates for no obvious reason. I might push out an update to add a diagnostic to see why that might be happening.
I just pushed an update that should log something if the client drops the connection, as might be happening in that log above. It's a bit noisy -- there is other stuff being watched for too...
Excellent, thank you. I just upgraded to the latest development version. I'll reply again if / when this recurs.
Thanks. Just doing some checking with various sanitizer tools on Clang/FreeBSD and some data races are surfacing. I'll keep you posted with any updates.
Just pushed an update with those data races fixed -- it just might make a difference... Whenever you got a chance to try it, it would be great to get some feedback.
Great, I just upgraded to the latest development version. Will continue to look out for any recurrences of the issue!
Hi, earlier today I tried to connect my iOS client to SPS. The client got another "Airplay: Unable to connect to <SPS server name>"
error message. This time, however, the server segfaulted - in my original bug report, the server did not segfault. So perhaps this is a different bug than my original bug report?
Here are the logs regardless: https://gist.github.com/dasl-/f4ee52a6bde927cd23c22053c2fb4256
Here is the output of --displayConfig
also: https://gist.github.com/dasl-/50bfef011b3b02d10ade50617546c45d
Unfortunately I did not have coredumps enabled on this SPS server. But I've enabled them now so I can capture the coredump next time.
Many thanks. This looks a lot like a bug we've been chasing over at Issue #1723 -- I was lucky enough to find a replicable procedure for causing an anomaly and managed to push an update about 15 hours ago. As ever, if you got a chance to update and keep a lookout, it would be appreciated.
Great, will do - I just upgraded to the latest development version.
Hello again! Today I tried to connect from my iOS 16.1.1 client, and I received the "Airplay: Unable to connect to <SPS server name>"
error again.
Here are logs: https://gist.github.com/dasl-/ccf2fba3f06d53fef2b536dd1336e527
I think the timeline in these logs is:
Here's --displayConfig on the server: https://gist.github.com/dasl-/e66dfc4f94ce1a4e62898f5baeed91ac
There was no segfault / crash. The SPS server continued running throughout all of this, and a restart of SPS was not necessary.
Just to be clear, I consider this an incredibly minor inconvenience at most - reconnecting solves it, and 99.9% of the time SPS is working perfectly :)
Thanks for this! It looks like it didn’t like something in the pair-setup sequence. Hmm.
This issue has been inactive for 28 days so will be closed 7 days from now. To prevent this, please remove the "stale" label or post a comment.
What happened?
When trying to connect to SPS from a iOS client, I sometimes get an error in the client UI:
"Airplay: Unable to connect to <SPS server name>"
This has happened once on 2 separate SPS servers I have so far. I can try to collect more data over time to try to narrow down what causes the problem.
Restarting SPS solves the problem.
I upgraded SPS to a newer version in the past couple weeks, so I am wondering if there was possibly a regression recently. Of course it could also be a coincidence and unrelated to upgrading SPS.
Relevant log output
System Information.
SPS server is raspberry pi 3A using builtin DAC. Client is iOS 16.1.1
Configuration Information.
PulseAudio or PipeWire installed?
How did you install Shairport Sync?
Built from source
Check previous issues