Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Audio dropouts
22-06-2018, 17:24
Post: #11
RE: Audio dropouts
I don't have another router to swap in but I did put in a switch as you suggested. No difference. The Lumin app sees the Synology UPnP server but not MinimServer.
Find all posts by this user
Quote this message in a reply
22-06-2018, 17:43
Post: #12
RE: Audio dropouts
I just heard back from Synology support. They found the following a "port conflict" I don't know what this means and the Synology support person didn't elaborate but this is the message that was generated on the error log on the NAS:

2018-02-16T21:56:32-06:00 Synology_Media synoscgi_SYNO.Core.Package.Installation_1_install[3038]: resource_api.cpp:163 Acquire service-cfg for MinimServer when 0x0001 (done)
[b][b]2018-02-16T21:56:35-06:00 Synology_Media servicetool: [b]service_is_port_conflict.c:1321 szTmpString=1900/udp conflict
2018-02-16T21:56:35-06:00 Synology_Media servicetool: utils.c:147 /var/packages/MinimServer/target/etc/MinimServer.sc conf file port conflict with existed conf file setting
[/b][/b][/b]
Find all posts by this user
Quote this message in a reply
22-06-2018, 17:45 (This post was last modified: 22-06-2018 17:51 by simoncn.)
Post: #13
RE: Audio dropouts
This is consistent with a network UPnP discovery issue. Some UPnP servers (I think including Synology) "flood" the network with very frequent device announcements to compensate for other faulty network components that don't handle some UPnP messages correctly. MinimServer uses the ohNet UPnP stack, which doesn't do this flooding and this can cause discovery problems if other network components aren't well behaved.

As you have eliminated most other possibilities, you might need to replace the router to solve this problem.
Find all posts by this user
Quote this message in a reply
22-06-2018, 17:49 (This post was last modified: 22-06-2018 17:50 by simoncn.)
Post: #14
RE: Audio dropouts
I just saw your message about the port conflict. It might be that there is a conflict between MinimServer and some other package that you have installed on your NAS. What other packages are in your installed list? Also, what DSM version are you running?
Find all posts by this user
Quote this message in a reply
22-06-2018, 18:32
Post: #15
RE: Audio dropouts
Installed packages:

Audio Station
Cloud Station
Download Station
Hyper Backup
Media Server
Photo Station
PHP 7.0
Universal Search
Video Station

DSM version 6.2-23739

BTW - when I went to the Package center, MinimServer was shown as an installed package but showed it was not running. I clicked the run button and for now is working. Somehow is got turned off...
Find all posts by this user
Quote this message in a reply
23-06-2018, 09:23
Post: #16
RE: Audio dropouts
I noticed that the port conflict message in your log is very old (2018-02-16) so unless you have been having problems since February, this shouldn't be relevant.
Find all posts by this user
Quote this message in a reply
23-06-2018, 12:50
Post: #17
RE: Audio dropouts
Good point regarding the date. I hadn't looked at it that closely. That date was around the time that I setup the Lumin player and installed MinimServer on the NAS. The issue over the past week ago was first recognized as dropouts and difficulty re-connecting to MinimServer. Yesterday it appears that something has stopped MinimServer from running altogether. Easy enough to get it running again apparently...but for how long? Any ideas what would cause it to stop running and have such a tenuous connection?
Find all posts by this user
Quote this message in a reply
23-06-2018, 15:35
Post: #18
RE: Audio dropouts
It sounds like MinimServer could have crashed. In this case, there might be some relevant information in the MinimServer/appData folder. You could look in the minimserver.log file in this folder immediately after the crash (before you restart MinimServer). There might also be other files in this folder that contain useful information (anything other than .config and .mcache files).

Are you running the latest 0.8.5.3 version of MinimServer? If not, it would be a good idea to update to this version.
Find all posts by this user
Quote this message in a reply
24-06-2018, 22:46
Post: #19
RE: Audio dropouts
(23-06-2018 15:35)simoncn Wrote:  It sounds like MinimServer could have crashed. In this case, there might be some relevant information in the MinimServer/appData folder. You could look in the minimserver.log file in this folder immediately after the crash (before you restart MinimServer). There might also be other files in this folder that contain useful information (anything other than .config and .mcache files).

Are you running the latest 0.8.5.3 version of MinimServer? If not, it would be a good idea to update to this version.

Yes, there were 3 crash logs in the MinimServer folder. Her is one of them:
BTW, the NAS was removed from it's direct connection to the router and is now on a switch. Since I restarted MinimServer the system has been working perfectly for the past 48 hours.


MinimServer crash dump, produced at 20180615-213243.505

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

"Thread-1860" id=1871 RUNNABLE (in native)

"Thread-1859" id=1870 RUNNABLE (in native)

"Thread-1858" id=1869 RUNNABLE (in native)

"Thread-1857" id=1868 RUNNABLE (in native)

"Thread-1603" id=1614 RUNNABLE (in native)

"Thread-922" id=933 RUNNABLE (in native)

"Thread-921" id=932 RUNNABLE (in native)

"Thread-15" id=25 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:1178)
at org.jminim.core.LogImpl.fatalError(LogImpl.java:253)
- locked org.jminim.core.LogImpl@113767
at org.jminim.lib.OhNetService$FatalErrorHandler.message(OhNetService.java:874)
- locked org.jminim.lib.OhNetService$FatalErrorHandler@1b7326a

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

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

"Thread-7" id=17 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=16 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@16b70af
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=15 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@e322b1
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:1015)

"Thread-4" id=14 WAITING
at java.base@9.0.1/java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@1388a05
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@198cfea
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:3476)

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

"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@336dd3
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@180a272
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@3ac477
at java.base@9.0.1/java.lang.Object.wait(Object.java:516)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:3338)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2003)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1192)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:137)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:121)
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:494)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:145)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:89)
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
25-06-2018, 07:18 (This post was last modified: 25-06-2018 07:19 by simoncn.)
Post: #20
RE: Audio dropouts
This is a known problem (see this thread). It is related to your VPN setup on the NAS and the solution is to set the ohnet.subnet property as described in this section. It is possible that this might also help with the dropouts issue.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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