Threaded Mode | Linear Mode

simoncn · 17-01-2015, 13:18

(17-01-2015 12:48)DLNABubble Wrote: Hi Simon et all,

I'm currently evaluating if I should replace my miniDLNA instance running on a Synology NAS (409slim) replace by a MiminServer. The Java packages I discovered the other week, provided by patters (from Serviio ) finally enabled me to install MinimServer. Whilst Serviio rendered my DS (128MB, Marvell 88F6281 - 1,2 GHz) quite unusable, MinimServer is doing fine. Even the harddiscs spin down which they didn't whilst miniDLNA was running. Combined with the auto resart package, new recordings are picked up as well automatically. More or less the same way as I was used to whilst running miniDLNA. So far I'm very pleased! I do have a few thoughts but will address these in a different post.

I'm pleased to hear about these positive points for MinimServer.

Quote:After reading the elaborate install guide etc, I still have a problem understanding in how to enable the debug logging of MinimWatch. What exactly do I have to put into data/minimwatch.config?

Directly editing minimserver.config is not supported or recommended. This is why it isn't mentioned in the install guide or user guide. Also, this wouldn't help because you have confirmed that MinimServer is running correctly and can be seen by UPnP control points.

Quote:Why I want to do that?

Whilst BubbleUPNP on various devices, as well as a Hama DIR 3100 can see MinimServer and render music provided by it, MInimWatch can't find the server's instance at the same time.

I can access the MinimServer's serice url (http://<disc-station-ip>:9790/ ) from the Laptop MinimWatch is running on (no matter if connected directly via LAN or WLAN).

MinimWatch is running fine and the icon (grey coloured) is showing up in the KDE's task bar.

So any hints on how to resolve this issue are welcome. Thanks in adavance!

It sounds like the laptop you are using to run MinimWatch is unable to receive incoming multicast messages from MinimServer. To confiirm/investigate this, I suggest the following as initial steps:

1) Run a UPnP control point such as upplay (see this page) on the same laptop and see whether it discovers MinimServer. If not, this confirms there is a multicast problem.

2) In MinimWatch, change the ohnet.debug property to All-Timer and change the logging level to Debug, then select Refresh from the grey minim icon. After waiting 20 seconds, stop and restart MinimServer. After waiting 60 seconds, copy the minimwatch.log file from the minimwatch/data directory before it gets overwritten. Zip the minimwatch.log file and attach it to a post here and I will take a look at it.