Roon 1.8 (Legacy) Metadata Improver Paused and New Tracks Not Identified (ref#US4NBX)

Support
1

What’s happening?

· Something else

How can we help?

· I'm having trouble adding music to my library

Describe the issue

I'm on Roon 1.8 (Legacy) and have added music to my ROCK. None of the new tracks I have added have been identified and "Metadata Improver" has been paused.

Describe your network setup

Router: ASUS ROG Rapture GT-AXE16000
ROCK: Intel NUC8i3BEH3

2

Hi,

Check out this page from the Roon’s Help site …

Hope it helps you to resolve this issue, if not Roon’s support team will be along to help.

3

I’ve already tried some of these solutions.

Upgrading to Roon 2.0 isn’t for me and I’m on the latest version of Roon 1.8 (Legacy) (Version 1.8 (build 1151)).

Thanks.

4

To save time when Roon’s support team engage with this, can you list what troubleshooting steps you did try.

5

Hi @Kuch_Kuch,

We’ve been able to reach the ROCK to examine diagnostics. RoonOS has logged repeated network reachability failures since 9/18; basic upstream requests to timeservers, Roon’s device identification and metadata database servers, and account servers have all failed. Furthermore, the machine isn’t listing an active ethernet connection.

The identifier is queueing albums that have failed to identify on import, but the network failures have already at that point unauthorized the session. When network reachability is restored, Roon does appear to import content and identify it.

What is the specific network chain between this ROCK and the internet?

Is there a particular reason you’re resistant to updating to Roon 2.0?

7

ROCK> ASUS Router>ISP Modem>Internet - All connected by Ethernet

Generally heard that searching through music is a faster on Roon 1.8. Makes me hesiitant to try Roon 2.0 when I can’t downgrade.

8
  1. Change the DNS that your network is using

I’ve switched this from ISP to Google

  1. Disable IPv6 on your router and server

Never have enabled this

  1. Remove any managed switches, WIFI repeaters, or powerline adapters from your setup

Only have a Mesh setup with one other node. Don’t have any switches, WIFI repeaters, or powerline adapters on my network. ROCK is directly connected to my ASUS router.

  1. Disable any VPN, firewall, and antivirus running on your server

Don’t have any on my server to my knowledge

I’ve also tried a reboot and shutdown :slight_smile:

1 Like
9

Hey @Kuch_Kuch,

Can you allocate additional network bandwidth to your ROCK? Perhaps testing out different cables/ports would be helpful as well.

10

Apologies for the late response @benjamin - I’ve been out of the country for a few days.

Not sure how to allocate additional bandwidth to it. I’m with a service provider that provides me with 500MB/sec download and 30MB/sec upload and am surprised ROCK can’t work with this considering there isn’t much going on with my network.

I’m happy to try another Gigabit Port on my router. If there is a particular ethernet cable you suggest please let me know. I’m using Amazon Basics Cat6 cables at the moment.

11

I take it you have tried rebooting the server and restarting your network gear as a first step? If not then restart all network gear. Power them all off. Then switch on one at a time with modem/router/switch. Then reboot your server.

12

Hi @Kuch_Kuch,
You can try 2.0 without losing the ability to revert to 1.8 by following the below steps.

  • Stop RoonServer from running in ROCK’s WebUI
  • Navigate to your ROCK’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart the RoonServer in the WebUI to generate a new Roon database folder
  • On the Roon Remotes find the folder that says “Roon”
  • Rename the “Roon” folder to “Roon_old”
  • Restart the remotes and press “Use another Roon Server” and connect to the new database

You can revert to 1.8 by simply deleting the 2.0 folders and then removing old from the names of the 1.8 folders.

13

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