You are here: Home » Reply » Reply To: DNS-323 Firefly and Bonjour

Reply To: DNS-323 Firefly and Bonjour

#14637
rpedde
Participant

@drewd wrote:

Ron,

This is the response when it is running:

1330 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1331 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1360 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1361 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf

This is the response after it stopped:

1330 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1331 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1360 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1361 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1480 root grep -i mt-daapd

So….there were four running at the beginning and four after it fell over.

Don’t know what this means….

Drew

It means nothing probably changed on the server. Still advertising, still running. Which means it’s probably a networking issue. I’d still suspect whatever wireless stuff you have between the server and client.

Sadly, I don’t have a fix for that. You could verify it by running wired and seeing if you could replicate the issue.