Post Reply 
MinimStreamer on Raspberry Pi dropout
25-02-2015, 21:40
Post: #17
RE: MinimStreamer on Raspberry Pi dropout
(25-02-2015 21:08)simoncn Wrote:  
(25-02-2015 20:52)jack_c85 Wrote:  Here's an instance of dropout before extending the stream delay to 10 seconds:

19:49:15.602 Thread-357: loading media playlist
19:49:15.688 Thread-357: adding media segment 222639654
19:49:15.703 Thread-357: playing media segment 222639654
19:49:16.306 Thread-357: finished writing 258098 bytes
19:49:16.319 Thread-357: sleeping for 2817 ms
19:49:19.138 Thread-357: loading media playlist
19:49:19.195 Thread-357: no new media segments available
19:49:19.209 Thread-357: sleeping for 1680 ms
19:49:20.890 Thread-357: loading media playlist
19:49:20.973 Thread-357: no new media segments available
19:49:20.979 Thread-357: sleeping for 1697 ms
19:49:22.686 Thread-357: loading media playlist
19:49:22.747 Thread-357: adding media segment 222639655
19:49:22.759 Thread-357: playing media segment 222639655
19:49:23.370 Thread-357: finished writing 258121 bytes
19:49:23.377 Thread-357: sleeping for 2817 ms
19:49:26.203 Thread-357: loading media playlist
19:49:26.299 Thread-357: no new media segments available
19:49:26.312 Thread-357: sleeping for 1649 ms
19:49:27.963 Thread-357: loading media playlist
19:49:28.021 Thread-357: no new media segments available
19:49:28.028 Thread-357: sleeping for 1689 ms
19:49:29.726 Thread-357: loading media playlist
19:49:29.771 Thread-357: no new media segments available
19:49:29.772 Thread-357: sleeping for 1706 ms
19:49:31.479 Thread-357: loading media playlist
19:49:31.563 Thread-357: adding media segment 222639656
19:49:31.578 Thread-357: playing media segment 222639656
19:49:32.158 Thread-357: finished writing 258052 bytes
19:49:32.167 Thread-357: sleeping for 2848 ms
19:49:35.023 Thread-357: loading media playlist
19:49:35.082 Thread-357: adding media segment 222639657
19:49:35.088 Thread-357: playing media segment 222639657
19:49:35.784 Thread-357: finished writing 258095 bytes
19:49:35.791 Thread-357: sleeping for 2733 ms
19:49:38.525 Thread-357: loading media playlist
19:49:47.341 Thread-355: HTTPConnection: end of input stream data
19:49:47.344 Thread-355: Streamer: getting request chain for org.jminim.lib.HTTPConnection$Request@ccc8e3
19:49:47.349 Thread-355: Streamer: stopping chain org.jstreamer.core.ChainImpl@6ae59d
19:49:47.349 Thread-355: ChainImpl: stop org.jstreamer.core.ChainImpl@6ae59d
19:49:47.350 Thread-355: ChainImpl: removing target from org.jstreamer.core.TargetChain@1978bea
19:49:47.350 Thread-355: ChainImpl: stop org.jstreamer.core.ChainImpl@ad8b8f
19:49:47.351 Thread-355: ChainImpl: stopping chain org.jstreamer.core.ChainImpl@ad8b8f
19:49:47.352 Thread-355: ChainSource: stopping reader thread
19:49:47.363 Thread-359: ChainSource: error reading input stream: org.jstreamer.OutputException: java.io.InterruptedIOException
19:49:47.363 Thread-359: Buffer: closing buffer: org.jstreamer.core.Buffer@1300d9a
19:49:47.364 Thread-355: ChainSource: stopping source
19:49:47.366 Thread-358: BufferReader: fillBuffer returned -1: buffer=org.jstreamer.core.Buffer@1300d9a
19:49:47.367 Thread-358: ChainTarget: end of data from input stream
19:49:47.368 Thread-358: ChainImpl: stop org.jstreamer.core.ChainImpl@6ae59d
19:49:47.369 Thread-358: BufferPoolReader: close
19:49:47.370 Thread-358: BufferReader: close: buffer=org.jstreamer.core.Buffer@157422
19:49:47.371 Thread-358: Buffer: removeReader: org.jstreamer.core.Buffer@157422
19:49:47.371 Thread-358: Buffer: removeReaders calling notifyAll: org.jstreamer.core.Buffer@157422
19:49:47.372 Thread-358: BufferReader: close: buffer=org.jstreamer.core.Buffer@1300d9a
19:49:47.372 Thread-358: Buffer: removeReader: org.jstreamer.core.Buffer@1300d9a
19:49:47.373 Thread-358: Buffer: removeReaders calling notifyAll: org.jstreamer.core.Buffer@1300d9a
19:49:53.579 Thread-357: loadMediaPlaylist openConnection: java.net.ConnectException: Connection refused
Error reading HLS stream: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:2​06)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
at sun.net.www.http.HttpClient.New(HttpClient.java:308)
at sun.net.www.http.HttpClient.New(HttpClient.java:326)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.j​ava:1167)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java​:1103)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:​997)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:931)
at org.jstreamer.lib.HTTPSource$ReaderThread.loadMediaPlaylist(HTTPSource.java:536)​
at org.jstreamer.lib.HTTPSource$ReaderThread.playStream(HTTPSource.java:677)
at org.jstreamer.lib.HTTPSource$ReaderThread.run(HTTPSource.java:483)
19:49:55.309 Thread-357: HTTPSource: closing piped output stream
19:49:55.315 Thread-355: HTTPSource: closing outgoing socket Socket[addr=a.files.bbci.co.uk/90.223.233.203,port=80,localport=53276]
19:49:55.315 Thread-355: ChainSource: source stopped

This log is very interesting. It shows that the BBC server didn't respond to the "loading media playlist" request sent at 19:49:38.525 and this eventually caused the Sonos to run out of audio data to play.

It might be that MinimStreamer is sending requests too frequently and the BBC server is detecting this. If so, it's strange that I haven't seen this myself. How long were you playing the stream before the dropout happened?

Oh ok... interesting. I wasn't playing it long, probably under 10 minutes.

This morning however it was fine for around 50 minutes, it completely varies.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: MinimStreamer on Raspberry Pi dropout - jack_c85 - 25-02-2015 21:40

Forum Jump:


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