MinimSrver won't load onto Linn Kinsky

[JCHRISJORDAN]

Hi,
I have a problem with MinimServer.
Kinsky will not load it. When I try, the MinimServer icon on the Taskbar changes from green to grey. The MinimWatch log is as follows:
“MinimWatch 0.8.4, Copyright © 2012-2016 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot™ Client VM (build 25.111-b14, mixed mode)
Platform default charset is windows-1252
Active subnet is 192.168.0.0
Startup complete
starting MinimServer[nas-BE-E5-51]
MinimServer[nas-BE-E5-51] is running
Error 1 [Unknown] invoking GetAllPackageStatus on remote runtime monitor
Error 1 [Unknown] invoking GetProperty on remote runtime monitor”
I have tried re-installing both Kinsky and MinimServer on the PC (but not yet tried re-installing it on the ReayNAS NV2)
The PC is running Windows 10.
There are approx. 500,000 songs on the NAS.
Can you advise me of a way forward, please?
Regards,
Chris

[simoncn]

These symptoms mean that MinimServer (running on the NAS) has crashed. The MinimServer log is available as the file minimerver.log in the NAS shared folder named "backup" . You should be able to access this shared folder from your Windows PC.

The minimserver.log file records information from most errors but it might not capture information about the crash you are seeing. To capture additional diagnostic information that should help with this, please do the following:

1) Create a plain text file named minimstart.conf containing the following line:
outfile = /c/backup/minimserver-out.log

2) Copy this file to the "backup" shared folder on the NAS

3) Stop and restart MinimServer on the NAS

You should now see an additional file named minimserver-out.log in the "backup" shared folder.

Now try to browse the MinimServer library from Kinsky. After the crash (minim icon changed from green to grey), copy the minimserver.log and minimserver-out.log files from the "backup" folder to another location on your PC. It is important to do this before you restart MinimServer.

Now create a zip file containing the copied minimserver.log and minimserver-out.log files and attach this zip file to a post here. I will look at the contents of the zip file and let you know what is causing the crash.

[JCHRISJORDAN]

Hi, Simon.
I tried creating minimstart.conf as per your instructions, loaded into the backup folder, but it did not generate a minimserver-out.log file.
What seems to be happening is that as soon as MinimServer goes active on the NAS, it generates a minimserver-crash.log. The icon stays green until I try to re-start MinimServer, when the icon goes grey.

I have attached the latest minimserver-crash.log file for you to look at.

I can't locate an add attachment facility on the thread, so I have cut & pasted the contents of minimserver-crash-20171107-130816.log below:


MinimServer crash dump, produced at 20171107-130816.541

OhNetService: unable to write message to log

java.lang.NullPointerException
at org.jminim.lib.OhNetService$LogOutput.message(OhNetService.java:675)

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

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

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

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

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

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

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

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

"Thread-12" id=20 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-11" id=19 RUNNABLE (in native)

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

"Thread-9" id=17 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@1655d6a
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:387)

"Thread-8" id=16 BLOCKED
at org.jminim.core.LogImpl.printStackTraceSync(LogImpl.java:1105)
- blocked on org.jminim.core.LogImpl@12b64c1
- owned by "Thread-7" id=15
at org.jminim.core.LogImpl.errorEx(LogImpl.java:221)
at com.minimserver.Server$ContentDirectoryProvider.search(Server.java:18972)
at org.openhome.net.device.providers.DvProviderUpnpOrgContentDirectory1$DoSearch.ac​tionInvoked(DvProviderUpnpOrgContentDirectory1.java:1049)

"Thread-7" id=15 RUNNABLE
at sun.management.ThreadImpl.dumpThreads0(Native Method)
at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
at org.jminim.core.LogImpl.writeCrashDump(LogImpl.java:1221)
at org.jminim.core.LogImpl.printStackTraceSync(LogImpl.java:1146)
- locked org.jminim.core.LogImpl@12b64c1
at org.jminim.core.LogImpl.reportErrorEx(LogImpl.java:235)
at org.jminim.lib.OhNetService$LogOutput.message(OhNetService.java:699)
- locked org.jminim.lib.OhNetService$LogOutput@a3fbcc

"Thread-6" id=14 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@1ee9e17
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:860)

"Thread-5" id=13 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@cf038d
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:815)

"Thread-2" id=9 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$TimerThread@5c6939
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:2765)

"Thread-1" id=8 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.core.RuntimeImpl$ActionThread@1a497a5
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:2719)

"Signal Dispatcher" id=4 RUNNABLE

"Finalizer" id=3 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@39a7e0
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@ca0701
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 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.Object@1faaf80
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:2636)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1398)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1110)
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:677)
at org.jminim.launch.Launcher.launch(Launcher.java:210)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:34)

- - - - - - - - - - - - - - - -

Regards, & once again, thank you for your help.

Chris

[simoncn]

Thanks for this crash log. It gives me some very useful information about what is happening.

When you post a message, if you scroll down to below the box where you enter the text you will see an Attachments section with a New Attachment: Browse button and an Add Attachment button. The former selects a file to attach and the latter actually does the attaching.

I am working on producing a test build for you to try. When it is ready, I will send you a PM.