Minim not accessible

[simoncn]

(30-06-2016 15:21)SoundAdikt Wrote:  If I understand correctly, I had to install 0.8.3.4 when I upgraded to DSM 6 (when it became GA). The problem existed as soon as I did that, probably on the basis that DSM v6 GA came out (if I remember correctly) in March, by which time Update 76 had become available. I'm pretty sure that as part of the installation I would have upgraded the packages at the same time thus I would never have tried 0.8.3.4 with update 75 or lower.

Yes, this makes sense.

Quote:Given MinimServer is not working correctly, I would be happy to remove it (including config files) and install 0.8.3.4 if you would be able to send me a link to download the spk file. I could then try it without upgrading any of the packages to see what happens.

Thanks.

I appreciate this offer but I feel that reverting to 0.8.3.4 would be a step backward that might cause other problems and is unlikely to get us any closer to fixing the problem. I would prefer to put my efforts into debugging and fixing the current ohNet code.

[SoundAdikt]

No problem! But reach out if I can provide any assistance.

[Kochmeister]

Hi Simon,

The minim server had been up for about 3 weeks now. When logging into my router I found that the router had been "up" for the same time.
I noticed that there was a firmware update for the router, so it rebooted. After that the minim server was "gone" in my UPNP apps and minim watch on my laptop.

I gathered the data you requested in post-13, see attachment.
My hardware:

- ASUS RT-AC68U - Firmware Version:3.0.0.4.380_3831
- Synology DS 212 - DSM 6.0.1-7393 Update 1

Not sure if it is of any use but attached the router log file as well.
Not sure what the aug 1 loggings are, seems reboot or something like that.

hope you can advice!

Marc

[Lex]

(13-06-2016 11:20)Kochmeister Wrote:  Hi Minim Support,

Lately (I think since DSM-6) minim is not visible anymore in the tream-app.
I use a synology 212+. on latest DSM 6 and minim 0.8.4
Minim starts fine, and is accessible for some time and after that it is not anymore. I can not link it to any actions on the NAS.
Minim watch on the laptop can not reach Minim and is grey.
In the Syno package center it reports status "running".

When I stop the minim server to restart it it reports:

Quote:MinimServer had to be stopped using a forced kill. Please contact MinimServer support if this happens repeatedly.

Can you please advice me how to fix this?

Thanks.

I have had a similar (actually quite similar) problem with my ds213j the last week. In my case I was able to solve it by deinstalling bubbleupnp server.

Incidentally, there is a dsm update this morning which deals with a upnp vulnerability.

[Kochmeister]

Okay, did some troubleshooting and DSM update:

- Synology DS 212 - DSM 6.0.1-7393 Update 1
has minimserver
bubbleupnp

- router reboot (repro-check)
Minim "gone"

- update synology
DSM 6.0.1-7393 Update 2
Applied the workaround to mitigate a security vulnerability of libupnp module (CVE-2016-6255).

- minim running after stop
MinimServer had to be stopped using a forced kill.....
Minim Start
Wait for minim to complete the scan

- Reboot router
Minim "gone"

- Stop minim
MinimServer had to be stopped using a forced kill.....

- Stop BubbleUPNP on NAS

- Start minim
Wait for minim to complete the scan

- reboot router
Minim "gone"

- Restart minim (forcekill)

- uninstall bubbleUpNp
Backed up config

- Reboot router
Minim "Gone"

My conclusion in my case:
- Not related to DSM update-2
- not related to bubbleUpNp

[SoundAdikt]

From what I could see there appears to be a bug in the current ohNet stack used by MinimServer. It's on Simon's "to do" list after with his help, I managed to send him the info he needed...

Fingers crossed!

[simoncn]

Thanks for this additional information. I am investigating how best to fix this problem. The fix is not simple.

I have just returned home from some time away and I will continue my investigations. When I have any news, I will post it here.