Live TV Not working Since latest Beta Version

General Discussions Plex Features
62

Lets concentrate on today’s logs,

There were two devices/apps using livetv.

Android (CUBOT MAX) on IP address 192.168.0.4
Plex Web using Chrome from IP Address 192.168.0.19

The last actions were -
channel 207 being tuned on Plex Web at 12:40:37
and
channel 207 being tuned on the android device at 13:47:45

LiveTV stream to Plex Web continued till 13:15 when it was stopped by the web app.

streaming to the android continued till 13:49 when the android app asked the server to stop and the livetv session was cancelled

What am i looking for? What was being attempted that did not work?

63

Hi @sa2000
This is the latest one within the last 5 mins!! Channel 207 was being recorded while I was watching BBC News on Channel 231 and when it got to the end of the last recording it through "Playback Error"on my Laptop on 231 at 18:00

I thought this one may throw the light on the issue? I hope?

I’m not an expert in the Plex Logs, but at 18:31 does it actually stop the Tuner on both programmes? This cannot be right can it? If it is, why would it do this?

What I’m trying to say in my crazy way is that a recording that was in process and has now stopped shouldn’t stop another channel that someone is watching should it? This is the issue I’ve had either on the Network or across the Internet using Plex Web. Hope I’ve made myself a little clearer now? I know my ex-wife and Girlfriend both hate me for the way I try and explain myself, so apologies in advance…

Dave

Plex Media Server Logs_2018-11-01_18-31-04.zip (3.2 MB)

64

This is a good step, glad to see it. However… I am running into a problem where channels won’t tune, but Plex isn’t waiting any time at all before giving up. This morning about half my attempts fail.

Here is the log for a failed tune attempt:

Nov 02, 2018 09:46:31.161 [3980] DEBUG - DVR:Subscription: Starting a new rolling subscription for session eog25e2rxy4u2jn3zuhni716 channel 2470.
Nov 02, 2018 09:46:31.161 [5704] DEBUG - Client [eog25e2rxy4u2jn3zuhni716] reporting timeline state stopped, progress of 0/0ms for guid=, ratingKey=382545 url=, key=/livetv/sessions/2efc4a4d-c1af-4e45-ab0c-2be72701440e, containerKey=, metadataId=382545, source=
Nov 02, 2018 09:46:31.161 [3980] DEBUG - DVR:Subscription: Cancelling a current rolling subscription for the same session identifier.
Nov 02, 2018 09:46:31.161 [3980] DEBUG - DVR:Grabber: Cancelling operation for ‘Live TV - Session’ with status cancelled.

I’m using xTeVe and in the above scenario, Plex never requests a stream at all from xTeVe. The channel in question is playable with no issues in VLC.

65

@sa2000 Any update on the issue of recordings finished shutting down both tuners? Not using the server at the moment, saying that none of the family are, we’ve gotten to a stage where we’re beginning to give up hope totally.

Many thanks in advance,

Dave

66

@sa2000 @ChuckPa Sorry for being a pain in the unmentionables, but I was wondering if any update on this issue was on the cards? Even with my eyesight issues I’ve scanned the logs and cannot understand why either a recording ending or change or stop a channel would cause the second Tuner in one of my 3 Hauppage WinTV DuoHD receivers to stop both tuners and not the one?
I have the Tuners plugged into USB3 ports too, so I know there’s enough bandwidth for the devices.

I do hope this can be fixed as my 3 year old son can watch his childrens channel without it being interrupted by “Playback Error” when a recording is finished or one of the users on the server stop or changes channels, I know in my latest log files from November 1st at 1800 to 1831 show that Plex shuts off both Tuners when it should have only shut off the one that was being used by the DVR and the other I was watching, and it stopped it in mid flow.

Dave

67

I have no livetv capability here so am completely unable to assist further.

68

I am still looking into your issue together with many other forum reported issues - I have not got to a point where I could see a problem to be referred to the development team - investigation will continue

If you have specific actions to highlight that you spot as being wrong let me know what it is and if you have already provided logs that cover that time

69

