Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Minimerver crash on Raspberry Pi
17-12-2014, 15:58
Post: #1
Minimerver crash on Raspberry Pi
Hello Simon,

Minimserver is crashing at irregular intervals. I found the following crash report:

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

"Thread-0" id=7 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.launch.Launcher$ConsoleThread@1aedf82
at java.lang.Object.wait(Object.java:502)
at org.jminim.launch.Launcher$ConsoleThread.run(Launcher.java:1168)

"Signal Dispatcher" id=4 RUNNABLE

"Finalizer" id=3 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@12f984a
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:142)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:158)
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@c4ed6a
at java.lang.Object.wait(Object.java:502)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157)

"main" id=1 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.Object@1767c8d
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:2245)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1226)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:827)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:91)
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:483)
at org.jminim.launch.Launcher.doLaunch(Launcher.java:502)
at org.jminim.launch.Launcher.launch(Launcher.java:140)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:30)

I am running 0.8.2

Hopefully this can somehow be fixed.

Thanks, Guus
Find all posts by this user
Quote this message in a reply
18-12-2014, 08:40
Post: #2
RE: Minimerver crash on Raspberry Pi
(17-12-2014 15:58)guussie Wrote:  Hello Simon,

Minimserver is crashing at irregular intervals. I found the following crash report:

I am running 0.8.2

Hopefully this can somehow be fixed.

Thanks, Guus

This "crash report" doesn't show any evidence of a crash. Did you accidentally omit some part of the crash report file?
Find all posts by this user
Quote this message in a reply
18-12-2014, 09:31
Post: #3
RE: Minimerver crash on Raspberry Pi
(18-12-2014 08:40)simoncn Wrote:  
(17-12-2014 15:58)guussie Wrote:  Hello Simon,

Minimserver is crashing at irregular intervals. I found the following crash report:

I am running 0.8.2

Hopefully this can somehow be fixed.

Thanks, Guus

This "crash report" doesn't show any evidence of a crash. Did you accidentally omit some part of the crash report file?

Hi Simon,

I attach the report as it was logged.

Guus


Attached File(s)
.log  minimserver-crash-20141217-130301.log (Size: 5.63 KB / Downloads: 1)
Find all posts by this user
Quote this message in a reply
18-12-2014, 09:42
Post: #4
RE: Minimerver crash on Raspberry Pi
(18-12-2014 09:31)guussie Wrote:  Hi Simon,

I attach the report as it was logged.

Guus

Thanks very much! The crash information is at the start of the file:

ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Queue.cpp:179 in thread UpnpSession 0

As a first step, please update to MinimServer 0.8.3 (which contains a more recent level of ohNet) and let me know if you are still seeing this problem.
Find all posts by this user
Quote this message in a reply
22-12-2014, 08:36
Post: #5
RE: Minimerver crash on Raspberry Pi
(18-12-2014 09:42)simoncn Wrote:  As a first step, please update to MinimServer 0.8.3 (which contains a more recent level of ohNet) and let me know if you are still seeing this problem.

Hello Simon,

I upgraded to 0.8.3 and just had another crash.

Crash report below.

Guus



MinimServer crash dump, produced at 20141222-072348.167

ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Queue.cpp:179 in thread UpnpSession 1

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

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

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

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

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

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

"Thread-13" id=20 RUNNABLE
at sun.management.ThreadImpl.dumpThreads0(Native Method)
at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:440)
at org.jminim.core.LogImpl.writeCrashDump(LogImpl.java:1172)
at org.jminim.core.LogImpl.fatalError(LogImpl.java:251)
- locked org.jminim.core.LogImpl@e4054e
at org.jminim.lib.OhNetService$FatalErrorHandler.message(OhNetService.java:715)
- locked org.jminim.lib.OhNetService$FatalErrorHandler@10fac93

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

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

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

"Thread-8" id=15 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.launch.Launcher$ConsoleRequest@1bdb679
at java.lang.Object.wait(Object.java:502)
at org.jminim.launch.Launcher$ConsoleRequest.awaitCompletion(Launcher.java:1392)
at org.jminim.launch.Launcher$ConsoleReader.readLine(Launcher.java:1267)
- locked org.jminim.launch.Launcher$ConsoleReader@1ca3548
at com.minimserver.lib.ServerConsole$ServerConsoleThread.run(ServerConsole.java:102​2)

"Thread-7" id=14 RUNNABLE (in native)
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:404)
at java.net.ServerSocket.implAccept(ServerSocket.java:545)
at java.net.ServerSocket.accept(ServerSocket.java:513)
at org.jminim.lib.HTTPService.runServerThread(HTTPService.java:328)
at org.jminim.lib.HTTPService.access$200(HTTPService.java:28)
at org.jminim.lib.HTTPService$1.run(HTTPService.java:313)

"Thread-6" id=13 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@1a50cf5
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:365)

"Thread-5" id=12 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@1624826
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:856)

"Thread-4" id=11 WAITING
at java.lang.Object.wait(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@15453f7
at java.lang.Object.wait(Object.java:502)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:811)

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

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

"Thread-0" id=7 RUNNABLE (in native)
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:143)
- locked java.lang.Object@1cd04b3
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 sun.nio.ch.ChannelInputStream@852e56
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 java.io.InputStreamReader@1147eb
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 java.io.InputStreamReader@1147eb
at java.io.BufferedReader.readLine(BufferedReader.java:389)
at org.jminim.launch.Launcher$ConsoleThread.run(Launcher.java:1352)

