Issue with UPnP / DLNA Media Interface on Synology NAS

[doncmdr]

In short: When running LMS on a Synology the UPnP / DLNA Media Server disappears from clients less than an hour after starting.

The long version:
I am a first time Synology User, I have installed LMS 7.9.1 from the beta repository.
Currently I am in the process of migrating my LMS from a MACmini to a Synology.

I have a Pioneer AV Receiver that can connect to Media Server to play Music.
I have been using LMS on my MACmini with the UPnP / DLNA Media Interface for some time now to play music on my AV Receiver without issues.
However when I use LMS on my Synology the Media Server appears immediately in the list on the client after I start it, but within an hour the Media Server disappears from the client list and does not show up again until I restart LMS.

On the MACmini I am running Logitech Media Server Version: 7.9.0 - 1488878280
and on the Synology with DSM 6.1 I run Logitech Media Server Version: 7.9.1 - 1504317335

I don't know if it is an MACmini VS Synology issue or a LMS 7.9.0 VS 7.9.1 issue or even something else.
I did not find a way to run a different version of LMS on the Synology, as there is only one version offered by Synology and the LMSRepack repository that I found seems to have shut down.

I set the log level for the UPnP / DLNA media interface to debug level but I could not find any obvious issues.
It seems there is no configuration for that plugin, so there is no setting I can tweak.

Can anyone offer some advice?
I open for suggestions on how to further investigate this.
Did anyone ever experience something similar?

[drmatt]

No direct experience but is it likely the Synology goes to sleep and only wakes on connection using a storage protocol (i.e. cifs/NFS or a browser connection)? I think a second point is that fewer and fewer people are using the NAS builds of LMS when the rPi version is so much better performing and better supported.


Transcoded from Matt's brain by Tapatalk

[pinkdot]

I did not find a way to run a different version of LMS on the Synology, as there is only one version offered by Synology and the LMSRepack repository that I found seems to have shut down.

Indeed, I stopped creating packages for Synology. To time consuming with over 12 different architectures and different OS versions.

No direct experience but is it likely the Synology goes to sleep and only wakes on connection using a storage protocol (i.e. cifs/NFS or a browser connection)?

Could be, but Synology nas don' t hibernate that easily. A lot of packages prevent the nas to hibernate, LMS included. My bet would be on the sloppy LMS update Synology provided.

I think a second point is that fewer and fewer people are using the NAS builds of LMS when the rPi version is so much better performing and better supported.

Better support? Yes, I agree. Better performance? You could be so wrong here, most products in the current Synology portfolio outperform a Rasberry ;-)

[drmatt]

Better performance? You could be so wrong here, most products in the current Synology portfolio outperform a Rasberry ;-)

For I/O I completely agree with you, the Pi is poor, restricted by everything hanging off that USB 2 bus. For CPU horsepower, however, I'd say it's a closer run thing, but totally depending on the model. I know some of the NAS are Celeron or AMD based and will run rings around a pi.

Anyhow, pi is great for running the UI and has more than enough I/O capability to stream media, so I'd call it "right sized" performance...


Transcoded from Matt's brain by Tapatalk

[doncmdr]

No direct experience but is it likely the Synology goes to sleep and only wakes on connection using a storage protocol (i.e. cifs/NFS or a browser connection)?

I don't think its a sleep issue. I can use my squeezeboxes connected to the server at any time.

I decided to move away from a MACmini as server after Apple not updating if for 4 years after making it worse.
Since I have the NAS running anyway I would rather not setup another device like a rPi thats also running all the time even though the power consumption is low.

The NAS also supports Docker, maybe I need to look in that direction if the Synology native packages don't work.

[pinkdot]

The NAS also supports Docker, maybe I need to look in that direction if the Synology native packages don't work.

I wouldn't take the docker route, yet. What Nas do you have?
I'm willing to build a cleaned up version of the package. That way we can see if this issue is caused by Synology, or if something else is causing this.
If this isn't a Synology problem, the Docker route isn't going to help you either (most likely.)

Sent from my Redmi 3S using Tapatalk

[doncmdr]

I wouldn't take the docker route, yet. What Nas do you have?
I'm willing to build a cleaned up version of the package.

@pinkdot: Thank you for offering your help. I have a DS416play.