Hi @sa2000,
I’ve uploaded my logs from November 1st straight after the issue happened between 1800 and 1832, so far it’s rendering my Live TV system I’ve built useless when a recording ends or someone on the same tuner either stops a channel or changes a channel it closes the other tuner down, so I know this is in the logs I have supplied on November 1st.
If you cannot see a problem then I’m at a loss that you cannot answer what my problem is before handing it to the Dev’s or passing it on to another person to lighten your workload.

Please answer this one though, if a recording is happening on the same tuner that someone is watching TV on or 2 are watching 2 programmes on a Dual TV receiver like the WinTV DuoHD should the recording or another user stopping the one tuner cause the tuner I am watching to shut down also? I know what your answer is going to be, and I’m an ex-software dev and IT Support Tech…

Dave

70

@ChuckPa Thanks Chuck, It’s beginning to drive me crazy, and I amazed that no one can assist on the issue I’m experiencing. I’m running the 3xWinTV DuoHD receivers on USB3 so they have enough bandwidth to cope so somewhere along the line, Plex is shutting down 2 Tuners when it only has to shut down one if either a recording is finished or another user on the network or internet changes a channel or stops their instance. In my eyes this should not happen and I cannot believe that another Team Member can see this issue to pass on to the Dev’s to sort out, it’s making me think about switching to something else after I have spent the money on the 3 Dual Receive USB Tuners, something I’m not willing to do yet as I’ve been using Plex for a number of years now without any issues till now.
This issue needs to be addressed, I am very surprised no other user has experienced this issue either on another Linux/Windows or Mac PMS.

Here’s hoping someone can get the Dev’s to answer this issue…

Dave

71

@sa2000 Just to show what is happening, as it happened on November 1st at 1830…

Nov 01, 2018 18:30:19.333 [0x7f47737fe700] WARN - [E] http_streamer_t: http write error
Nov 01, 2018 18:30:19.333 [0x7f476d7f2700] INFO - [I] http_streamer_t::send_thread_func: removing http client

Nov 01, 2018 18:30:19.333 [0x7f476d7f2700] INFO - [I] http_streamer_t::send_thread_func: all clients are deleted. Setting exit flag

Nov 01, 2018 18:30:19.336 [0x7f476cff1700] INFO - [I] streamer_container_t::control_thread. Removed disconnected streamer b9e6648d-5f2d-40d0-8a4f-708e76aa4115
Nov 01, 2018 18:30:19.337 [0x7f476cff1700] INFO - [I] streamer_container_t::delete_streamer. Last streamer was deleted. Stop program streamer
Nov 01, 2018 18:30:19.337 [0x7f476cff1700] INFO - [I] dvb_program_streamer_t::stop. Stoping program streamer for channel triplet://9018:4222:4352
Nov 01, 2018 18:30:19.337 [0x7f476cff1700] INFO - [I] transponder_streamer::stop_channel. Stop request for channel triplet://9018:4222:4352
Nov 01, 2018 18:30:19.349 [0x7f476e7f4700] INFO - [I] CTVSStreamSource::RemoveAllPids. Removing PIDs for client triplet://9018:4222:4352
Nov 01, 2018 18:30:19.349 [0x7f476cff1700] INFO - [I] transponder_streamer::start_idle_timer
Nov 01, 2018 18:30:19.357 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 0
Nov 01, 2018 18:30:19.365 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 1
Nov 01, 2018 18:30:19.373 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 16
Nov 01, 2018 18:30:19.381 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 17
Nov 01, 2018 18:30:19.389 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 18
Nov 01, 2018 18:30:19.397 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 500
Nov 01, 2018 18:30:19.405 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 501
Nov 01, 2018 18:30:19.413 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 502
Nov 01, 2018 18:30:19.421 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 505
Nov 01, 2018 18:30:19.429 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 7103
Nov 01, 2018 18:30:19.437 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 7105
Nov 01, 2018 18:30:19.445 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 7201
Nov 01, 2018 18:30:19.456 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 7219
Nov 01, 2018 18:30:19.468 [0x7f47477fe700] INFO - [I] tuner 0, demux 0. Deleting PID 8191
Nov 01, 2018 18:30:21.158 [0x7f4773fff700] INFO - [I] device_manager_t::idle_timer_func. Stream container for channel triplet://9018:4222:4352 on device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Deleting it.
Nov 01, 2018 18:30:28.433 [0x7f476dff3700] INFO - [I] Stopping graph
Nov 01, 2018 18:30:28.477 [0x7f476e7f4700] INFO - [I] Stop device request for tuner 0, frontend 0
Nov 01, 2018 18:30:28.485 [0x7f47477fe700] INFO - [I] Exiting streaming thread for tuner 0, frontend 0
Nov 01, 2018 18:30:31.208 [0x7f4773fff700] INFO - [I] device_manager_t::idle_timer_func. Device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Unloading it.
Nov 01, 2018 18:30:31.209 [0x7f4773fff700] INFO - [I] transponder_streamer::stop_idle_timer
Nov 01, 2018 18:30:31.209 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Waiting for streaming thread to stop
Nov 01, 2018 18:30:31.239 [0x7f476e7f4700] INFO - [I] Stop device request for tuner 65535, frontend 0
Nov 01, 2018 18:30:31.239 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Streaming is stopped
Nov 01, 2018 18:30:31.239 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Stream source is stopped
Nov 01, 2018 18:30:31.486 [0x7f476dff3700] INFO - [I] transponder_streamer::idle_thread_func finished

Nov 01, 2018 18:31:01.428 [0x7f4772ffd700] WARN - [E] http_streamer_t: http write error
Nov 01, 2018 18:31:01.428 [0x7f4745ffb700] INFO - [I] http_streamer_t::send_thread_func: removing http client
Nov 01, 2018 18:31:01.428 [0x7f4745ffb700] INFO - [I] http_streamer_t::send_thread_func: all clients are deleted. Setting exit flag

Nov 01, 2018 18:31:01.438 [0x7f472ffff700] INFO - [I] streamer_container_t::control_thread. Removed disconnected streamer bde42af8-733c-47c6-b967-fdfc0899fed0
Nov 01, 2018 18:31:01.438 [0x7f472ffff700] INFO - [I] streamer_container_t::delete_streamer. Last streamer was deleted. Stop program streamer
Nov 01, 2018 18:31:01.438 [0x7f472ffff700] INFO - [I] dvb_program_streamer_t::stop. Stoping program streamer for channel triplet://9018:32771:33472
Nov 01, 2018 18:31:01.438 [0x7f472ffff700] INFO - [I] transponder_streamer::stop_channel. Stop request for channel triplet://9018:32771:33472
Nov 01, 2018 18:31:01.468 [0x7f4744ff9700] INFO - [I] CTVSStreamSource::RemoveAllPids. Removing PIDs for client triplet://9018:32771:33472
Nov 01, 2018 18:31:01.468 [0x7f472ffff700] INFO - [I] transponder_streamer::start_idle_timer
Nov 01, 2018 18:31:01.476 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 0
Nov 01, 2018 18:31:01.484 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 1
Nov 01, 2018 18:31:01.492 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 16
Nov 01, 2018 18:31:01.500 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 17
Nov 01, 2018 18:31:01.508 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 18
Nov 01, 2018 18:31:01.516 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 1030
Nov 01, 2018 18:31:01.524 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 1031
Nov 01, 2018 18:31:01.532 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 1032
Nov 01, 2018 18:31:01.542 [0x7f472f7fe700] INFO - [I] tuner 1, demux 0. Deleting PID 8191
Nov 01, 2018 18:31:01.599 [0x7f4773fff700] INFO - [I] device_manager_t::idle_timer_func. Stream container for channel triplet://9018:32771:33472 on device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:1 is idle. Deleting it.

I have noticed a Write Error on both Tuners when either the recording stops or someone on the same tuner changes or stops the other receiver on the same USB device… Now I have done this work, can you assist? I will add I am registered blind too…

I have made the sections that it shows a Write Error and Deletes both Clients so it’s easier for me to see and others…

Cheers and hope we can resolve this issue quickly…

Spoke to soon, this is with just one user on using it…

Nov 03, 2018 21:25:25.578 [0x7f47707f8700] WARN - [E] http_streamer_t: http write error
Nov 03, 2018 21:25:25.578 [0x7f4747fff700] INFO - [I] http_streamer_t::send_thread_func: removing http client

Nov 03, 2018 21:25:25.578 [0x7f4747fff700] INFO - [I] http_streamer_t::send_thread_func: all clients are deleted. Setting exit flag

Nov 03, 2018 21:25:25.581 [0x7f476d7f2700] INFO - [I] streamer_container_t::control_thread. Removed disconnected streamer 38555454-0864-4770-b1b4-95ca170c9eec
Nov 03, 2018 21:25:25.582 [0x7f476d7f2700] INFO - [I] streamer_container_t::delete_streamer. Last streamer was deleted. Stop program streamer
Nov 03, 2018 21:25:25.582 [0x7f476d7f2700] INFO - [I] dvb_program_streamer_t::stop. Stoping program streamer for channel triplet://9018:4222:4222
Nov 03, 2018 21:25:25.582 [0x7f476d7f2700] INFO - [I] transponder_streamer::stop_channel. Stop request for channel triplet://9018:4222:4222
Nov 03, 2018 21:25:25.585 [0x7f476e7f4700] INFO - [I] CTVSStreamSource::RemoveAllPids. Removing PIDs for client triplet://9018:4222:4222
Nov 03, 2018 21:25:25.585 [0x7f476d7f2700] INFO - [I] transponder_streamer::start_idle_timer
Nov 03, 2018 21:25:25.593 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 0
Nov 03, 2018 21:25:25.601 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 1
Nov 03, 2018 21:25:25.609 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 16
Nov 03, 2018 21:25:25.617 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 17
Nov 03, 2018 21:25:25.625 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 18
Nov 03, 2018 21:25:25.633 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 100
Nov 03, 2018 21:25:25.641 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 101
Nov 03, 2018 21:25:25.649 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 102
Nov 03, 2018 21:25:25.657 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 105
Nov 03, 2018 21:25:25.665 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 106
Nov 03, 2018 21:25:25.673 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 152
Nov 03, 2018 21:25:25.681 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 7103
Nov 03, 2018 21:25:25.689 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 7105
Nov 03, 2018 21:25:25.697 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 7201
Nov 03, 2018 21:25:25.707 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 7219
Nov 03, 2018 21:25:25.718 [0x7f476cff1700] INFO - [I] tuner 0, demux 0. Deleting PID 8191
Nov 03, 2018 21:25:29.364 [0x7f4773fff700] INFO - [I] device_manager_t::idle_timer_func. Stream container for channel triplet://9018:4222:4222 on device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Deleting it.
Nov 03, 2018 21:25:35.112 [0x7f476dff3700] INFO - [I] Stopping graph
Nov 03, 2018 21:25:35.150 [0x7f476e7f4700] INFO - [I] Stop device request for tuner 0, frontend 0
Nov 03, 2018 21:25:35.160 [0x7f476cff1700] INFO - [I] Exiting streaming thread for tuner 0, frontend 0
Nov 03, 2018 21:25:39.384 [0x7f4773fff700] INFO - [I] device_manager_t::idle_timer_func. Device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Unloading it.
Nov 03, 2018 21:25:39.384 [0x7f4773fff700] INFO - [I] transponder_streamer::stop_idle_timer
Nov 03, 2018 21:25:39.384 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Waiting for streaming thread to stop
Nov 03, 2018 21:25:39.418 [0x7f476e7f4700] INFO - [I] Stop device request for tuner 65535, frontend 0
Nov 03, 2018 21:25:39.418 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Streaming is stopped
Nov 03, 2018 21:25:39.418 [0x7f4773fff700] INFO - [I] CTVSStreamSource::Term. Stream source is stopped
Nov 03, 2018 21:25:40.161 [0x7f476dff3700] INFO - [I] transponder_streamer::idle_thread_func finished

This happened tonight within 10 minutes ago after 3 hours of one user just using it tuned to one channel, the channel they were tuned to has 100% signal and quality, so it’s definitely a Plex issue and needs to be investigated…

Dave

72

Good Morning,
It’s Sunday, into week oh I’ve lost count of how long this issue has been going on for, and it has happened again with one person on the server watching Live TV at 09:15am. My 3 year old Son, all I heard was “Oh No Daddy, not 'gain!”
I’ve done all I can, but it seems Plex is now getting to a stage as I said it’s getting unusable to a degree I’m looking at switching. The logs show once again a Write Error on the USB device, something no one else could see… makes me wonder if Plex have qualified log viewers to work for them, I found the error with my trusty Text to Speech Engine as I’m registered blind, but I swear all I can hear in my head at the moment is log reader going through the logs in my sleep!!

I’m not aiming this at just one Team Member of Plex, I’m aiming it at all those who just feel it’s better to think of adding new items to a platform that has issues to be fixed first before adding things…

I’m done moaning, I just hope it gets fixed sooner rather than later and you guys don’t start losing users to another product…

Dave

LiveTVError-0915041118
LiveTVError-0915041118943×530 93.7 KB

73

@sa2000 Just to let you know, I spent a couple of hours yesterday evening formatting and re-installing Ubuntu and Plex onto the Dedicated i5-3330 PC that we use for streaming around the home and within 30 mins of my son watching a different channel to his usual one, it came up with “Playback Error!” once again, and as I said this is a clean install!

Here’s what the Tuner logs say again…

Nov 05, 2018 10:30:15.918 [0x7fe51ccb8700] WARN - [E] http_streamer_t: http write error
Nov 05, 2018 10:30:15.918 [0x7fe514ff9700] INFO - [I] http_streamer_t::send_thread_func: removing http client
Nov 05, 2018 10:30:15.918 [0x7fe514ff9700] INFO - [I] http_streamer_t::send_thread_func: all clients are deleted. Setting exit flag
Nov 05, 2018 10:30:15.924 [0x7fe4edffb700] INFO - [I] streamer_container_t::control_thread. Removed disconnected streamer deadae8a-6b70-4c4f-97ca-f2647a89454a
Nov 05, 2018 10:30:15.924 [0x7fe4edffb700] INFO - [I] streamer_container_t::delete_streamer. Last streamer was deleted. Stop program streamer
Nov 05, 2018 10:30:15.924 [0x7fe4edffb700] INFO - [I] dvb_program_streamer_t::stop. Stoping program streamer for channel triplet://9018:4222:4672
Nov 05, 2018 10:30:15.925 [0x7fe4edffb700] INFO - [I] transponder_streamer::stop_channel. Stop request for channel triplet://9018:4222:4672
Nov 05, 2018 10:30:15.942 [0x7fe4eeffd700] INFO - [I] CTVSStreamSource::RemoveAllPids. Removing PIDs for client triplet://9018:4222:4672
Nov 05, 2018 10:30:15.942 [0x7fe4edffb700] INFO - [I] transponder_streamer::start_idle_timer
Nov 05, 2018 10:30:15.950 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 0
Nov 05, 2018 10:30:15.958 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 1
Nov 05, 2018 10:30:15.966 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 16
Nov 05, 2018 10:30:15.974 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 17
Nov 05, 2018 10:30:15.982 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 18
Nov 05, 2018 10:30:15.990 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 401
Nov 05, 2018 10:30:15.998 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 402
Nov 05, 2018 10:30:16.006 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 405
Nov 05, 2018 10:30:16.014 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 406
Nov 05, 2018 10:30:16.022 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 800
Nov 05, 2018 10:30:16.030 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 7103
Nov 05, 2018 10:30:16.038 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 7104
Nov 05, 2018 10:30:16.046 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 7201
Nov 05, 2018 10:30:16.056 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 7211
Nov 05, 2018 10:30:16.067 [0x7fe4ecff9700] INFO - [I] tuner 0, demux 0. Deleting PID 8191
Nov 05, 2018 10:30:18.763 [0x7fe51ecbc700] INFO - [I] device_manager_t::idle_timer_func. Stream container for channel triplet://9018:4222:4672 on device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Deleting it.
Nov 05, 2018 10:30:25.595 [0x7fe4ee7fc700] INFO - [I] Stopping graph
Nov 05, 2018 10:30:25.607 [0x7fe4eeffd700] INFO - [I] Stop device request for tuner 0, frontend 0
Nov 05, 2018 10:30:25.613 [0x7fe4ecff9700] INFO - [I] Exiting streaming thread for tuner 0, frontend 0
Nov 05, 2018 10:30:28.783 [0x7fe51ecbc700] INFO - [I] device_manager_t::idle_timer_func. Device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb3/3-1/3-1.1/3-1.1:1.0:0 is idle. Unloading it.
Nov 05, 2018 10:30:28.784 [0x7fe51ecbc700] INFO - [I] transponder_streamer::stop_idle_timer
Nov 05, 2018 10:30:28.784 [0x7fe51ecbc700] INFO - [I] CTVSStreamSource::Term. Waiting for streaming thread to stop
Nov 05, 2018 10:30:28.819 [0x7fe4eeffd700] INFO - [I] Stop device request for tuner 65535, frontend 0
Nov 05, 2018 10:30:28.819 [0x7fe51ecbc700] INFO - [I] CTVSStreamSource::Term. Streaming is stopped
Nov 05, 2018 10:30:28.819 [0x7fe51ecbc700] INFO - [I] CTVSStreamSource::Term. Stream source is stopped
Nov 05, 2018 10:30:29.614 [0x7fe4ee7fc700] INFO - [I] transponder_streamer::idle_thread_func finished

