Reply to thread

Message: <blockquote data-quote="Owlsroost" data-source="post: 1221297" data-attributes="member: 83973">It seems to be a related problem to the 'unable to play' one - an RTSP PLAY request from client to server is timing out after 0.5 sec:[2017-05-11 09:47:14,327] [ bad9638] [ efc] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue    :p" loading="lazy" data-shortname=":p" />lay(): start = 3115.000000, duration = 3716.076904, m_duration = 3715.077881[2017-05-11 09:47:14,327] [ bad9638] [ efc] - CRTSPClient::InternalPlay() - start = 3115.000000[2017-05-11 09:47:14,828] [ bad9638] [ efc] - CRTSPClient::InternalPlay(): RTSP PLAY timed out[2017-05-11 09:47:14,828] [ bad9638] [ efc] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" />hutdown()[2017-05-11 09:47:14,828] [ bad9638] [ efc] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" />hutdown(): send RTSP TEARDOWN[2017-05-11 09:47:15,154] [ bad9638] [ efc] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" />topBufferThread()[2017-05-11 09:47:15,154] [ bad9638] [1ec4] - CRTSPClient::ThreadProc(): thread stopping, thread ID = 7876[2017-05-11 09:47:15,154] [ bad9638] [ efc] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" />topBufferThread(): done...but without the server logs for the same period we only have half the story. Since it's already played some of the file (before doing the 'seek' to get to the resume point, which is when it fails), it can't be due to disks not running. The StreamingServer.log should show the seek commands happening (when you can catch another instance of the failure).</blockquote>

Verification