Yesterday I did some more testing about the issue.
I installed an older LMS 7.9.0 - 1453293926 package on the Synology to see if the issue was introduced with the latest build.
I also installed the latest nightly 7.9.1 - 1512734075 on my MACmini.
After that things did not change. UPnP Mediaserver on MACmini still always available and on the Synology dissappearing after 30min.

I also found out that not only restarting LMS brings the Mediaserver back but also unplugging the Ethernet cable on my AV Receiver for a few seconds seems to trigger an update
of the list of available Media servers.
I don't know enough about UPnP protocol to know if this is related, but I found the following in the log files after plugging in the Ethernet cable again:

17-12-11 17:15:46.8001 Slim::Plugin::UPnP::Discovery::_read (194) M-SEARCH from 192.168.11.131:38583 for upnp:rootdevice (mx: 3)
[17-12-11 17:15:47.2153] Slim::Plugin::UPnP::Discovery::__ANON__ (497) Replying to 192.168.11.131:38583: "HTTP/1.1 200 OK\r\nCache-Control: max-age=1800\r\nDate: Mon, 11 Dec 2017 16:15:46 GMT\r\nExt: \r\nLocation: http://192.168.11.141:9002/plugins/U...Aaa\r\nServer: Linux/x86_64-linux UPnP/1.0 DLNADOC/1.50 LogitechMediaServer/7.9.0/1453293926\r\nST: upnp:rootdevice\r\nUSN: uuid:ED65BBE1-1982-C86F-89EB-450D777CDA45::upnp:rootdevice\r\n\r\n"
[17-12-11 17:15:47.2274] Slim::Plugin::UPnP::MediaRenderer::description (214) MediaRenderer.xml for 00:04:20:26:15:aa requested by dLeyna/0.5.0 GUPnP/0.20.13 DLNADOC/1.50
[17-12-11 17:15:47.3015] Slim::Plugin::UPnP::Discovery::_read (194) M-SEARCH from 192.168.11.131:38583 for upnp:rootdevice (mx: 3)
[17-12-11 17:15:47.5009] Slim::Plugin::UPnP::Discovery::__ANON__ (497) Replying to 192.168.11.131:38583: "HTTP/1.1 200 OK\r\nCache-Control: max-age=1800\r\nDate: Mon, 11 Dec 2017 16:15:47 GMT\r\nExt: \r\nLocation: http://192.168.11.141:9002/plugins/U...A37\r\nServer: Linux/x86_64-linux UPnP/1.0 DLNADOC/1.50 LogitechMediaServer/7.9.0/1453293926\r\nST: upnp:rootdevice\r\nUSN: uuid:997EC018-A870-E981-ABCF-A418EFB85C4C::upnp:rootdevice\r\n\r\n"
[17-12-11 17:15:47.5140] Slim::Plugin::UPnP::MediaRenderer::description (214) MediaRenderer.xml for 00:04:20:28:4e:37 requested by dLeyna/0.5.0 GUPnP/0.20.13 DLNADOC/1.50
[17-12-11 17:15:47.8017] Slim::Plugin::UPnP::Discovery::_read (194) M-SEARCH from 192.168.11.131:38583 for upnp:rootdevice (mx: 3)
[17-12-11 17:15:48.3055] Slim::Plugin::UPnP::Discovery::__ANON__ (497) Replying to 192.168.11.131:38583: "HTTP/1.1 200 OK\r\nCache-Control: max-age=1800\r\nDate: Mon, 11 Dec 2017 16:15:47 GMT\r\nExt: \r\nLocation: http://192.168.11.141:9002/plugins/U...xml\r\nServer: Linux/x86_64-linux UPnP/1.0 DLNADOC/1.50 LogitechMediaServer/7.9.0/1453293926\r\nST: upnp:rootdevice\r\nUSN: uuid:31587DD1-0AAD-4594-9B21-A074D0318BC4::upnp:rootdevice\r\n\r\n"
[17-12-11 17:15:48.3408] Slim::Plugin::UPnP::MediaServer::description (99) MediaServer.xml requested by dLeyna/0.5.0 GUPnP/0.20.13 DLNADOC/1.50
[17-12-11 17:15:48.3528] Slim::Plugin::UPnP::Discovery::__ANON__ (497) Replying to 192.168.11.131:38583: "HTTP/1.1 200 OK\r\nCache-Control: max-age=1800\r\nDate: Mon, 11 Dec 2017 16:15:46 GMT\r\nExt: \r\nLocation: http://192.168.11.141:9002/plugins/U...xml\r\nServer: Linux/x86_64-linux UPnP/1.0 DLNADOC/1.50 LogitechMediaServer/7.9.0/1453293926\r\nST: upnp:rootdevice\r\nUSN: uuid:31587DD1-0AAD-4594-9B21-A074D0318BC4::upnp:rootdevice\r\n\r\n"
[17-12-11 17:15:48.3825] Slim::Plugin::UPnP::SOAPServer::processControl (136) Invoking Slim::Plugin::UPnP::MediaServer::ContentDirectory->GetSearchCapabilities( undef )
[17-12-11 17:15:48.5128] Slim::Plugin::UPnP::SOAPServer::processControl (136) Invoking Slim::Plugin::UPnP::MediaServer::ContentDirectory->GetSortCapabilities( undef )
[17-12-11 17:15:48.5397] Slim::Plugin::UPnP::SOAPServer::processControl (99) SOAPServer: Slim::Plugin::UPnP::MediaServer::ContentDirectory does not implement GetSortExtensionCapabilities
[17-12-11 17:15:48.5438] Slim::Plugin::UPnP::SOAPServer::fault (227) UPnP fault: 401 / Invalid Action
[17-12-11 17:15:48.5442] Slim::Plugin::UPnP::SOAPServer::fault (228) Result: <?xml version="1.0" encoding="UTF-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError><errorCode xsi:type="xsd:int">401</errorCode><errorDescription xsi:type="xsd:string">Invalid Action</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>
[17-12-11 17:15:48.5563] Slim::Plugin::UPnP::SOAPServer::processControl (99) SOAPServer: Slim::Plugin::UPnP::MediaServer::ContentDirectory does not implement GetFeatureList
[17-12-11 17:15:48.5605] Slim::Plugin::UPnP::SOAPServer::fault (227) UPnP fault: 401 / Invalid Action
[17-12-11 17:15:48.5608] Slim::Plugin::UPnP::SOAPServer::fault (228) Result: <?xml version="1.0" encoding="UTF-8"?><s:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError><errorCode xsi:type="xsd:int">401</errorCode><errorDescription xsi:type="xsd:string">Invalid Action</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>
[17-12-11 17:15:48.5706] Slim::Plugin::UPnP::Events::request (92) SUBSCRIBE /plugins/UPnP/MediaServer/ContentDirectory/eventsub
[17-12-11 17:15:48.5713] Slim::Plugin::UPnP::Events::subscribe (250) Subscribe: 3D5E38FD-A8F5-4A13-B55E-58FDFE412491 (Slim::Plugin::UPnP::MediaServer::ContentDirectory) (1800 sec) -> http://192.168.11.131:41218/ServiceProxy11
[17-12-11 17:15:48.5717] Slim::Plugin::UPnP::Events::sendNotify (383) Delaying notify for 3D5E38FD-A8F5-4A13-B55E-58FDFE412491, not yet active
[17-12-11 17:15:48.5724] Slim::Plugin::UPnP::Events::sendResponse (149) Sub 3D5E38FD-A8F5-4A13-B55E-58FDFE412491 is now active
[17-12-11 17:15:48.7723] Slim::Plugin::UPnP::Events::sendNotify (410) Notifying to 192.168.11.131:41218 for 0 / Slim::Plugin::UPnP::MediaServer::ContentDirectory
[17-12-11 17:15:48.7727] Slim::Plugin::UPnP::Events::sendNotify (411) NOTIFY /ServiceProxy11 HTTP/1.1
Host: 192.168.11.131:41218
Content-Type: text/xml; charset="utf-8"
Content-Length: 167
NT: upnp:event
NTS: upnp:propchange
SID: uuid:3D5E38FD-A8F5-4A13-B55E-58FDFE412491
SEQ: 0

