What is "Sent mDNS discovery list response"?

Support
1

Roon Core Machine

Mac mini 2018, 3 GHz 6-core i5, 64GB Ram

Networking Gear & Setup Details

Netgear GS105NA/GS108 switches, Eero pro 6 wifi, Netgear CM500 Modem, 400MB Cable.

Connected Audio Devices

Devialet expert 150 Pro, Devialet Phantom I Gold, Ropieee/Digi One ->Benchmark DAC3 HGC

Number of Tracks in Library

13,900

Description of Issue

What is “Sent mDNS discovery list response”? I don’t remember seeing it before. Constantly writing on my SSD is not good.

05/14 09:03:06 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:06 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:07 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:08 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:09 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:10 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:10 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:10 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:10 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:10 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:11 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:11 Debug: [airplay/discovery] Sent mDNS discovery list response
05/14 09:03:11 Info: [stats] 36176mb Virtual, 1523mb Physical, 783mb Managed
05/14 09:03:11 Debug: [airplay/discovery] Sent mDNS discovery list response

2

Looks like a multicast discovery as part of airplay.

3

I agree. I don’t have any airplay devices enabled. Why check so frequently? Why continuously write to the log?

4

Perhaps its the airplay capability of the devaliet being looked for by roon.

5

Logs are of no use to the average user, unless he has an issue to investigate.
It would be preferable for the user to be able to disable them or set various logging levels (errors only, debug mode etc.).

1 Like
6

The average user wont look at them at all.

7

Everyone should be concerned about applications constantly writing to their SSD.

8

The average user barely knows what a computer is never mind memory or storage.
I work in a support function :expressionless:

9

According to Roon I have six devices capable of Airplay. None of them are enabled. I don’t see any value in Roon checking on Airplay devices 6-8 times per second.

10

Me neither might be an error. Haven’t the faintest…
I’d wait for proper support after the weekend.

11

Yup, that’s why I posted. Maybe the application is doing something wrong.

1 Like
12

The frequency itself is not a problem.
However, considering that the line starts with ‘Debug’ I think that the Roon team forgot this one.

Normally, in production, you have less logging information and ‘debug’ is certainly one of them.
That also explains why you didn’t see it before, as this is normally not visible in production.

1 Like
13

Lines starting with debug are common in Roon log files. For example, I’ve just done a quick count in my current Roon Server log – there are 16941 lines including ‘trace’, 6663 with ‘info’, and 3547 with ‘debug’.

14

Hmmm… I never check them (expect when reviewing feedback from RoPieee users). I would normally expect debug lines to not show in production, but hey that’s just me :wink:

15

It’s the same in the client log files too – tons of debug lines. And I agree, I wouldn’t have expected quite so many. My only reason for mentioning it was to reassure the OP that it’s not unusual, i.e. not indicative of a problem, in and of itself.

1 Like
16

Better than having no breakpoints or status messages, like the 30,000 lines of cobol that “had an error somewhere” i got given once.

1 Like
17

I power cycled all my network gear (not the Roon server) and the debug messages stopped. I would guess the messages do indicate some kind of network problem. Next time I will get a tcpdump and see what is happening.

18

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