MinimStreamer reconnect when recording

[acowx]

(16-10-2015 14:05)simoncn Wrote:  

(16-10-2015 00:54)acowx Wrote:  Wow, that's awesome. Darn BBC feeds..... It's my lifeline to home from the US&A

MinimStreamer 0.5.16 is available now. This should fix the problem from your latest log. I have also made another change to try to work around a different server issue that might cause an interrupted recording.

Latest log from 0.5.16, it seemed to stop around 10:18 this morning.

Weird.

[simoncn]

(18-10-2015 15:44)acowx Wrote:  Latest log from 0.5.16, it seemed to stop around 10:18 this morning.

Weird.

The log shows that the BBC server sent an error code 500 in response to a request from MinimStreamer and MinimStreamer retried the request a total of 10 times and got the same error every time. The retry logic was added in versions 0.5.15 and 0.5.16. Given that 10 retries didn't fix the problem, it seems that this error is not recoverable. I haven't seen this error myself and I don't know what is causing it. Given that the error is coming from the BBC server, it seems unlikely that it is related to other activity on your local network.

[acowx]

(18-10-2015 21:20)simoncn Wrote:  

(18-10-2015 15:44)acowx Wrote:  Latest log from 0.5.16, it seemed to stop around 10:18 this morning.

Weird.

The log shows that the BBC server sent an error code 500 in response to a request from MinimStreamer and MinimStreamer retried the request a total of 10 times and got the same error every time. The retry logic was added in versions 0.5.15 and 0.5.16. Given that 10 retries didn't fix the problem, it seems that this error is not recoverable. I haven't seen this error myself and I don't know what is causing it. Given that the error is coming from the BBC server, it seems unlikely that it is related to other activity on your local network.

Maybe add a config item to set the # of milliseconds between retries on a 500 response ? Dunno, but I can't imagine that the 500 response code lasts for an extended period of time.

I do agree with you that it's not related to my LAN, so that's comforting for me !

Or maybe I just schedule 6 x 1 hour recordings and hope for the best :-)

[simoncn]

(18-10-2015 23:02)acowx Wrote:  Maybe add a config item to set the # of milliseconds between retries on a 500 response ? Dunno, but I can't imagine that the 500 response code lasts for an extended period of time.

I do agree with you that it's not related to my LAN, so that's comforting for me !

Or maybe I just schedule 6 x 1 hour recordings and hope for the best :-)

I could add a delay between retries and/or increase the number of retries. I don't think it makes sense to make these values configurable because the behaviour of the BBC server will not be different for different users.

I will contact you by PM to arrange for you to try a test build with these changes. When we have found a combination that works reliably for you, I will publish it as an official release.

[acowx]

(19-10-2015 09:34)simoncn Wrote:  

(18-10-2015 23:02)acowx Wrote:  Maybe add a config item to set the # of milliseconds between retries on a 500 response ? Dunno, but I can't imagine that the 500 response code lasts for an extended period of time.

I do agree with you that it's not related to my LAN, so that's comforting for me !

Or maybe I just schedule 6 x 1 hour recordings and hope for the best :-)

I could add a delay between retries and/or increase the number of retries. I don't think it makes sense to make these values configurable because the behaviour of the BBC server will not be different for different users.

I will contact you by PM to arrange for you to try a test build with these changes. When we have found a combination that works reliably for you, I will publish it as an official release.

Full 6 hour recording without a hitch today.....

[acowx]

(20-10-2015 03:08)acowx Wrote:  

(19-10-2015 09:34)simoncn Wrote:  

(18-10-2015 23:02)acowx Wrote:  Maybe add a config item to set the # of milliseconds between retries on a 500 response ? Dunno, but I can't imagine that the 500 response code lasts for an extended period of time.

I do agree with you that it's not related to my LAN, so that's comforting for me !

Or maybe I just schedule 6 x 1 hour recordings and hope for the best :-)

I could add a delay between retries and/or increase the number of retries. I don't think it makes sense to make these values configurable because the behaviour of the BBC server will not be different for different users.

I will contact you by PM to arrange for you to try a test build with these changes. When we have found a combination that works reliably for you, I will publish it as an official release.

Full 6 hour recording without a hitch today.....

30'ish minutes today, log attached.

[simoncn]

(20-10-2015 22:50)acowx Wrote:  30'ish minutes today, log attached.

PM sent.