"Signal Dispatcher" id=4 RUNNABLE

"Finalizer" id=3 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.ref.ReferenceQueue$Lock@3fa06c
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:142)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:158)
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@1e8c1c4
at java.lang.Object.wait(Object.java:502)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157)

"main" id=1 WAITING
at java.lang.Object.wait(Native Method)
- waiting on java.lang.Object@e2ba71
at java.lang.Object.wait(Object.java:502)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:2566)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1363)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:976)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:107)
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:483)
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)

- - - - - - - - - - - - - - - -
Find all posts by this user
Quote this message in a reply
22-12-2014, 09:13
Post: #6
RE: Minimerver crash on Raspberry Pi
(22-12-2014 08:36)guussie Wrote:  Hello Simon,

I upgraded to 0.8.3 and just had another crash.

Crash report below.

Guus

MinimServer crash dump, produced at 20141222-072348.167

ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Queue.cpp:179 in thread UpnpSession 1

This is the same problem.

What were you doing with MinimServer and/or with the Raspberry Pi immediately before the crash occurred?

Are you using Raspbian to run MinimServer?
Find all posts by this user
Quote this message in a reply
22-12-2014, 09:25
Post: #7
RE: Minimerver crash on Raspberry Pi
(22-12-2014 09:13)simoncn Wrote:  
(22-12-2014 08:36)guussie Wrote:  Hello Simon,

I upgraded to 0.8.3 and just had another crash.

Crash report below.

Guus

MinimServer crash dump, produced at 20141222-072348.167

ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Queue.cpp:179 in thread UpnpSession 1

This is the same problem.

What were you doing with MinimServer and/or with the Raspberry Pi immediately before the crash occurred?

Are you using Raspbian to run MinimServer?

Yes, I am using Raspbian. It's a little server and I was not doing anything in particular.

However, I am running Logitech Media Server (without DLNA) on the same machine in order to have access to streaming services on another RPi running mediaplayer.

Is there a way I could check what happend on the RPi?

I will now be away for a week. I will keep the server running....
Find all posts by this user
Quote this message in a reply
22-12-2014, 10:51
Post: #8
RE: Minimerver crash on Raspberry Pi
(22-12-2014 09:25)guussie Wrote:  Yes, I am using Raspbian. It's a little server and I was not doing anything in particular.

However, I am running Logitech Media Server (without DLNA) on the same machine in order to have access to streaming services on another RPi running mediaplayer.

Is there a way I could check what happend on the RPi?

I will now be away for a week. I will keep the server running....

This crash is very likely to be triggered by some activity within MinimServer or from other DLNA devices on the network or by the RPi enabling or disabling a network interface. I don't think the error message and crash dump provide enough information to debug the problem without also knowing what activity triggered it.

You can capture a log of this activity by making the following changes:

1) From the MinimWatch minim icon, select "Properties" (not "Options > Properties (watch)") and change the ohnet.debug property to All-Timer

2) From the MinimWatch minim icon, select "Show log" (not "Options > Show log (watch)") and change the logging level to Debug, then close the log window

When the crash occurs next, the file minimserver/data/minimserver.log will contain the additional information that I need. Please copy this file before you restart MinimServer, as restarting MinimServer will overwrite this file.
Find all posts by this user
Quote this message in a reply
06-01-2015, 08:51
Post: #9
RE: Minimerver crash on Raspberry Pi
(22-12-2014 10:51)simoncn Wrote:  
(22-12-2014 09:25)guussie Wrote:  Yes, I am using Raspbian. It's a little server and I was not doing anything in particular.

However, I am running Logitech Media Server (without DLNA) on the same machine in order to have access to streaming services on another RPi running mediaplayer.

Is there a way I could check what happend on the RPi?

I will now be away for a week. I will keep the server running....

This crash is very likely to be triggered by some activity within MinimServer or from other DLNA devices on the network or by the RPi enabling or disabling a network interface. I don't think the error message and crash dump provide enough information to debug the problem without also knowing what activity triggered it.

You can capture a log of this activity by making the following changes:

1) From the MinimWatch minim icon, select "Properties" (not "Options > Properties (watch)") and change the ohnet.debug property to All-Timer

2) From the MinimWatch minim icon, select "Show log" (not "Options > Show log (watch)") and change the logging level to Debug, then close the log window

When the crash occurs next, the file minimserver/data/minimserver.log will contain the additional information that I need. Please copy this file before you restart MinimServer, as restarting MinimServer will overwrite this file.

Hello Simon,

Here is a link to the minim server.log file after a crash:

https://www.dropbox.com/s/5848d578qihmbl...g.zip?dl=0

Greetings, Guus
Find all posts by this user
Quote this message in a reply
06-01-2015, 09:47
Post: #10
RE: Minimerver crash on Raspberry Pi
(06-01-2015 08:51)guussie Wrote:  Hello Simon,

Here is a link to the minim server.log file after a crash:

https://www.dropbox.com/s/5848d578qihmbl...g.zip?dl=0

Greetings, Guus

There is no evidence of a crash in this log file. MinimServer was ended at 02:00:08 by an external action (either "kill" or "stopall").
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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