<?xml version="1.0"?>
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
  <e:property><SystemUpdateID>1512983526</SystemUpdateID></e:property>
</e:propertyset>

This looks the same on both devices.
Exactly 30min later on the Synology I get the following messages after that the Mediaserver disappears from the list.

[17-12-11 17:43:59.7914] Slim::Plugin::UPnP::Events::request (92) SUBSCRIBE /plugins/UPnP/MediaServer/ContentDirectory/eventsub
[17-12-11 17:43:59.7919] Slim::Plugin::UPnP::Events::subscribe (190) Renewed: 3D5E38FD-A8F5-4A13-B55E-58FDFE412491 (1800 sec)
[17-12-11 17:43:59.7926] Slim::Plugin::UPnP::Events::sendResponse (149) Sub 3D5E38FD-A8F5-4A13-B55E-58FDFE412491 is now active
[17-12-11 17:45:50.7950] Slim::Plugin::UPnP::Events::request (92) UNSUBSCRIBE /plugins/UPnP/MediaServer/ContentDirectory/eventsub
[17-12-11 17:45:50.7955] Slim::Plugin::UPnP::Events::unsubscribe (302) Unsubscribe: 3D5E38FD-A8F5-4A13-B55E-58FDFE412491 (Slim::Plugin::UPnP::MediaServer::ContentDirectory)