Why would it keep doing this? As I have now confirmed that it wasn’t the install I had before I formatted, this needs to be addressed…

Dave

74

You mentioned before that you believe the issue as being someone else starts to access livetv or end a session when another session gets failed. Are we still with that or moved to a more general unspecific playback errors

Also having snippets of logs are no good to me,. I can only investigate problems when the full logs zip is attached and the indication as to what time the error was and for what

I will get back to your problem hopefully later today

75

Hi @sa2000
There was no one else on the fresh server this time, it happens with a recording in progress while we’re watching on the same USB receiver, or when another user switches channels or for some reason as I’ve shown in my last log snippet, it just drops with one watching after a period of time.
I’m doing further tests here, I know I’ve got the server set to record at 1400 for my 3 year old son.
Oh one thing I’ve noticed is that it doesn’t drop on the server, but only on remote PC’s and devices, hope this helps with the investigation?

It also seems that @adoteq is having a similar issue to, is there something with the remote/network devices?

Dave

76

I cannot make any comments without investigating issues through full logs

I intend to go back to your original logs later tonight
If you have any more logs I would not mind looking

77

@sa2000 Just thought I’d let you know that I’ve installed Plex Media Player on it Ubuntu laptop which along with the other remote PC’s that have the “Playback Error” using Plex through the browser, and as if by magic the issue of when once recording or user is using the other receiver and stopping it, after 2 hours of cartoons being recorded at 3pm the receiver my 3 year old son was using to watch another channel didn’t drop.
This tells me that Transcoding through Chrome and Firefox is a issue. I’ve installed the latest daily build of PMP on Ubuntu 18.04LTS and noticed it wasn’t transcoding it was natively playing unlike Chrome and Firefox.
Thought I’d let you know my findings here…

Look forward to seeing what you think also…

Dave

78

Have been looking at the logs from the 1st November and trying to match your statement to the logs to see where it is going wrong

There was a Plex Web Chrome session on computer with IP address 192.168.0.19 that was viewing Live TV on channel 231. This started before the time that is in the logs (before 17:03)

There were two scheduled recordings that appear to have completed successfully:

At 18:00 scheduled recording for channel 207 started for PJ Masks (2015) - 2018-11-01 18 00 00 - Catboy's Butterfly Brigade -
This was scheduled to record until 18:16

