Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Synology DSM 6.1.1-15101
28-04-2017, 20:51
Post: #11
RE: Synology DSM 6.1.1-15101
Thanks for all your helpful replies! Smile
Find all posts by this user
Quote this message in a reply
29-04-2017, 22:25 (This post was last modified: 29-04-2017 22:26 by simoncn.)
Post: #12
RE: Synology DSM 6.1.1-15101
I tried updating from DSM 6.1 to DSM 6.1.1 on a DS115 with MinimServer 0.8.4.2 installed and running. I ignored the message saying that MinimServer is not compatible and would be disabled by the update. The update completed successfully and MinimServer was running after the update with no message about Java being corrupted.
Find all posts by this user
Quote this message in a reply
30-04-2017, 03:01
Post: #13
RE: Synology DSM 6.1.1-15101
Updated to DSM 6.1.1-15101, no problem found despite the MinimServer non-compatible warning
using:
Synology DS214play
Java 8.0.121-0013b
MinimServer 0.8.4 update 99
MinimStreamer 0.6.2
Find all posts by this user
Quote this message in a reply
30-04-2017, 09:49
Post: #14
RE: Synology DSM 6.1.1-15101
After the 6.1.1. update on my DS214+, everything seemed to be fine, then yesterday for the first time ever, I had Minimserver crash on a re-scan. I stopped Minimserver via Minimwatch, and was able to re-start. Today my brother tells me that Minimserver has crashed during a re-scan on his DS416play after updating to 6.1.1.

So something has happened with 6.1.1 ?
Find all posts by this user
Quote this message in a reply
30-04-2017, 11:00
Post: #15
RE: Synology DSM 6.1.1-15101
After your helpful comments I also installed the update without any problems on my DS 213J. No problems with re-scan as well.
Find all posts by this user
Quote this message in a reply
30-04-2017, 12:57
Post: #16
RE: Synology DSM 6.1.1-15101
Triggered by ac16161's post, I just tried a rescan. No problems at my end. MinimServer started without error messages.
/Peter
Find all posts by this user
Quote this message in a reply
30-04-2017, 14:28
Post: #17
RE: Synology DSM 6.1.1-15101
(30-04-2017 09:49)ac16161 Wrote:  After the 6.1.1. update on my DS214+, everything seemed to be fine, then yesterday for the first time ever, I had Minimserver crash on a re-scan. I stopped Minimserver via Minimwatch, and was able to re-start. Today my brother tells me that Minimserver has crashed during a re-scan on his DS416play after updating to 6.1.1.

So something has happened with 6.1.1 ?

What do you mean by "crashed"? For example, is there a red icon in MinimWatch and a Java exception in the MinimServer log? Or has MinimServer just stopped and disappeared from MinimWatch?
Find all posts by this user
Quote this message in a reply
30-04-2017, 17:24
Post: #18
RE: Synology DSM 6.1.1-15101
(30-04-2017 14:28)simoncn Wrote:  
(30-04-2017 09:49)ac16161 Wrote:  After the 6.1.1. update on my DS214+, everything seemed to be fine, then yesterday for the first time ever, I had Minimserver crash on a re-scan. I stopped Minimserver via Minimwatch, and was able to re-start. Today my brother tells me that Minimserver has crashed during a re-scan on his DS416play after updating to 6.1.1.

So something has happened with 6.1.1 ?

What do you mean by "crashed"? For example, is there a red icon in MinimWatch and a Java exception in the MinimServer log? Or has MinimServer just stopped and disappeared from MinimWatch?

I'd just added a few tracks and the re-scan hanged for ages, with no sign of Minimserver in my control point. It was not the first rescan after 6.1.1. Bit of a coincidence that my brothr had his first ever stalled rescan not long after installing 6.1.1.
Find all posts by this user
Quote this message in a reply
30-04-2017, 21:48
Post: #19
RE: Synology DSM 6.1.1-15101
(30-04-2017 17:24)ac16161 Wrote:  I'd just added a few tracks and the re-scan hanged for ages, with no sign of Minimserver in my control point. It was not the first rescan after 6.1.1. Bit of a coincidence that my brothr had his first ever stalled rescan not long after installing 6.1.1.

It is normal for MinimServer to disappear from the control point during a rescan. If the rescan completed after a delay, this means that MinimServer did not crash. In this case, the probable cause would be some background DSM activity consuming a lot of system resources and interfering with the MinimServer rescan.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)