Post Reply 
MinimServer stopped on Synology NAS
20-05-2019, 17:56
Post: #1
MinimServer stopped on Synology NAS
Hi

I have a Synology DS115j NAS drive with minim server running on it, this ha been working well for over two years, I now have started having a recurring problem which may have started after some updates to the Synology (I did not instigate these).

When I go to my streamer first time on a day it does not see MinimServer, I then go to the Synology and find that minim server has stopped. It restarts ok and everything runs normally. I can stop using the system and later come back to it and all works fine. Then the following day I go to the system and find MinimServer has again stopped.

The NAS drive does an automatic back up at 3.00am in the morning and this is the only thing I am aware of happening overnight which is when MinimServer appears to stop running.

Current version of MinimServer: 08.5.3 (update 128)

NAS drive Synology DS115j, backed up using hyper vault to a DS216j
DSM Version: DSM 6.2.2-24922
Find all posts by this user
Quote this message in a reply
20-05-2019, 20:39
Post: #2
RE: MinimServer stopped on Synology NAS
When you login to the NAS in the morning and MinimServer has stopped, please look at the minimserver.log file in the MinimServer/appData folder and copy and paste the last 50 lines of this file to a post here. You need to do this before restarting MinimServer as this overwrites the log information. Also, are there are any files in this folder with names containing "minimserver-crash" or "hserr"?
Find all posts by this user
Quote this message in a reply
21-05-2019, 01:12
Post: #3
RE: MinimServer stopped on Synology NAS
Ok here we go.

MinimServer crash dump, produced at 20190515-045033.907

ohNet fatal error: Unhandled exception NetworkAddressInUse at OpenHome/Network.cpp:324 in thread AdapterChange

"Thread-12" id=23 RUNNABLE
at java.management@9.0.1/sun.management.ThreadImpl.dumpThreads0(Native Method)
at java.management@9.0.1/sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:472)
at org.jminim.core.LogImpl.writeCrashDump(LogImpl.java:1206)
at org.jminim.core.LogImpl.fatalError(LogImpl.java:262)
- locked org.jminim.core.LogImpl@e726dc
at org.jminim.lib.OhNetService$FatalErrorHandler.message(OhNetService.java:874)
- locked org.jminim.lib.OhNetService$FatalErrorHandler@1a6ce83

"Thread-7" id=18 RUNNABLE (in native)
at java.base@9.0.1/java.net.PlainSocketImpl.socketAccept(Native Method)
at java.base@9.0.1/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:459)
at java.base@9.0.1/java.net.ServerSocket.implAccept(ServerSocket.java:551)
at java.base@9.0.1/java.net.ServerSocket.accept(ServerSocket.java:519)
at org.jminim.lib.HTTPService.runServerThread(HTTPService.java:333)
at org.jminim.lib.HTTPService.access$200(HTTPService.java:31)
at org.jminim.lib.HTTPService$1.run(HTTPService.java:318)

"Thread-6" id=17 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@ee0f5f
at java.base@9.0.1/java.lang.Object.wait(Object.java:516)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:388)

"Thread-5" id=16 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@1f6aded
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:1015)

"Thread-4" id=15 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@1bc04d5
at java.base@9.0.1/java.lang.Object.wait(Object.java:516)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:970)

"Thread-1" id=10 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$TimerThread@11e62de
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:3935)

"Thread-0" id=9 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$ActionThread@1ad28a2
at java.base@9.0.1/java.lang.Object.wait(Object.java:516)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:3889)

"Common-Cleaner" id=7 TIMED_WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@1b27e7f
at java.base@9.0.1/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.base@9.0.1/jdk.internal.ref.CleanerImpl.run(CleanerImpl.java:148)
at java.base@9.0.1/java.lang.Thread.run(Thread.java:844)
at java.base@9.0.1/jdk.internal.misc.InnocuousThread.run(InnocuousThread.java:122)

"Signal Dispatcher" id=4 RUNNABLE

"Finalizer" id=3 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@635230
at java.base@9.0.1/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.base@9.0.1/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:172)
at java.base@9.0.1/java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)

