Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Guidance for upgrading to Synology DSM 6.0
31-03-2016, 15:50
Post: #1
Guidance for upgrading to Synology DSM 6.0
I have written some guidance notes to help with upgrading a Synology NAS to DSM 6.0 and you can find them at the top of this page. If there any problems or questions regarding this upgrade process, please post them here.
Find all posts by this user
Quote this message in a reply
05-04-2016, 11:59
Post: #2
RE: Guidance for upgrading to Synology DSM 6.0
Hello, ever since upgrading to DSM 6, I'm having difficulties getting MinimServer to reliably work on my DS213j. This is what I have done:

- Uninstalled Java 7
- Uninstalled MinimServer leaving the configuration files in tact (I know this isn't necessary)
- Installed Java 8, upgraded to Oracle Java 8
- Downloaded the ARM7 MinimServer pkg file and installed (version MinimServer 0.8.3.4 reported in DSM, on port 9790 it says MinimServer 0.8.3 update 78, ie. no mention of 0.8.3.4)

What I am observing is:
- MinimServer works correctly upon starting the package
- After a while, MinimServer is no longer discoverable through any control point and MinimWatch
- MinimServer is shown as running on port 9790
- If I stop or restart MinimServer from DSM, I get a DSM system log warning stating MinimServer had to be stopped using a forced kill
- Upon restart, MinimServer is discoverable and functions normally but then is no longer discoverable after a period of time - usually an hour or so
- I'm also running Synology Media Server for photos and video (not audio) and this continues to be discoverable, so this implies it's not a network issue
- I have rebooted the NAS

Any suggestions would be most welcome.

Many thanks, SoundAdikt.
Find all posts by this user
Quote this message in a reply
05-04-2016, 14:02
Post: #3
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 11:59)SoundAdikt Wrote:  Hello, ever since upgrading to DSM 6, I'm having difficulties getting MinimServer to reliably work on my DS213j. This is what I have done:

- Uninstalled Java 7
- Uninstalled MinimServer leaving the configuration files in tact (I know this isn't necessary)
- Installed Java 8, upgraded to Oracle Java 8
- Downloaded the ARM7 MinimServer pkg file and installed (version MinimServer 0.8.3.4 reported in DSM, on port 9790 it says MinimServer 0.8.3 update 78, ie. no mention of 0.8.3.4)

What I am observing is:
- MinimServer works correctly upon starting the package
- After a while, MinimServer is no longer discoverable through any control point and MinimWatch
- MinimServer is shown as running on port 9790
- If I stop or restart MinimServer from DSM, I get a DSM system log warning stating MinimServer had to be stopped using a forced kill
- Upon restart, MinimServer is discoverable and functions normally but then is no longer discoverable after a period of time - usually an hour or so
- I'm also running Synology Media Server for photos and video (not audio) and this continues to be discoverable, so this implies it's not a network issue
- I have rebooted the NAS

Any suggestions would be most welcome.

Many thanks, SoundAdikt.

The procedure that you followed to upgrade looks fine.

It sounds like MinimServer is crashing. After MinimServer becomes undiscoverable, use File Station to access the MinimServer/appData folder and copy the contents of the minimserver.log and minimserver-out.log files to a post here. You need to do this before you stop and restart MinimServer from the Package Center because the restart will overwrite the contents of these files. Please also check whether the appData folder contains any files whose names start with hs_err_pid. Many thanks!
Find all posts by this user
Quote this message in a reply
05-04-2016, 14:14
Post: #4
RE: Guidance for upgrading to Synology DSM 6.0
Hi,
I just wanted to upgrade MS to 0.8.3.4 but while uploading much needed package (for DS713+ MinimServer-0.8.3.4-x64.spk) but the following notice appears "This package does not contain a digital signature".
Hence, whole upgrade process itself is aborted.
Is there any help how to proceed?
Thank you.
Find all posts by this user
Quote this message in a reply
05-04-2016, 14:50
Post: #5
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 14:14)Thutmo Wrote:  Hi,
I just wanted to upgrade MS to 0.8.3.4 but while uploading much needed package (for DS713+ MinimServer-0.8.3.4-x64.spk) but the following notice appears "This package does not contain a digital signature".
Hence, whole upgrade process itself is aborted.
Is there any help how to proceed?
Thank you.

There are detailed instructions on this page. See step 3 of this section.
Find all posts by this user
Quote this message in a reply
05-04-2016, 17:24
Post: #6
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 14:02)simoncn Wrote:  The procedure that you followed to upgrade looks fine.

It sounds like MinimServer is crashing. After MinimServer becomes undiscoverable, use File Station to access the MinimServer/appData folder and copy the contents of the minimserver.log and minimserver-out.log files to a post here. You need to do this before you stop and restart MinimServer from the Package Center because the restart will overwrite the contents of these files. Please also check whether the appData folder contains any files whose names start with hs_err_pid. Many thanks!