At 18:15 scheduled recording for channel 207 started for PJ Masks (2015) - 2018-11-01 18 15 00 - Owlette the Winner
This was scheduled to record until 18:31

At 18:16 the recording for the first PJ Masks episode completed ok

At 18:16 chapter thumbnnail generation transcoder job started for the PJ Masks 18:00 episode and completed ok at 18:16:52

At 18:31:01 the 2nd recording completed

You said

when it got to the end of the last recording it through "Playback Error"on my Laptop on 231 at 18:00

I cannot see any error in the server log. The last recording finished at 18:31 and not 18:00 - so not sure what you mean here. In fact it was 18:00 when the first recording was started and this completed at 18:16. The 2nd recording started at 18:15 and finished at 18:31

Was it 18:00 ? screenshot with the time and url would have helped

This shows the build up of load on the server
image

If it did not clear itself without a restart, then it may have been a deadlock

And this shows the whole period covered by the logs
image

I can see that the server load level got high with number of queued requests at a very high level of 100. May be that is a factor and there was a timeout in Plex Web rather than an actual error. But the climb in queued requests did not really start till after 18:04

The real build up and slow requests started when remote roku 3 started transcode request for theme music. Do you recall this ? could we eliminate the roku3 from the issue being reported here

79

@mw0dcm I would like to start a separate investigation into the roku behaviour

By the time you collected the logs there were 78 outstanding requests