"Reference Handler" id=2 RUNNABLE
at java.base@9.0.1/java.lang.ref.Reference.waitForReferencePendingList(Native Method)
at java.base@9.0.1/java.lang.ref.Reference.processPendingReferences(Reference.java:174)
at java.base@9.0.1/java.lang.ref.Reference.access$000(Reference.java:44)
at java.base@9.0.1/java.lang.ref.Reference$ReferenceHandler.run(Reference.java:138)

"main" id=1 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on java.lang.Object@dbdb30
at java.base@9.0.1/java.lang.Object.wait(Object.java:516)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:3797)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2315)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1267)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:142)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:126)
at java.base@9.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base@9.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base@9.0.1/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base@9.0.1/java.lang.reflect.Method.invoke(Method.java:564)
at org.jminim.mlaunch.MinimLaunch.doLaunch(MinimLaunch.java:519)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:150)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:90)
at java.base@9.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base@9.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base@9.0.1/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base@9.0.1/java.lang.reflect.Method.invoke(Method.java:564)
at app//org.jminim.launch.Launcher.launch(Launcher.java:88)
at app//com.minimserver.launch.LaunchServer.main(LaunchServer.java:34)

- - - - - - - - - - - - - - - -
Find all posts by this user
Quote this message in a reply
21-05-2019, 09:10 (This post was last modified: 21-05-2019 09:10 by simoncn.)
Post: #4
RE: MinimServer stopped on Synology NAS
(21-05-2019 01:12)Bronx54 Wrote:  Ok here we go.

MinimServer crash dump, produced at 20190515-045033.907

ohNet fatal error: Unhandled exception NetworkAddressInUse at OpenHome/Network.cpp:324 in thread AdapterChange

Thanks for this information. This problem is caused by a flaw in ohNet (used by MinimServer) when the NAS is used as a VPN client in certain cases. Please can you post full details of your VPN setup, including which VPN service the NAS is accessing.
Find all posts by this user
Quote this message in a reply
21-05-2019, 10:16
Post: #5
RE: MinimServer stopped on Synology NAS
Sorry not sure how to get this information, not very savvy with networks, my NAS drive connects to an Apple airport extreme router via a Linksys 8 port gigabit switch. Internet connection is through a Draytek Vigor 130 modem.

I have looked through the DS115j settings and parameters and cannot find any reference to VPN settings, I have also looked at the Airport Extreme and cannot see any reference to VPN settings.
Find all posts by this user
Quote this message in a reply
21-05-2019, 10:26
Post: #6
RE: MinimServer stopped on Synology NAS
In DSM, open Control Panel, then select Network, then select the Network Interface tab. Do you see anything there that says VPN?
Find all posts by this user
Quote this message in a reply
21-05-2019, 13:23
Post: #7
RE: MinimServer stopped on Synology NAS
Hi I cannot see anything with VPN listed the below is what is shown on the screen you suggested.

The control panel, Network Interface has the following.

LAN
Connected

Use DHCP Yes
IP address 10.0.1.19
Subnet mask 255.255.255.0
IPv6 address fe80::211:32ff:fe40:daa9/64
Network Status 1000 Mbps, Full duplex, MTU 1500

PPPoE
Disconnected

IPv6 Tunneling
Disconnected
Find all posts by this user
Quote this message in a reply
21-05-2019, 13:54
Post: #8
RE: MinimServer stopped on Synology NAS
Thanks for this. To investigate the problem further, I will need you to produce a debug log and send it to me. I will send you a PM with instructions for doing this, probably tomorrow. Thanks very much for your help with investigating the cause of this problem.
Find all posts by this user
Quote this message in a reply
03-06-2019, 10:26
Post: #9
RE: MinimServer stopped on Synology NAS
I'm having this issue as well. If there is anything I can do to help, please let me know.
Find all posts by this user
Quote this message in a reply
03-06-2019, 11:28
Post: #10
RE: MinimServer stopped on Synology NAS
Do you have a VPN client running on your NAS (see above posts for how to check 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)