Slow Search Issues

Hi Noris. The dns resolution errors do only occur on booting the rock machine which as mentioned is a result of the switch runnig STP as part of any device being connected and this denies any connection on the port for 30 secs whilst it checks all is ok.

This seems to make Roon server go in a panic and won’t connect to streaming services even after it’s all connected and has network/internet. It’s like it doesn’t bother retrying or has completely timed out, even if I press retry at the failed login prompt in Roon remotes UI. Only manually restarting just Roon server application will make it connect. This is a bit annoying any reason why Roon gives up like this. Is it because it’s not set the dns servers? Perhaps setting it to fixed up might help with it?

This aside still getting slow searches but Radio has been fine. I think the dns errors are a red herring for this issue though as they only happen as I said on boot due to the switch.

Hello @CrystalGipsy,

We are investigating some DNS reports on ROCK and I have seen a similar failure state. Can I please ask you to follow these instructions so I can add your report to the investigation?

  • Restart RoonServer from the WebUI (do not reboot the entire ROCK but just RoonServer)
  • Create an archive of the current Logs (https://kb.roonlabs.com/Logs) and name it “Fresh_state.zip”
  • Reboot ROCK from the webUI (the entire machine, not just RoonServer)
  • Create another archive of the current Logs and name it “Rebooted_ROCK.zip”
  • Check to see if you are able to access the network/ play TIDAL content
  • If you are not able to, go back into the WebUI and reboot just RoonServer again
  • Make another archive of the logs and name them “Rebooted_RoonServer_only.zip”

At the end of this process you should have 3 .zip files - Fresh state, Rebooted ROCK and Rebooted RoonServer only. I kindly ask you to upload these .zip files to our servers for analysis (I will PM you upload instructions in a min) and I will add this info to the investigation.

Thanks,
Noris

Sorry missed this last night. I will do this asap and let you know.

1 Like

Hey @CrystalGipsy,

I wanted to touch base with some good news, which is that our technical team has been able to reproduce this behavior and we’ve opened up a bug report with our developers.

While I can’t say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and I will keep this thread up to date as the team passes along feedback and work begins to get this resolved. Thanks again for the report!

– Noris

Thanks for the update. Nice to know I don’t have to change any of my network gear.

Hi @CrystalGipsy,

Appreciate your patience while we made some improvements in this area. We have just released Roon OS build 172 which addresses this issue, thanks again for your help here!

– Noris

1 Like

Great stuff all works now.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.

Hi @support I am once again finding that Roons searches are slow .It’s taking on average 6-8 seconds to bring up results. I just did a search for The Beatles which I imagine is a popular search and via Roon this took around 7 secs this seems quite excessive compared to Tidal and Qobuz apps on same PC took about 1 and feels pretty much instant. It does seem that since Qobuz and the new search algorithms the whole process has got a lot slower. Whist I understand Roon is also looking at my own library as well as the streaming services I hope this is still teething problems and this gets optimized soon. I don’t have a large library only 2500 albums and more core is an i7 with 8GB with a 200mb internet. If I logout of Tidal and Qobuz then search is pretty much instant for the same query so searching the streaming services seems to be the culprit of it being slow or at least a symptom.

Hi @CrystalGipsy,

Do you mind reproducing this issue and then letting me know a timestamp of this slowness? I’d like to see if diagnostics can shed some light on where the issue lies.

Thanks,
Noris

Hi Norris a reboot of core seems to have sped things up for now . My worry here is that this slowness happens over time and I should not have to do this to clear it up. I will feedback in a few days to see if it gets slower as the machine had only been up for days prior to this reboot.

1 Like

@noris so 19.10 this evening unbelievably slow to load any artist and its list of album.

Hi @CrystalGipsy,

Sorry for the delay here, can you please let me know what Roon Remote you were using at the time?

– Noris

Android phone this last time. If have noticed that this remote is really bad compared to my android tablet and windows laptop. It takes ages to load albums.

So tonight 23:58 GMT roon cant find The Blue Nile in under a minute, internet perfectly fine to. I have two albums in my local collection…Sorry nut something is really not right.

Hello @CrystalGipsy,

Apologies for the delay in getting back to you here, we have been actively discussing this issue internally to figure out a test plan and gather results for an investigation. We are now asking users to run a test so that we can have a better baseline of factors surrounding this issue.

Can you please this test the next time you’re in this state and respond with the exact local time that you start the test (e.g. 11:38AM) and the time that each step takes:

  1. Run a speed test here and report your results in your response
  2. Open Overview page.
  3. Open Discover page.
  4. Perform a search for “The Beatles”.
  5. Open “The Beatles” artist page.
  6. Open the “Help!” album page.
  7. Start playback of “Help!” (how long does it take before it plays?).
  8. Search for “Daft Punk”.
  9. Open the “Daft Punk” artist page.
  10. Open the “Random Access Memories” album page.
  11. Start playback of “Random Access Memories”.

I’m hoping that we can compare the results from this test to other user reports and if possible identify any common patterns. I noticed in another thread that you mentioned that you have different response times when using Android vs PC, if you can please run this test on both, that would also give us a good data point.

Thanks,
Noris

I just had an issue right now on Windows loading Magical MysteryTour from The Beatles which is on Qobuz took at least 30secs to load it. . Help I have in local Library so it loaded straight away, the rest load ok today they have at other times not done.

Speed is 102mb/s with 9ms latency.

Hi @CrystalGipsy,

I’m checking the diagnostics from your core and unfortunately I am seeing a whole lot of NameResolutionFailures:

	Line 246: 04/08 18:21:10 Warn: [tidal/http] GET https://api.tidalhifi.com/v1/sessions/0da998e0-d4e6-4728-9954-ecdaa9dbbe7f?token=Imi5DLPIAVRmszdL& => NetworkError Error: NameResolutionFailure
	Line 248: 04/08 18:21:10 Critical: [easyhttp] web exception without response: : System.Net.WebException: Error: NameResolutionFailure
	Line 258: 04/08 18:21:10 Warn: [qobuz] [http] error result from http request: System.Net.WebException: Error: NameResolutionFailure
	Line 293: 04/08 18:21:10 Warn: Error in web request https://api.tidalhifi.com/v1/sessions/0da998e0-d4e6-4728-9954-ecdaa9dbbe7f?token=Imi5DLPIAVRmszdL&: NetworkError (Error: NameResolutionFailure)
	Line 294: 04/08 18:21:10 Warn: [tidal/http] GET https://api.tidalhifi.com/v1/sessions/0da998e0-d4e6-4728-9954-ecdaa9dbbe7f?token=Imi5DLPIAVRmszdL& => NetworkError Error: NameResolutionFailure
	Line 296: 04/08 18:21:10 Critical: [easyhttp] web exception without response: : System.Net.WebException: Error: NameResolutionFailure
	Line 306: 04/08 18:21:10 Warn: [qobuz] [http] error result from http request: System.Net.WebException: Error: NameResolutionFailure

Has anything changed here with regards to how you have your setup configured? I recall that you updated to Roon OS build 174 already but something might still be triggering a DNS issue. If you only reboot just RoonServer from the WebUI, does search work as expected?

Thanks,
Noris

No nothing has changed. I did power of the core twice last night as was experimenting with power supplies so that might account for it as it takes a while for my switch to allow connections on boot due to STP, but that time is before I was home unless it’s not counting for daylight saving time. But it was working and connecting to Tidal and Qobuz after the 30sec period.