Cannot see Minimserver anymore for UPNP/DLNA

[gbrist]

I have a Synology DS218+ and have been using Licenced Minimserver for a while with no problems.
Recently I updated the NAS to DSM 7.1.1-42962 Update 7 as well as version 257 of Minimserver.
I can however use DBPoweramps Asset with no problems but I usually have this stopped and prefer to use Minimserver. So it would be good to find out whats gone wrong please.
Now on either my Samsung Phone or Tablet I cannot see Minimerver presented as a UPNP/DLNA presence and is continually rescanning just like port 9790
I have not installed MinimStreamer.
Pretty simple profile.
I also use a docker version port 9792 that I used for a LAME version when I'm out and about with OpenVPN that no longer presents as a UPNP/DLNA presence

Seems to be rescanning forever (ie all night)


MinimServer 2.2 update 257, Copyright © 2012-2025 Simon Nash. All rights reserved.

Your license type is Full. For more information, select the License tab.

Media server status for MinimServer[DS218]: Rescanning

Your last rescan was at 11:26:23 on 07 Feb 2025

You have selected the following content directory:

/volume1/music/FLAC-L5



Just as an aside..
150000 music tracks.
I can however use DBPoweramps Asset on the same DS218+ with no problems but I usually have this stopped and prefer to use Minimserver. So it would be good to find out whats gone wrong please.
I also can play using my music player from other 3 remote Synology NAS's using Openvpn with MInimerserver..difference is they have not been upgraded... just this one.
Hopefully it is simple and you can help me?
Thanks.

[simoncn]

If you use Synology File Station to look at the minimserver.log file in the MinimServer/appData shared folder, do you see the same directory or group of directories being scanned repeatedly? If so, please post details.

[gbrist]

(08-02-2025 00:34)simoncn Wrote:  If you use Synology File Station to look at the minimserver.log file in the MinimServer/appData shared folder, do you see the same directory or group of directories being scanned repeatedly? If so, please post details.

Thanks. Attached is what is in that log file.

[simoncn]

Thanks for posting this log. The messages look normal but there is no message saying that the scan has finished.

Please do the following:

1) From the MinimServer configuration web page, open the Properties tab and then open the System subtab
2) Set the .logLevel property to verbose
3) Stop and restart MinimServer from Synology Package Center
4) MinimServer should start scanning your library. Allow this scan to run for 20 minutes.
5) The minimserver.log file should be quite large. In Synology File Station, compress this file and attach the compressed file to a post here.
6) Please also attach the minimserver.config file (in the same appData folder)

[gbrist]

After more than 24hrs MinimServer completed the rescanning and on waking up this morning it appears to be back functioning normally.
Have restarted the NAS a few times and the UPNP/DLNA presence appears after 20mins or so.
So I guess that it is functional.
Sorry to have troubled you and thanks for your support.
A bit perplexing though as to why but given I updated both the NAS and Minimserver in the same time frame.
Next time I'll be upgrading separately.
Hopefully no more issues.
Thanks again

[simoncn]

Taking 20 minutes to show up on UPnP/DLNA isn't normal. MinimServer should show up in 30 seconds or less.

This long delay is usually caused by a problem with multicast discovery on your network. There is information about this on this page. If your router has a setting for IGMP snooping (not IGMP proxy), try disabling this if you can.

Also, 24 hours for a rescan is far too long. The first rescan takes longer but it shouldn't take more than 30 minutes or so. Subsequent rescans are faster (perhaps 2 or 3 minutes) because they use the MinimServer cache. Is your music library on an HDD inside the NAS or are you accessing it in some other way?

[gbrist]

(08-02-2025 21:50)simoncn Wrote:  Taking 20 minutes to show up on UPnP/DLNA isn't normal. MinimServer should show up in 30 seconds or less.

This long delay is usually caused by a problem with multicast discovery on your network. There is information about this on this page. If your router has a setting for IGMP snooping (not IGMP proxy), try disabling this if you can.

Also, 24 hours for a rescan is far too long. The first rescan takes longer but it shouldn't take more than 30 minutes or so. Subsequent rescans are faster (perhaps 2 or 3 minutes) because they use the MinimServer cache. Is your music library on an HDD inside the NAS or are you accessing it in some other way?

Music is on an 8TB Iron Wolf within the NAS. Only a single drive.
No IGMP snooping. Router is a simple Telco router. Same router / config for 3 or 4 years.
The UPNP/DLNA has never taken less than 20mins or so. Asset on the other hand is much quicker.
Just found this on the Synology Forum
https://community.synology.com/enu/forum...ply=522408
One thing I have just noticed is that I do not seem to be able to select "stop" for Asset (as I usually just use Minimserver) nor if I wanted to "stop" Minimserver either via the Package Server drop down the option is there but it does nothing..that's a bit weird.
Wonder if there could be a Synology issue...have added a comment to this Synology forum post..not too confident that they will be a responsive as you have been
By the way.. playing music from the NAS seems to be playing normally...which is good.

[simoncn]

I see that the difference in discovery times between Asset and MinimServer has been discussed previously on this thread. The delay with MinimServer is caused by something on your network (most likely the router) blocking M-SEARCH messages (see this post).

This doesn't explain why a rescan is taking such a long time. Do you see this for all rescans? The first scan is slower because MinimServer has to read data from every file in your library but rescans after this should be much quicker.

[gbrist]

(09-02-2025 16:38)simoncn Wrote:  I see that the difference in discovery times between Asset and MinimServer has been discussed previously on this thread. The delay with MinimServer is caused by something on your network (most likely the router) blocking M-SEARCH messages (see this post).

This doesn't explain why a rescan is taking such a long time. Do you see this for all rescans? The first scan is slower because MinimServer has to read data from every file in your library but rescans after this should be much quicker.

Just to let you know..
Synology got me to manually update the NAS with DSM 7.2.1 - 69057 for the DS218+ that they gave me a link to.. and this seems have solved the issue.
No other explanation from them as to why this release was not presented as an upgrade in the control panel upgrade/restore because it was this upgrade that was there that caused this issue in the first place IMO.
Also I can't do much to make changes to the Telco router.. its a pretty simple network I have mainly using cabled Gig Ethernet around my home with about 6 devices (tv's, PC etc) plus a couple of wifi devices (phone..tablet etc).
Nothing too fancy.
So I guess that I will just have to put up with a slightly longer rescan.
Sorry to have troubled you and thanks for your help.
Cheers
Steve

[streamer99]

I seem to be having a similar problem to the OP. I have used minim server on a Synology DS1819+ for several years. The current DSM version is 7.2.2-72806 update 3.
It has always been a rather hit and miss situation as to whether minimserver would be visible to the ios control point, in my case usually mconnect on ios 18.3.1
More than once I have considered giving up minim server because of this - I usually have to manually request a rescan before I can make any streaming selection, sometimes 2 or 3 times.
Probably since the latest update of DSM a few days ago, performance has been the worst I have experienced with contact lost in a few minutes so one must rescan again before anything can be seen.
As I understand it, there are no minim server settings the user can appropriately adjust to help. My router and WAP have IGM snooping off.