Files as requested - these errors are no different to what the previous version of MinimServer reported (no hs_err_pid files by the way):

minimserver.log:

MinimServer 0.8.3 update 78, Copyright © 2012-2016 Simon Nash. All rights reserved.
MinimStreamer 0.5.23, Copyright © 2012-2016 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot™ Client VM (build 25.77-b03, mixed mode)
Platform default charset is UTF-8
Using single subnet 192.168.1.0
Language setting is 'enu'
Current time is Tue Apr 05 12:01:24 IST 2016 in time zone Europe/Dublin
starting Music Server
Error: couldn't access file /volume1/music/albums/Jorge Reyes/The Flayed God/07 Jorge Reyes - �%81rbol Sagrado.flac
Warning: conflicting ALBUMARTIST values ignored for album Two Against Nature
first conflicting value: 01 Steely Dan
first conflicting item: Gaslighting Abbie
second conflicting value: 02 Steely Dan
second conflicting item: What a Shame About Me
Error: couldn't access file /volume1/music/albums/Yann Tiersen/Amélie/04 Yann Tiersen - Comptine d'un Autre �%89té.flac
Error: couldn't access file /volume1/music/albums/Yann Tiersen/Amélie/14 Yann Tiersen - Si Tu N'�%89tais Pas Là.flac
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 216 in file Lloyd Cole/Dont Get Weird On Me Babe/01 Butterfly.mp3 (length 7416964)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 220 in file Lloyd Cole/Dont Get Weird On Me Babe/02 There For Her.mp3 (length 9806649)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 215 in file Lloyd Cole/Dont Get Weird On Me Babe/03 Margos Waltz.mp3 (length 9741861)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 225 in file Lloyd Cole/Dont Get Weird On Me Babe/04 Half Of Everything.mp3 (length 17002867)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 217 in file Lloyd Cole/Dont Get Weird On Me Babe/05 Man Enough.mp3 (length 9732459)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 227 in file Lloyd Cole/Dont Get Weird On Me Babe/06 What He Doesnt Know.mp3 (length 9789938)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 223 in file Lloyd Cole/Dont Get Weird On Me Babe/07 Tell Your Sister.mp3 (length 8500530)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 219 in file Lloyd Cole/Dont Get Weird On Me Babe/08 Weeping Wine.mp3 (length 6336542)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 219 in file Lloyd Cole/Dont Get Weird On Me Babe/09 To The Lions.mp3 (length 6438942)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 218 in file Lloyd Cole/Dont Get Weird On Me Babe/10 Pay For It.mp3 (length 15238027)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 229 in file Lloyd Cole/Dont Get Weird On Me Babe/11 The One You Never Had.mp3 (length 6037712)
Error: ID3v2.4 'PRIV' frame size has incorrect format at offset 234 in file Lloyd Cole/Dont Get Weird On Me Babe/12 Shes A Girl And Im A Man.mp3 (length 10239251)
Warning: conflicting ALBUMARTIST values ignored for album Amores Perros
on disc 1
first conflicting value: Various
first conflicting item: Gustavo Santaolalla/Tema Amores Perros
second conflicting value: Amores Perros
second conflicting item: Me Van A Matar
Error: couldn't access file /volume1/music/compilations/Various/Common Ground; Voices Of Modern Irish Music/12 Liam �%93 Maonlaí - Cathain.flac
Warning: conflicting ALBUMARTIST values ignored for album Dali Stereo Demonstration CD
on disc 1
first conflicting value: Various
first conflicting item: Henry Mancini/Pink Panther
second conflicting value: Dadawa
second conflicting item: Dadawa/Canton Story
Error: couldn't access file /volume1/music/compilations/Various/It's Only Rock N Roll, Disc 2/05 Blue �%96yster Cult - (Don't Fear) The Reaper.flac
Error: couldn't access file /volume1/music/compilations/Various/Perfect Day/01 Various Artists - Perfect Day �%80%9997.flac
Error: couldn't access file /volume1/music/compilations/Various/Perfect Day/02 Various Artists - Perfect Day �%80%9997 (male version).flac
Error: couldn't access file /volume1/music/compilations/Various/The Best... Album in the World... Ever! Volume 3, Disc 1/17 Teenage Fanclub - Sparky�%80%99s Dream.flac
Warning: conflicting ALBUMARTIST values ignored for album Darren's mix
on disc 1
first conflicting value: John Farnham
first conflicting item: Pressure Down
second conflicting value: LOU GRAMM
second conflicting item: Midnight Blue (LP Version)
Music Server is running




minimserver-out.log:

MinimServer 0.8.3 update 78, Copyright © 2012-2016 Simon Nash. All rights reserved.
MinimStreamer 0.5.23, Copyright © 2012-2016 Simon Nash. All rights reserved.
starting Music Server
Enter command (? for help):
>Music Server is running
>


Thank you.
Find all posts by this user
Quote this message in a reply
05-04-2016, 20:40
Post: #7
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 14:50)simoncn Wrote:  
(05-04-2016 14:14)Thutmo Wrote:  Hi,
I just wanted to upgrade MS to 0.8.3.4 but while uploading much needed package (for DS713+ MinimServer-0.8.3.4-x64.spk) but the following notice appears "This package does not contain a digital signature".
Hence, whole upgrade process itself is aborted.
Is there any help how to proceed?
Thank you.

