Mac Mini M1 2020 (BigSur 11.6)
Roon Server 1.8 (build 831)
Networking Gear & Setup Details
Asus ZenWifi XT8 (Mesh - 1 router + 2 nodes) Firmware: 3.0.0.4.386_42095
Mac Mini connected to WiFi.
Connected Audio Devices
Number of Tracks in Library
21701 tracks
Description of Issue
Roon Server is launched at startup. No problem to use it from Roon Remotes (Desktop or iOS devices). Works well.
However when I stop listening and I come back after a few hours and try to connect with a Roon Remote it can’t find the Roon Core… I have to restart Roon Server on the Mac Mini.
Energy Saver on the Mac Mini is set to:
Never turn the display off
Prevent the computer from sleeping automatically when the display is off
Don’t put the hard disks to sleep when possible
Wake for network access
Don’t start automatically after a power failure
Having to restart Roon Server on the Mac Mini when I want to use Roon is killing part of the fun…
I’m happy to investigate more but don’t know what info would be helpful.
iOS (iPhone, iPad) and Desktop (macOS). All latest version.
On the Mac Mini M1 the Roon Server process starts using 300-400% of cpu and when I look a the system activity the process has written 90GB+ on disk…
I need to stop the server and starts it again.
The problem is with the Roon Server process running on the Mac Mini not with the remote devices
Hey Im also seeing the restart issue with this newer update on M1 Mac mini (B-Sur 11.6) If playing music downloaded, or streamed…if stopped will not continue playing or even skip up or back a track, have to shut Roon down then reopen only takes a second, but this didn’t used to happen…This is the only issue no other major issues but Roon Needs to be written to take advantage of Apples core processors as this will be better for everyone… and needs to happen soon.
Some more info:
On the Mac Mini M1 I’ve Roon Server and Roon installed. I run the Roon Server. This what the Roon Remotes connect to but I can launch Roon on the Mac Mini as Remote connecting to the Roon Server on the same Mac Mini.
I also have an external drive connected to the Mac Mini with 3 partitions which I used for TimeMachine, CarbonCopyCloner and Storage plus some mapped drive to my QNAP TS-453D.
I went to my /Library folder and I’ve 3 Roon folders:
/Roon
/RoonGoer
/RoonServer
I’ve stopped Roon Server and deleted the logs in /Roon/Logs/ and /RoonServer/Logs/ and restarted Roon Server. I’ll see upon the next problem what it’s in the logs and I’ll send them over to you as per the procedure.
Should have started with that to be fair instead of wasting time…
I’m really wondering why Roon Server logs shows multiple warnings about
10/23 12:04:38 Warn: could not run /usr/sbin/diskutil info -plist '/Volumes/.timemachine/0D8BD25F-0107-4F1C-9861-515910418B74/2021-10-19-232748.backup' -- Exit code was: 1
Why is RoonServer even bothering with TimeMachine drives or other external drives???
Everything related to Roon is on the internal Mac Mini SSD “Macintosh SSD” including my own Music library.
Ok it looks like it never recovers from network blips
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [server] Error accepting connection: System.Net.Sockets.SocketException (0x80004005): Network subsystem is down
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x00014] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.Byte[]& buffer, System.Int32& bytesTransferred, System.IAsyncResult asyncResult) [0x0002c] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.IAsyncResult asyncResult) [0x00000] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.TcpListener.EndAcceptSocket (System.IAsyncResult asyncResult) [0x00026] in <f34012a0712d47c3928ecd2def984fcd>:0
at Sooloos.Broker.Distributed.Server.ev_accept (System.IAsyncResult r) [0x0001a] in <a841d4f358904ce7b1ae48527a828f4a>:0
10/24 11:54:18 Warn: [server] Error accepting connection: System.Net.Sockets.SocketException (0x80004005): Network subsystem is down
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x00014] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.Byte[]& buffer, System.Int32& bytesTransferred, System.IAsyncResult asyncResult) [0x0002c] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.IAsyncResult asyncResult) [0x00000] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.TcpListener.EndAcceptSocket (System.IAsyncResult asyncResult) [0x00026] in <f34012a0712d47c3928ecd2def984fcd>:0
at Sooloos.Broker.Distributed.Server.ev_accept (System.IAsyncResult r) [0x0001a] in <a841d4f358904ce7b1ae48527a828f4a>:0
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [server] Error accepting connection: System.Net.Sockets.SocketException (0x80004005): Network subsystem is down
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x00014] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.Byte[]& buffer, System.Int32& bytesTransferred, System.IAsyncResult asyncResult) [0x0002c] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.Socket.EndAccept (System.IAsyncResult asyncResult) [0x00000] in <f34012a0712d47c3928ecd2def984fcd>:0
at System.Net.Sockets.TcpListener.EndAcceptSocket (System.IAsyncResult asyncResult) [0x00026] in <f34012a0712d47c3928ecd2def984fcd>:0
at Sooloos.Broker.Distributed.Server.ev_accept (System.IAsyncResult r) [0x0001a] in <a841d4f358904ce7b1ae48527a828f4a>:0
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
10/24 11:54:18 Warn: [multicastsocket] in readloop async cb: The socket is not connected
logs filled with this…
Network is working just fine. I’m on the Mac Mini using it.
Thanks a whole lot for adding information to this thread. We’d love to help figure out what is going on. I wonder if you could grab the whole Logs folder and upload it here?
Once you had a moment to upload the files, could you please let us know? Thx
Hello to everyone,
I have the exact issue described by @Frederic_Soulier.
Apple Mac Mini M1 8GB/256 SSD Big Sur 11.6.1
Connected via Gigabit Ethernet, energy savings disabled (it’s my home server)
After a few hours the roon server app is using a lot of memory and doesn’t respond anymore; I have to shutdown and restart the roon server app.
Also having issues with a Mac Mini M1. Won’t load any music or find any devices including the Mac Mini itself! Started a separate thread. I hope someone can investigate soon.
Aloha!
Hi @beka
Is there any news? It’s been 3 weeks…
Once Roon Server gets in a pickle the whole wifi subsystem is not working… As soon as I quit Roon Server the Mac Mini M1 comes back to life with wifi working again…
I’m a lifetime Roon subscriber. I can’t enjoy Roon Server because I have to avoid running it…
For what it’s worth I have a Mac Mini M1. 256/8gig 12.xx The one I bought in June of this year had a major issue. Rebooting. This occurred right out of the box. I spent hours with Apple support to no avail. Got them to warranty the mini and problem solved.
I had the same issue (before Roon completely broke with update 880) of having to quit and restart Roon every time I move away from the app after some time.
Mac Mini, 11.4. Roon 1.8 (previous build to 880)
Updated Roon Server to latest version (1.8 build 884) yesterday in the vain hope something may have been fixed.
This morning my Mac Mini M1 had rebooted…