MinimServer Forum

Full Version: Synology DSM 6.1.1-15101
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi!

My Synology warns me that MinimServer is not compatible with the latest update. So i didn't dare to install the update. Anybody braver than me tried it out...?

Best wishes,

Müsli
I've updated my ds211j and it works.

After the reboot, I tried to start the minim server a few times and it failed (ds211j is very slow starting everything after a reboot). Received some messages of error, the last one different, saying something about java corrupt but when I has to ready to give up it started without any intervention.



(28-04-2017 10:51)muesli Wrote: [ -> ]Hi!

My Synology warns me that MinimServer is not compatible with the latest update. So i didn't dare to install the update. Anybody braver than me tried it out...?

Best wishes,

Müsli
This issue - meaningless warning about incompatibility and when starting the service *) - happened in the past several times, when new DSM Updates were published. Simon Nash did resolve that by contacting Synology. And as Elias pointed out: Starting the MinimServer service is no problem, it keeps running fine despite the error message.

*) see screenshots attached.[attachment=1361][attachment=1362]
The message about Java being corrupted after a DSM update has been fixed in MinimServer 0.8.4.2. If you have MinimSrever 0.8.4.2 installed before you do the DSM update, you should not get this message.
(28-04-2017 12:53)simoncn Wrote: [ -> ]The message about Java being corrupted after a DSM update has been fixed in MinimServer 0.8.4.2. If you have MinimSrever 0.8.4.2 installed before you do the DSM update, you should not get this message.
Dear Simon, I had version 0.8.4.2 installed prior to updating. I always install MinimServer and MinimWatch Updates as soon as they are published. So the issue is not fixed but nevertheless harmless. Thanks for great app and support.
(28-04-2017 14:14)goforit Wrote: [ -> ]
(28-04-2017 12:53)simoncn Wrote: [ -> ]The message about Java being corrupted after a DSM update has been fixed in MinimServer 0.8.4.2. If you have MinimSrever 0.8.4.2 installed before you do the DSM update, you should not get this message.
Dear Simon, I had version 0.8.4.2 installed prior to updating. I always install MinimServer and MinimWatch Updates as soon as they are published. So the issue is not fixed but nevertheless harmless. Thanks for great app and support.

I can confirm that this happens even with the latest version of MinimServer.

As an FYI, the DSM front-end handles the error differently depending on whether you run the full web version or the mobile version. In the later version it just cuts out with an error 63. In the full web version, it gives you the option to go forward or cancel. So, if you run DSM and MinimServer and you want to update to DSM 6.1.1 you must do this on the full web version.
Thanks for this information. It seems that there is a new issue with DSM 6.1.1 that did not happen with the previous version update.

I will try this myself soon. For those who have already tried it, does the message about Java occur once only or does it occur every time MinimServer is started?
Hi Simon,
I just updated to DSM 6.1.1-15101, and although I did receive the initial notification from DSM that the MinimServer package is not compatible, I went ahead and selected Continue with the update.
It took some time, however, I experienced no other error messages, and now both MinimWatch, the MinimServer Status web page, and the DSM Package Center indicates that MinimServer is running ..... and more importantly, I can select and play music from my NAS.
(I am still on a DS214se. Java version is 1.8.0_131. MinimServer is 0.8.4.2)
/Peter
(28-04-2017 15:08)simoncn Wrote: [ -> ]For those who have already tried it, does the message about Java occur once only or does it occur every time MinimServer is started?
Hi Simon, I stopped and started again the MinimServer: no message occurs. So this seems to happen only once after updating DSM. Running config:
MinimServer 0.8.4 update 99, Copyright © 2012-2017 Simon Nash. All rights reserved.
MinimStreamer 0.6.2, Copyright © 2012-2017 Simon Nash. All rights reserved.
Java™ SE Embedded Runtime Environment (build 1.8.0_121-b13)
Java HotSpot™ Embedded Client VM (build 25.121-b13, mixed mode)
Platform default charset is UTF-8
Language setting is 'ger'
Current time is Fri Apr 28 18:14:56 CEST 2017 in time zone Europe/Amsterdam
starting MinimServer
Here is the first part of my log file in case it makes any difference:

MinimServer 0.8.4 update 99, Copyright © 2012-2017 Simon Nash. All rights reserved.
MinimStreamer 0.6.2, Copyright © 2012-2017 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot™ Client VM (build 25.131-b11, mixed mode)
Platform default charset is UTF-8
Language setting is 'enu'
Current time is Fri Apr 28 16:38:04 IST 2017 in time zone Europe/Dublin
Pages: 1 2
Reference URL's