On the MACmini however I don't see the unsubscribe only the Renewed messages:

[17-12-11 17:45:14.8075] Slim::Plugin::UPnP::Events::request (92) SUBSCRIBE /plugins/UPnP/MediaServer/ContentDirectory/eventsub
[17-12-11 17:45:14.8079] Slim::Plugin::UPnP::Events::subscribe (190) Renewed: E06B99D3-0CDC-43D8-A424-461E077BADB0 (1800 sec)
[17-12-11 17:45:14.8083] Slim::Plugin::UPnP::Events::sendResponse (149) Sub E06B99D3-0CDC-43D8-A424-461E077BADB0 is now active

This raises a few questions for me. It seems there is some kind of timeout running out. But why only on the NAS? Is the client actively unsubscribing from the NAS MediaServer? If so, why does he not also unsubscribe from the MACmini Mediaserver?

[pinkdot]

Doesn't seem like an Synology issue. Something is triggering upnp to unsubscribe. Question is what.

Do you have Media Server active on your nas? If so, switch of Media Server and see if that's interfering.

(I'm still willing to clean up a package for you, but I doubt it will fix the issue, just let me know).

Sent from my Redmi 3S using Tapatalk

[doncmdr]

Doesn't seem like an Synology issue. Something is triggering upnp to unsubscribe. Question is what.

Do you have Media Server active on your nas? If so, switch of Media Server and see if that's interfering.

(I'm still willing to clean up a package for you, but I doubt it will fix the issue, just let me know).

I tend to agree that it is not a Synology issue. After another day of testing, I observed the MediaServer on the MACmini disappear from the client list as well.
It took 21h instead of 30min on the other mediaserver. Again after a short disconnection of the Ethernet Cable both servers reappear immediately.
I don't have other servers running on the Synology (only SMB) that could interfear with the UPnP /DLNA server.

So it is probably not necessary to create another package for the Synology, but thanks again for offering.

Then I think it can be either an issue with the UPnP / DLNA media interface plugin or with the UPnP Client in the Pioneer Receiver.
I have no idea how to go from here.
I will try to send a bug report to pioneer as the AV Receiver manufacturer, but I doubt this will help with anything.
If there is a way to file a bug report against the UPnP / DLAN media interface and have someone investigate the issue? I am happy to help any way I can, but I am not a software developer. And don't know details of the UPnP Protocol.

[pinkdot]

It took 21h instead of 30min on the other mediaserver.

The 30 min. or 1800 sec is defined in the LMS code. So it looks like LMS can' t find your Pioneer after 1800 sec.

So it is probably not necessary to create another package for the Synology, but thanks again for offering.

Indeed I don't think this would fix the issue, but I already created the x86_64 package for someone else, so use it if you want to. Just make sure you follow the instructions here!

Update lms package: gdrive

If there is a way to file a bug report against the UPnP / DLAN media interface and have someone investigate the issue? I am happy to help any way I can, but I am not a software developer. And don't know details of the UPnP Protocol.

In LMS you have the option to take a log: