Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MinimServer hanging after QNAP 4.3.3 Upgrade
13-08-2017, 12:01
Post: #1
MinimServer hanging after QNAP 4.3.3 Upgrade
Hi All,

After upgrading to QNAP 4.3.3 firmware, my most appreciated MinimServer keep on hanging after a while.

I have an Intel QNAP 469L. I tried reinstalling MinimServer 0.8.4.5, but that didn't solve the problem.

Below is one of the crash logs.

Any help is appreciated.

Thanks!


MinimServer crash dump, produced at 20170812-193935.607

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

"Thread-24" id=36 RUNNABLE (in native)

"Thread-23" id=35 RUNNABLE (in native)

"Thread-22" id=34 RUNNABLE
at sun.management.ThreadImpl.dumpThreads0(Native Method)
at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
at org.jminim.core.LogImpl.writeCrashDump(LogImpl.java:1178)
at org.jminim.core.LogImpl.fatalError(LogImpl.java:253)
- locked org.jminim.core.LogImpl@2a70ce50
at org.jminim.lib.OhNetService$FatalErrorHandler.message(OhNetService.java:805)
- locked org.jminim.lib.OhNetService$FatalErrorHandler@7155f3f5

"Thread-21" id=33 RUNNABLE (in native)

"Thread-20" id=32 RUNNABLE (in native)

"Thread-19" id=31 RUNNABLE (in native)

"Thread-18" id=30 RUNNABLE (in native)

"Thread-17" id=29 RUNNABLE (in native)

"Thread-16" id=28 RUNNABLE (in native)

"Thread-15" id=27 RUNNABLE (in native)

"Thread-14" id=26 RUNNABLE (in native)

"Thread-13" id=25 RUNNABLE (in native)
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-12" id=24 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@6fe5ad59
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:387)

"Thread-11" id=23 RUNNABLE (in native)

"Thread-10" id=22 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@24be4e88
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:946)

"Thread-9" id=21 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@8900601
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:901)

"Thread-6" id=18 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$TimerThread@568496bd
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:2884)

"Thread-5" id=17 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$ActionThread@14c96651
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:2838)

"Signal Dispatcher" id=4 RUNNABLE

"Finalizer" id=3 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@42d5a04e
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

"Reference Handler" id=2 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.Reference$Lock@4afd161b
at java.lang.Object.wait(Object.java:502)
at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"main" id=1 RUNNABLE (in native)
at sun.nio.fs.UnixNativeDispatcher.lstat0(Native Method)
at sun.nio.fs.UnixNativeDispatcher.lstat(UnixNativeDispatcher.java:300)
at sun.nio.fs.UnixFileAttributes.get(UnixFileAttributes.java:72)
at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.ja​va:52)
at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144​)
at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:9​9)
at java.nio.file.Files.readAttributes(Files.java:1737)
at java.nio.file.FileTreeWalker.getAttributes(FileTreeWalker.java:219)
at java.nio.file.FileTreeWalker.visit(FileTreeWalker.java:276)
at java.nio.file.FileTreeWalker.next(FileTreeWalker.java:372)
at java.nio.file.Files.walkFileTree(Files.java:2706)
at java.nio.file.Files.walkFileTree(Files.java:2742)
at com.minimserver.Server$Visitor.visitFile(Server.java:9487)
at com.minimserver.Server$Visitor.visitFile(Server.java:9393)
at java.nio.file.Files.walkFileTree(Files.java:2670)
at java.nio.file.Files.walkFileTree(Files.java:2742)
at com.minimserver.Server.readFiles(Server.java:4246)
at com.minimserver.Server.doStart(Server.java:2331)
at com.minimserver.Server.start(Server.java:516)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:167)
at org.jminim.core.ContextImpl.start(ContextImpl.java:92)
- locked java.lang.Object@383e5087
at org.jminim.core.RootContextImpl.startComponent(RootContextImpl.java:48)
at org.jminim.core.ContextImpl.start(ContextImpl.java:92)
- locked java.lang.Object@679a523f
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1495)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1004)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:127)
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:607)
at org.jminim.launch.Launcher.launch(Launcher.java:157)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:34)

- - - - - - - - - - - - - - - -
Find all posts by this user
Quote this message in a reply
13-08-2017, 22:22
Post: #2
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Please use MinimWatch to set the ohnet.debug property to Default+Network.

After the next failure, copy the minimserver.log file from the Public share of the QNAP to some other location. It is important to do this before you restart MinimServer.

I will PM you some instructions for uploading this saved log file to my FTP server. I will then look at it to try to find the cause of the problem.
Find all posts by this user
Quote this message in a reply
31-08-2017, 18:50
Post: #3
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Thank you!
Just followed the instructions and uploaded the log file.
Find all posts by this user
Quote this message in a reply
31-08-2017, 21:53
Post: #4
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Many thanks. I will look at this file and post an update in the next few days.
Find all posts by this user
Quote this message in a reply
31-08-2017, 22:21 (This post was last modified: 31-08-2017 22:21 by simoncn.)
Post: #5
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
My apologies. You also need to set the logging level (in the log window) to Debug. Without this, the log file doesn't contain the necessary information.

Please can you do this again with these settings. You can close the log window after changing the logging level setting because the necessary information is written to the minimserver.log file rather than being displayed in the log window.
Find all posts by this user
Quote this message in a reply
16-09-2017, 10:36
Post: #6
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Thanks Simon. The new log with the Debug turned on is now uploaded.
Find all posts by this user
Quote this message in a reply
16-09-2017, 15:36 (This post was last modified: 16-09-2017 15:38 by simoncn.)
Post: #7
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Thanks for this.

Unfortunately, it seems that this log file was produced without the Debug logging level being enabled. Please check your settings by doing the following:

1) In MinimWatch, select 'Show log' (not 'Options > Show log (watch)')
2) In the lower left corner of the log window, there is a setting for 'Logging level'. Check that this is set to Debug.
3) If the 'Logging level' property is not set to Debug, select this value in the drop-down box
4) Close the log window
5) In MinimWatch, select 'Properties' (not 'Options > Properties (watch)')
6) In the Properties window, select the System tab
7) Check the contents of the ohnet.debug field. This should be set to Default+Network.
8) If the ohnet.debug field is not set to Default+Network, type this value into the field and click the OK button

Many thanks.
Find all posts by this user
Quote this message in a reply
23-09-2017, 16:49
Post: #8
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Hi Simon,
I've followed your instructions and uploaded the new logs after the crash. I hope it will work this time Smile
Regards
Find all posts by this user
Quote this message in a reply
23-09-2017, 21:36
Post: #9
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Thanks for doing this. This log contains the information that I need.

In the log, I see some VPN activity. An adapter tun0 (10.8.0.1) is added and this is working OK. After this, another adapter tun2001 (10.7.7.16) is added and this is not working correctly with ohNet and MinimServer, leading to the crash. Please post your VPN configuration so that I can investigate further.
Find all posts by this user
Quote this message in a reply
24-09-2017, 16:29
Post: #10
RE: MinimServer hanging after QNAP 4.3.3 Upgrade
Thanks Simon.
tun2001 is TCP443 while the other is UDP connection.
The TCP connection did not have "Use default gateway on remote network" marked, while the UDP had it marked.
Could this be the issue? I turned on the option for TCP connection now.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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