There are detailed instructions on this page. See step 3 of this section.

Thank you,
problem solved - my DS Package Center Trust Level was not set to 'Any publisher'; that was my mistakeWink
Find all posts by this user
Quote this message in a reply
05-04-2016, 22:22
Post: #8
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 17:24)SoundAdikt Wrote:  Files as requested - these errors are no different to what the previous version of MinimServer reported (no hs_err_pid files by the way):

Thanks for this. It shows that MinimServer has not crashed, which (I think) must mean that MinimServer is hung.

To confirm this and get diagnostic information about the problem, please wait for MinimServer to become unresponsive and then do the following before restarting MinimServer:

1) Log into the NAS using SSH
2) Enter the command: cat /var/run/minimserver.pid and note the number in the response to this command
3) Enter the command: sudo kill -quit nnnn
where nnnn is the number that you got from step 2
4) Enter your admin password when prompted
5) The minimserver-out.log file should now contain diagnostic information starting with "Full thread dump Java"
6) Download the minimserver-out.log file to a computer and attach it as a file attachment (not inline) to a post here

Many thanks!
Find all posts by this user
Quote this message in a reply
05-04-2016, 23:37
Post: #9
RE: Guidance for upgrading to Synology DSM 6.0
Thank you for your help Simon.

>>>

MinimServer 0.8.3 update 78, Copyright © 2012-2016 Simon Nash. All rights reserved.
MinimStreamer 0.5.23, Copyright © 2012-2016 Simon Nash. All rights reserved.
starting Music Server
Enter command (? for help):
>Music Server is running
>2016-04-05 23:33:04
Full thread dump Java HotSpot™ Client VM (25.77-b03 mixed mode):

"Thread-25" #33 daemon prio=5 os_prio=0 tid=0x4c036778 nid=0x39a1 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-23" #31 daemon prio=5 os_prio=0 tid=0x4b51cd60 nid=0x39a2 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-22" #30 daemon prio=5 os_prio=0 tid=0x4c0880a0 nid=0x39a0 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Timer-0" #29 prio=5 os_prio=0 tid=0x4c034bd0 nid=0x3a86 in Object.wait() [0x4cea0000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x43221608> (a java.util.TaskQueue)
at java.lang.Object.wait(Object.java:502)
at java.util.TimerThread.mainLoop(Timer.java:526)
- locked <0x43221608> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:505)

"Thread-20" #28 daemon prio=5 os_prio=0 tid=0x4c090058 nid=0x39aa runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-19" #27 daemon prio=5 os_prio=0 tid=0x4b5169a0 nid=0x39a9 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-18" #26 prio=5 os_prio=0 tid=0x4cb9a948 nid=0x39de in Object.wait() [0x4cd8a000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45c04508> (a org.jminim.launch.Launcher$ConsoleRequest)
at java.lang.Object.wait(Object.java:502)
at org.jminim.launch.Launcher$ConsoleRequest.awaitCompletion(Launcher.java:1392)
- locked <0x45c04508> (a org.jminim.launch.Launcher$ConsoleRequest)
at org.jminim.launch.Launcher$ConsoleReader.readLine(Launcher.java:1267)
- locked <0x45b2f178> (a org.jminim.launch.Launcher$ConsoleReader)
at com.minimserver.lib.ServerConsole$ServerConsoleThread.run(ServerConsole.java:968​)

"Thread-17" #25 daemon prio=5 os_prio=0 tid=0x4c08a3a8 nid=0x39a8 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-12" #19 daemon prio=5 os_prio=0 tid=0x000aa798 nid=0x39a7 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"Thread-7" #14 prio=5 os_prio=0 tid=0x4bbe2f30 nid=0x39c4 runnable [0x4c870000]
java.lang.Thread.State: RUNNABLE
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)
at java.net.ServerSocket.implAccept(ServerSocket.java:545)
at java.net.ServerSocket.accept(ServerSocket.java:513)
at org.jminim.lib.HTTPService.runServerThread(HTTPService.java:332)
at org.jminim.lib.HTTPService.access$200(HTTPService.java:30)
at org.jminim.lib.HTTPService$1.run(HTTPService.java:317)

