Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[hoyt]

I spent some time troubleshooting this today, related to the following issue I noticed with the Home Assistant Integration that mattkhan has published (https://yabb.jriver.com/interact/index.php/topic,137808.msg958051.html#msg958051). This only seems to happen if I have MC open on a client on my network. My setup is MC Server running on Windows 11, and MC Client running on Mac. I also have an Amplipi (https://www.micro-nova.com/amplipi) as a DLNA zone.

If I have my client Mac running, the GUI on the Mac will "freeze". I notice this because the Spectrum Analyzer will sit still mid-song. The music keeps playing though. This is also when the HA Integration reports that my MC server becomes unavailable. To be clear, the MC Integration is pointed at my Windows server, not my Mac MC instance. On the Windows server, I have the following that pop up in the log related to these timepoints (192.168.6.227 is my Mac IP):

Code: [Select]

0044325: 10128: Reader: CWinINetReader::Open: ConnectToURL failed, timed out (6000 ms), URL=http://192.168.6.227:52101/AVTransport/control
0044325: 10128: Reader: CWinINetReader::Close: Start
0044325: 2844: Reader: CWinINetReader::DownloadFromHTTPURL: Canceled (checked after HttpSendRequest)
0044325: 2844: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (6048 ms)
0044325: 2844: Reader: CWinINetReader::Thread: Finish (6048 ms)
0044356: 10128: Reader: CWinINetReader::Close: Finish (31 ms)
0044356: 10128: Reader: CWinINetReader::Open: Finish (6079 ms)
0044356: 10128: General: CDLNADeviceServiceCaller::CallServiceFunction: DLNA function call failed or timeout! url = http://192.168.6.227:52101/AVTransport/control function = GetPositionInfo execution time = 6079.42 ms of 6000 ms.
0044356: 10128: Playback: CDLNADeviceControl::GetPosition: GetPosition returned NOT_IMPLEMENTED for RelTime
0044356: 10128: Sharing Plugins: JRWebService::Process: Finish (6079 ms)
0044356: 10128: Sharing Plugins: VHTTPMessage::Write: Wrote 393 bytes
0044356: 10128: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (7377810 ms)
When this happens, the Windows server GUI does not hang (I've had music playing on that so I can watch the Spectrum Analyzer as well). If I close the MC client and output to Player on the Windows 11 device, I see none of this behavior. I'm not sure what's happening, and not sure I totally would understand it, but it seems like my MC server gets pissed off that one client isn't acting like it should and this causes the HA Integration to report that my MC server is unavailable.

I set the DLA Controller to "Ignore Get Position Failures (for broken renderers)", but the problem remains (even after restarting MC on the Mac).

EDIT: I should also add that when this is happening, I have had a ping loop to google.com going on the Mac client. When the "hang" occurs, the pings continue successfully, so I don't think it's a network issue with the Mac.

[bob]

Not sure why the PC wouldn't be able to reach the Mac machine for 6 seconds which it appears to be what the windows log is saying.

Since the Mac is running as a client, you don't need the renderer on the Mac, correct?
You could turn that off in Media Network options (DLNA renderer). It seems like that is what the windows server is trying to query at the time.

[hoyt]

Thanks Bob. I had turned that on for the Mac client to test a different DLNA renderer to check something else and forgot that option even existed (though it was nice to see on the server what my client was playing).

I just disabled that on the Mac, tried a few things and that appears to be avoiding the 6 second timeout that I was seeing before. I even outputted to the other DLNA renderer on my network (the Amplipi) and I'm not seeing the timeouts/ unavailable entries in the HA integration. Still seems odd that JRiver as a DLNA renderer would cause the server to freak out, but I'll take the win.

Thanks!

[markf2748]

Still seems odd that JRiver as a DLNA renderer would cause the server to freak out, but I'll take the win.

I'm not saying you made this mistake, but it has caught me more than once:
It is very important that every machine running MC on the network have a unique DLNA Access Key.  If a client library is restored or copied from a server backup, and All Settings are restored, then the client's DLNA Access Key will be the same as the server's.  This situation can play havoc with MC devices on the network, and it's a real pain to unravel.