Thank you again for your ongoing patience as we work to isolate symptoms for each case reported here. As noted above, we have identified one potential mechanism for the behavior reported, and the next step is to cross-index against the individual reports above. Thus, the call for technical detail and our unusually tight enforcement of #support posting guidelines within this thread.
As a next step, we want to request a few volunteers to run Roon with a Command Flag to activate more granular logging for our developers. The specific Command Flag here is -perftimers; Iāve included instructions for each operating system below.
Please note: activating the -perftimers command line flag will create highly verbose logging in RoonServer/Roon logs.
Windows RoonServer/Roon Machine (All-In-One)
Right-click the Roon icon and select āpropertiesā from the drop-down menu
You will see a text input field titled āTargetā. At the end of the ātargetā input line, add -perftimers.
Make sure the āstart inā input field ends with āapplication folderā and nothing else
Start Roon by double-clicking on the shortcut
Reproduce the problem within Roon and ARC
Please post here to let us know that youāve volunteered to start with the flag.
Mac RoonServer/Roon Machine (All-In-One)
Open Terminal (Applications/Utilities ā Terminal)
Please post here to let us know that youāve volunteered to start with the flag.
Linux RoonServer Machine
Find and open the RoonAppliance startup script. This file is /opt/RoonServer/Appliance/RoonAppliance by default, but individual Linux installations may vary
Add the flag to the end of the last line in the script, giving something like: exec "$HARDLINK" --debug --gc=sgen --server "$SCRIPT.exe" "$@" -perftimers
Restart RoonServer. To do this, open a terminal and type sudo pkill start.sh You will be prompted for your password, type it in and then press enter, then wait for RoonServer to be restarted.
Reproduce the problem within Roon and ARC
Please post here to let us know that youāve volunteered to start with the flag.
Create a simple text file in that directory with the following name (all one word, no caps, no extension): roonserverargs
Inside that file, add one line with the command flag requested: -perftimers
Restart RoonServer in the ROCK web interface: type āROCKā into the address bar in any web browser, then click the ārestartā button under āRoon Server Softwareā
After recreating the issue and posting here to notify Roon Support, remember to go back and delete the roonserverargs file.
Please post here if youāre willing to activate more granular logging with the -perftimers command line flag. Weāll be awaiting your response. Thank you again!
Note that you need to remove the space in the command line where it says " Roon.app". I closed the Roon server when I ran the command the first time, but that resulted in ARC app not working from the start. 2nd time I left the Roon server running and now it seems to work. Itās correct that the command line keeps open and running logging?
Edit: wish I hadnāt now
My Windows machine now keeps crashing and needs a full power down to get going again, until Roon restarts and then does it all over again. Had to quite Roon server and stop it starting on reboot.
Greetings,
Iāve been using Roon ARC for several months both from my car and local network. My Roon core (2.0) is installed on a large QNAP NAS and always shows as running.
It is always unstable, especially when using remotely. It may start playing ok, then go into the spinning wheel, or error with Core Unreachableā¦ā¦
Roon ARC is no longer a new software product. Surely there is a definitive setup program or at least instructions. At the moment it is unusableā¦.
Cheers,
Steve
@connor - my core has gone into zombie mode again today. I have the logs (with -perftimers enabled), and I also have memory dumps of RoonServer.exe and RoonAppliance.exe. Where can I upload them to?
I havenāt restarted it yet, so let me know if thereās anything else I can capture.
I also have had it happen and have got the logs as well. Happy to upload wherever you need them. I believe in the past a link to upload them to you has been provided?
Thank you, no idea how I managed to look past that when searching for it. Iāve uploaded the logs from the few minutes around time it happened plus the full log that had it in there.
Iāve had this issue happen quite a lot - drives me mad. Restarting the ROCK server fixes the issue.
Trying to diagnose when this happens, it seems to be when I change networks. So if I move from 4/5G to WIFI and back again (using ARC) itāll probably trigger the issue and require a restart before any of the end points are accessible again.
Iāve uploaded my logs as well. The memory dump is bigger than 100mb (even compressed) so let me know if you need it and I can send it some other way.