"Thread-6" #13 prio=5 os_prio=0 tid=0x4bbe1d78 nid=0x39c3 in Object.wait() [0x4c68e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45bc1c70> (a org.jminim.lib.HTTPService$SocketThread)
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:387)
- locked <0x45bc1c70> (a org.jminim.lib.HTTPService$SocketThread)

"Thread-5" #12 prio=5 os_prio=0 tid=0x4c169168 nid=0x3999 in Object.wait() [0x4c34e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45bad240> (a org.jminim.lib.OhNetService$TimerThread)
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:860)
- locked <0x45bad240> (a org.jminim.lib.OhNetService$TimerThread)

"Thread-4" #11 prio=5 os_prio=0 tid=0x4c168270 nid=0x3998 in Object.wait() [0x4bf38000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45bad3c0> (a org.jminim.lib.OhNetService$ActionThread)
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:815)
- locked <0x45bad3c0> (a org.jminim.lib.OhNetService$ActionThread)

"Thread-2" #9 prio=5 os_prio=0 tid=0x4bba3f50 nid=0x398d in Object.wait() [0x4bfcd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45b64c18> (a org.jminim.core.RuntimeImpl$TimerThread)
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:2751)
- locked <0x45b64c18> (a org.jminim.core.RuntimeImpl$TimerThread)

"Thread-1" #8 prio=5 os_prio=0 tid=0x4bba4930 nid=0x398c in Object.wait() [0x4be9e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45b64d98> (a org.jminim.core.RuntimeImpl$ActionThread)
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:2705)
- locked <0x45b64d98> (a org.jminim.core.RuntimeImpl$ActionThread)

"Thread-0" #7 daemon prio=5 os_prio=0 tid=0x4bb20038 nid=0x3985 runnable [0x4bd4e000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.FileDispatcherImpl.read(FileDispatcherImpl.java:46)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:197)
at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:159)
- locked <0x45c04728> (a java.lang.Object)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103)
- locked <0x45c04768> (a sun.nio.ch.ChannelInputStream)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
- locked <0x45c0a7f8> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:161)
at java.io.BufferedReader.readLine(BufferedReader.java:324)
- locked <0x45c0a7f8> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:389)
at org.jminim.launch.Launcher$ConsoleThread.run(Launcher.java:1352)

"Service Thread" #6 daemon prio=9 os_prio=0 tid=0x40d81b18 nid=0x3980 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE

"C1 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x40d7eac8 nid=0x397f waiting on condition [0x00000000]
java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x40d7d620 nid=0x397e waiting on condition [0x00000000]
java.lang.Thread.State: RUNNABLE

"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x40d632b8 nid=0x397b in Object.wait() [0x4b64e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45a7fb38> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
- locked <0x45a7fb38> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

"Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x40d60900 nid=0x397a in Object.wait() [0x4b4f2000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45a7fcd8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:502)
at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
- locked <0x45a7fcd8> (a java.lang.ref.Reference$Lock)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"main" #1 prio=5 os_prio=0 tid=0x40d05870 nid=0x3978 in Object.wait() [0x40142000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x45b689b8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:2622)
- locked <0x45b689b8> (a java.lang.Object)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1392)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1106)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav​a:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jminim.launch.Launcher.doLaunch(Launcher.java:621)
at org.jminim.launch.Launcher.launch(Launcher.java:204)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:30)

"VM Thread" os_prio=0 tid=0x40d5c4a0 nid=0x3979 runnable

"VM Periodic Task Thread" os_prio=0 tid=0x40d83718 nid=0x3981 waiting on condition

JNI global references: 293

Heap
def new generation total 2432K, used 1778K [0x43000000, 0x432a0000, 0x45a00000)
eden space 2176K, 69% used [0x43000000, 0x4317c918, 0x43220000)
from space 256K, 100% used [0x43220000, 0x43260000, 0x43260000)
to space 256K, 0% used [0x43260000, 0x43260000, 0x432a0000)
tenured generation total 5504K, used 5085K [0x45a00000, 0x45f60000, 0x4ae00000)
the space 5504K, 92% used [0x45a00000, 0x45ef7680, 0x45ef7800, 0x45f60000)
Metaspace used 7465K, capacity 7735K, committed 7832K, reserved 8496K
Find all posts by this user
Quote this message in a reply
06-04-2016, 08:15
Post: #10
RE: Guidance for upgrading to Synology DSM 6.0
(05-04-2016 23:37)SoundAdikt Wrote:  Thank you for your help Simon.

This doesn't look healthy. It seems there has been some problem with the ohNet stack used by MinimServer and ohNet has crashed without producing an error message.

To find out why ohNet has crashed, I will need to see a full ohNet debug log . I will PM you the instructions for producing this.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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