Nov 01, 2018 18:16:50.557 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57446 (WAN)] GET /music/:/transcode/universal/start (34 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:17:29.862 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57455 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00002.ts (42 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:17:31.780 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57456 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00003.ts (43 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:17:33.855 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57457 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00004.ts (43 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:17:37.340 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57460 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00006.ts (42 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:17:46.985 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57465 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00011.ts (40 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:02.310 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57474 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00019.ts (37 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:04.641 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57475 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00020.ts (38 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:09.700 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57478 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00023.ts (38 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:15.904 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57481 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00026.ts (41 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:23.904 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57485 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00030.ts (43 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:30.863 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57489 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00033.ts (45 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:34.223 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57490 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00034.ts (45 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:38.844 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57491 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00035.ts (44 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:44.777 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57492 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00036.ts (45 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:51.219 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57493 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00037.ts (45 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:18:58.164 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57494 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00038.ts (47 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:05.076 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57495 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00039.ts (47 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:12.291 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57496 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00040.ts (49 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:19.441 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57498 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00041.ts (47 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:25.671 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57499 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00042.ts (50 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:33.922 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57500 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00043.ts (50 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:42.064 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57501 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00044.ts (49 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:48.926 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57503 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00045.ts (51 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:19:56.169 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57504 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00046.ts (53 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:14.174 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57506 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00048.ts (54 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:20.945 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57508 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00049.ts (54 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:29.182 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57509 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00050.ts (57 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:38.921 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57510 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00051.ts (57 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:46.469 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57511 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00052.ts (56 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:20:56.523 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57513 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00053.ts (59 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:07.327 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57514 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00054.ts (62 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:14.568 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57515 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00055.ts (62 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:22.200 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57517 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00056.ts (61 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:28.432 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57518 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00057.ts (62 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:38.250 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57519 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00058.ts (65 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:45.959 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57520 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00059.ts (66 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:21:55.125 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57522 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00060.ts (66 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:04.169 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57523 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00061.ts (69 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:13.418 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57524 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00062.ts (66 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:24.740 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57526 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00063.ts (68 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:33.762 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57527 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00064.ts (72 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:42.491 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57529 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00065.ts (71 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:22:52.349 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57530 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00066.ts (71 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:04.307 [0x7f1653ff4700] DEBUG - Request: [86.150.xxx.xxx:57531 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00067.ts (72 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:15.929 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57532 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00068.ts (74 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:27.854 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57533 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00069.ts (73 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:36.005 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57535 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00070.ts (73 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:49.072 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57536 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00071.ts (76 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:23:59.020 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57538 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00072.ts (78 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:24:09.672 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57539 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00073.ts (74 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:24:17.615 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57540 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00074.ts (76 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:24:32.576 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57542 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00075.ts (78 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:24:45.130 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57543 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00076.ts (79 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:24:55.476 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57544 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00077.ts (83 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:25:04.220 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57546 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00078.ts (82 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:25:20.188 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57547 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00079.ts (80 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:25:36.992 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57549 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00080.ts (83 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:25:51.157 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57550 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00081.ts (87 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:26:02.611 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57551 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00082.ts (84 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:26:19.073 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57553 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00083.ts (85 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:26:35.941 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57554 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00084.ts (88 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:26:49.002 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57556 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00085.ts (90 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:27:02.761 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57557 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00086.ts (89 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:27:19.234 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57559 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00087.ts (91 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:27:35.898 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57560 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00088.ts (91 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:27:47.249 [0x7f16aabfe700] DEBUG - Request: [86.150.xxx.xxx:57562 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00089.ts (91 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:28:03.014 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57563 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00090.ts (91 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:28:30.955 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57566 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00092.ts (93 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:28:42.200 [0x7f169d7ff700] DEBUG - Request: [86.150.xxx.xxx:57569 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00093.ts (97 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:28:59.135 [0x7f16647fc700] DEBUG - Request: [86.150.xxx.xxx:57570 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00094.ts (97 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:29:15.518 [0x7f1656ffa700] DEBUG - Request: [86.150.xxx.xxx:57572 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00095.ts (94 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:29:29.801 [0x7f16a3bfd700] DEBUG - Request: [86.150.xxx.xxx:57573 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00096.ts (97 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:29:52.405 [0x7f16637fa700] DEBUG - Request: [86.150.xxx.xxx:57575 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00097.ts (98 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:30:09.939 [0x7f16577fb700] DEBUG - Request: [86.150.xxx.xxx:57576 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00098.ts (107 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:30:27.786 [0x7f16587fd700] DEBUG - Request: [86.150.xxx.xxx:57578 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00099.ts (110 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:30:47.168 [0x7f16527f1700] DEBUG - Request: [86.150.xxx.xxx:57580 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00100.ts (98 live) TLS Signed-in Token (Dad)
Nov 01, 2018 18:30:47.409 [0x7f1652ff2700] DEBUG - Request: [86.150.xxx.xxx:57586 (WAN)] GET /video/:/transcode/universal/session/8e920676d52be0f7bc880bd6a882df8f/base/00100.ts (100 live) TLS Signed-in Token (Dad)

If this is repeatable - it started when Theme Music was to be played on the roku 3 - would like logs and also /connections list to show the queue of the requests and the state we are in for each

Please raise a separate topic for the investigation and put a link to it here

To get the connections list, you need to find the server security token string as that needs to be appended to the request url
To find out what it is, see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/

Then after starting theme music playback - preferably same one that caused the issue before - it took 15 minutes for the queue to reach 100 - so suggest waiting similar time, then in browser get the connections list
http://192.168.0.3:32400/connections?X-Plex-Token=xxxxxxxxxxxxxx and replacing the xxxxxxxxxxxx with the security token string

Copy the displayed response into a text file and save
and download the logs and info on version of the roku app and firmware level

If this captures it and the same issue is seen, i would like repeat with verbose logging in the server

When we know it is easily reproducible then can also look into getting roku app log as well

80

Hi @sa2000 I shall do this this evening when all has calmed down here, and I’ll follow your instructions as best as I can. We have had the issue without my Dad who is over 130 miles away that connects to the server, happen yesterday when my ex-wife was tuned to a channel and after a length of time it came up with a Playback Error, but since moving all the Linux based PC’s to Plex Media Player the issue has disappeared, so it’s a strange one that happens with the browser and not PMP, and only affects Live TV and not the media on my Hard Drives.

The issue happens on all PC’s using the browser to, including my Laptop connected to the home network through WiFi, which I wouldn’t expect.

Cheers,

Dave

81

I could not find any errors at 18:00
There may be several issues here.
The server was not in a healthy state after 15 minutes of roku requests - 18:15 to 18:30