Server Version 1.25.6.5577:
Player Version#:1.41.0.2876-e960c9ca Plex For Windows
PlexErrorTV.txt (17.5 KB)
Live TV & DVR no longer works after updating Plex.
Doesn’t matter what channel, always gives Code 5000, unable to tune to channel.
Trying to analyze based on a log snippet isn’t always a good thing, but from what you provided this is the significant line:
Mar 14, 2022 14:50:34.497 [0x7f479f7c5b38] DEBUG - [Grabber/5fc76b343f000e002d0c7096-5fc705eac8d56d002e06f5f1-l4m2x70gwv8uprxfcbetttnn] Grabber: Signal information for tune on channel 5fc76b343f000e002d0c7096-5fc705eac8d56d002e06f5f1: strength: 0, quality: 0
Signal strength: 0 Quality: 0 is being returned by your Plex Tuner Service as the result from your tuner.
Are you able to tune using your WinTV-quad outside of Plex? Can you verify that your antennae is still connected? I’d say rescan channels to see if the channel has been repacked to another frequency, but since you say this is happening for all channels that seems unlikely.
This seems to be a known issue, and they are working on it.
You say this is a Windows computer. Try restarting your computer, see if that fixes it. If you can, you can also try restarting the plexmediaserver process, which will fix it temporarily on a Linux server. I make no guarantees on anything Micro$oft produces, though. =)
It could be, though I don’t think we can be certain based on the log snippet posted. According to sa2000 the issue in the other thread that manifests with a “(Failed to connect to 127.0.0.1 port 32600: Connection refused)”, which isn’t in what has been provided so far. I do see http 200 responses on port 32600 from what was posted in this thread.
@jmchoo : All of the recommendations are good to try… and see if you see the connection refused in your logs.
“(Failed to connect to 127.0.0.1 port 32600: Connection refused)”
This is basically a networking error inside the host operating system. 127.0.0.1 is by common agreement the network address of “this” computer. My own address, so to speak. There are 65,535 ports on a computer.
When a computer wants to talk to another computer or itself, it sends the traffic to the IP address of the destination computer on the port number that type of traffic uses, Port 80 for HTTP, 443 for HTTPS, 22 for SSH, 20/21 for FTP and so on. If there is an active process or program running on the destination computer that is listening, they get together and talk their brains out.
The “connection refused” error is the sending computer saying that it can get to the destination, but nothing is listening for it on that port. The lights are burning bright but nobody’s home. This could possibly be firewalling, but it’s hard to imagine many people screwing the firewall up so bad that 127.0.0.1 can’t connect to 127.0.0.1
Anyhow, the theory as I understand it is something in the Plex Tuner Service program is crashing it; (segmentation fault under Linux, no idea what it reports in Windows), and when the program crashes, it doesn’t release port 32600. The overall Plex software seems to be smart enough to restart the crashed sub-program, but since the “dead” instance hasn’t released the required port, the new process can’t connect. Plex can’t communicate with it’s tuner. Game over.
Under Linux, you can restart the plex server & all of it’s sub-programs with one command; this resets everything related to Plex, including the port. So it works again, till the next crash. A.F.A.I.K, no one knows exactly what causes the crash or how to trigger it.
Without having a Plex server on a Windows machine, I am not so sure there is a way to restart it and all of the sub-processes, so the best suggestion I have for a Windows server is to reboot the thing.
They are working on this.
Yep, and the thing is that in the original posted log snippet the tuner service isn’t refusing connections on port 32600, which is the port used by the Plex Tuner Service. It is actually responding to the get requests with a http 200, which is success/ok. (Note the GET request to port 32600 on the loopback adapter, and the http 200 response 0.7 seconds later. It also provided info that the tuner signal strength/quality for that channel is 0, which is interesting.)
Mar 14, 2022 14:50:33.838 [0x7f479f7c5b38] DEBUG - [Grabber/5fc76b343f000e002d0c7096-5fc705eac8d56d002e06f5f1-l4m2x70gwv8uprxfcbetttnn] HTTP requesting GET http://127.0.0.1:32600/devices/compound_device093dvb%23v4l%23%2fsys%2fdevices%2fpci0000%3a00%2f0000%3a00%3a0a.0%2f0000%3a04%3a00.0%2f0000%3a05%3a02.0%2f0000%3a07%3a00.0%3a14f1%3a8880
Mar 14, 2022 14:50:34.497 [0x7f47a0618b38] DEBUG - [HttpClient] HTTP/1.1 (0.7s) 200 response from GET http://127.0.0.1:32600/devices/compound_device093dvb%23v4l%23%2fsys%2fdevices%2fpci0000%3a00%2f0000%3a00%3a0a.0%2f0000%3a04%3a00.0%2f0000%3a05%3a02.0%2f0000%3a07%3a00.0%3a14f1%3a8880 (reused)
Mar 14, 2022 14:50:34.497 [0x7f479f7c5b38] DEBUG - [Grabber/5fc76b343f000e002d0c7096-5fc705eac8d56d002e06f5f1-l4m2x70gwv8uprxfcbetttnn] Grabber: Signal information for tune on channel 5fc76b343f000e002d0c7096-5fc705eac8d56d002e06f5f1: strength: 0, quality: 0
Port 32600 is for communications with the tuner service, not how the tuner service communicates with the tuner itself.
Let’s let the OP try the feedback we’ve provided as it all has the potential to help them.
I’ve checked the antenna and reseated the tuner card, cleared out the channels and rescanned. These are the ones that were detected by Plex.
What software for linux can also use the Happauge card that’s recommended?
I’ve tried restarting the Plex service in Linux multiple times and also tried watching from TVs Phones and web, all have the same error.
“TranscodeSession: timed out waiting to find duration for live session”
This is the error causing the stream to fail. My suggestion is to stop using the Windows app and use a Roku instead.
There’s multiple problems in Plex for Windows that will likely take another year if not longer to be fixed.
I said in my previous reply that it happens with me using multiple different clients, Firestick TV, IOS, Web, and windows.
Something is wrong with my linux server that has the tuner card.
Every single one of those player apps you listed have horrible Live TV support. Especially the Firestick.
It looks like with your tuner card on linux you would need to install another streaming server (e.g. tvheadend), which I wouldn’t recommend. My apologies - I’ve got a different tuner where it is easy to test the tuner directly outside of Plex.
Next I’d suggest deleting your codec files. Stop your Plex server process, make a backup of the codec files if you like (it never hurts), delete the codec files (not the directory, just the files), and then start your Plex server process. Plex will automatically download the codecs as it needs them based on the file types played. The codec files are stored under the Plex data directory (see this link if you don’t know where that is), under the “Codecs” directory. In “Codecs” is another directory that for me was named with a uniqueidentifier-OS-processorclass name. It is this uniqueidentifier-OS-processorclass directory from which you want to delete all the files while the Plex server process is stopped. Since you are on Linux they will likely be shared library (.so) files.
If that doesn’t work, would you recreate the issue and post the full debug level plex log zip package? It would be useful to see if the tell-tell connection refused message is anywhere (or the unable to allocate port message) indicating the bug @Annoyed pointed out, or if something else is going on.
Hauppage does offer a custom kernel package for their cards, but at least for a PCIe card, they’re not needed, When I first bought the card back in 2018? I think it was, I just put the card in, and the standard kernel saw it and everything was happy.
When it became time to upgrade the machine from 16.04 to 20.04, before doing that, I installed the Hauppage kernel, and it made no difference in how the tuner card worked. It also started leaving errors in dmesg (a boot process log) regarding some media drivers being outdated/experimental, and it also seems that the custom kernel doesn’t get updated as often as the standard kernel.
At this time, I’m using 20.04.3 LTS with HWE enabled. Aside from the crashing issue, which the Hauppage kernel did NOT fix, it works fine. As far as I can tell, under Linux, with the PCIe card at least, you do not need to install custom drivers or anything else.
1 Like
Thanks for the insight.
I tried deleting the Codecs but that didn’t fix it.
Here is the Log Zip
Plex Media Server Logs_2022-03-15_10-35-29.zip (5.4 MB)
Do you know when exactly this issue began? I know you said after upgrading Plex, but the oldest Plex Media Server log only goes back to March 11 at 05:13:00, and it appears you were already on 1.25.6.5577 at that point. The oldest tuner service log goes back a bit further, and I do see a case where the tuner service shut down, didn’t release the port, and then gets a failure to allocate port 32600 on the subsequent start:
Mar 10, 2022 22:52:18.298 [0x7f996c1e2848] INFO - [I] web_server_t::start. Starting web server on port 32600
Mar 10, 2022 22:52:18.299 [0x7f996c1e2848] WARN - [E] web_server_t: bind: Address in use
Mar 10, 2022 22:52:18.299 [0x7f996c1e2848] WARN - [E] web_server_t: port 32600 is not available
However, the Plex Tuner Service then starts again about 12 minutes later successfully:
Mar 10, 2022 23:04:11.137 [0x7fc3fb6efb38] INFO - Plex Tuner Service v1.0.0.0 - Ubuntu PC x86_64 - build:
Mar 10, 2022 23:04:11.137 [0x7fc3fb6efb38] INFO - Linux version: 5.4.0-962202022022-generic (#0+mediatree+hauppauge-Ubuntu SMP Thu Feb 17 21:47:47 UTC 2022), language: en-US
Mar 10, 2022 23:04:11.137 [0x7fc3fb6efb38] INFO - Processor AMD FX(tm)-6300 Six-Core Processor
Mar 10, 2022 23:04:11.137 [0x7fc3fb6efb38] INFO - /usr/lib/plexmediaserver/Plex Tuner Service /usr/lib/plexmediaserver/Resources/Tuner/Private /usr/lib/plexmediaserver/Resources/Tuner/Shared 1.25.6.5577-c8bd13540 32600
Mar 10, 2022 23:04:11.136 [0x7fc3fd06a848] INFO - [I] broker_t::start...
Mar 10, 2022 23:04:11.140 [0x7fc3fd06a848] INFO - [I] device_manager_t::init.
Mar 10, 2022 23:04:11.141 [0x7fc3fd06a848] INFO - [I] device_manager_t::init. Initialize provider manager
Mar 10, 2022 23:04:11.141 [0x7fc3fd06a848] INFO - [I] device_manager_t::init. Initialize all device auxes
Mar 10, 2022 23:04:11.141 [0x7fc3fd06a848] INFO - [I] dvb_device_factory_t::get_aux_list
Mar 10, 2022 23:04:11.141 [0x7fc3fd06a848] INFO - [I] tvbutler_aux_t::init
Mar 10, 2022 23:04:11.143 [0x7fc3fd06a848] INFO - [I] web_server_t::start. Starting web server on port 32600
Mar 10, 2022 23:04:18.931 [0x7fc3fadcfb38] INFO - [I] web_service_t::process_device_discovery
Mar 10, 2022 23:04:18.931 [0x7fc3fadcfb38] INFO - [I] device_reactor_t::get_device_list ()
This is what a typical tune for you looks like in the tuner service logs:
Mar 15, 2022 10:34:48.240 [0x7effb1085b38] INFO - [I] Starting tuner 2, frontend 0
Mar 15, 2022 10:34:48.323 [0x7effb1085b38] INFO - [I] tuner 2, frontend 0 was opened successfully
Mar 15, 2022 10:34:48.323 [0x7effb1085b38] INFO - [I] detected tuner ids: vendor (14f1), product (8880)
Mar 15, 2022 10:34:48.324 [0x7effb1085b38] INFO - [I] No ca0 node is present for tuner 2
Mar 15, 2022 10:34:48.324 [0x7effb1085b38] INFO - [I] CTVSStreamSource::TuneTransponder. Transponder tuning request: diseqc 0, freq 31, modulation 0, polarization 0, symbol rate 0, LOF 0, LNB selection signal 0, FEC 0
Mar 15, 2022 10:34:48.324 [0x7effb1085b38] INFO - [I] Tuning request. 31, 0, 0, 0, 0, 0, 0
Mar 15, 2022 10:34:48.827 [0x7effb0e78b38] INFO - [I] Starting streaming thread for tuner 2, frontend 0
Mar 15, 2022 10:34:48.827 [0x7effb1085b38] WARN - [W] CV4lTunersStreamSrc::Start. pthread_setschedparam failed 1
Mar 15, 2022 10:34:48.828 [0x7effb0e78b38] INFO - [I] tuner 2, demux 0. adding PID 20
Mar 15, 2022 10:34:49.080 [0x7effb0f82b38] INFO - [I] transponder_streamer::tune_transponder_impl. Signal stats: 0, 0, 0
Mar 15, 2022 10:34:49.080 [0x7effb0d75b38] INFO - [I] tvs_program_streamer::tuning_thread. Starting tuning thread for program triplet://0:2273:4
Mar 15, 2022 10:34:49.081 [0x7effb0d75b38] INFO - [I] tvs_program_streamer::SetPATScanState. Waiting for PAT...
Mar 15, 2022 10:34:49.081 [0x7effb25a4b38] INFO - [I] web_service_t::process_start_channel. Successfully started channel triplet://0:2273:4 on device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:02.0/0000:07:00.0:0
Mar 15, 2022 10:34:49.086 [0x7effb167bb38] INFO - [I] http_streamer_t::send_thread_func: adding http client
Again, “Signal stats: 0, 0, 0” seems to indicate no signal or some type of issue getting data from your Hauppauge device for that channel (or any other you tried to tune.)
If this were my issue I’d proceed with the following to get more info:
- Do a full reboot of the server where Plex Server is running and then verify if the problem still exists. (I know you restarted Plex, but didn’t see that you had done a full server reboot.)
- Bring a TV into the room where your server is. Disconnect the coax antennae cable from your Hauppauge tuner and connect it to the TV. Verify that the TV can tune channels using the same antennae and cable.
- If neither of the above provides any insight, and the problem began with a Plex Server upgrade, then what was the previous version of Plex Server that you were on? If it was a major jump in Plex Server versions then sometimes that can create unusual issues. If it was only a minor increase in versions then revert to the last known working version of Plex to verify if it resolves the issue. If we can show that an old version works and a new version fails we should be able to get attention on this as a bug.
I hope this helps…
1 Like
Last couple of versions have changed EPG channel matching, at a minimum he should re-scan his channels but more likely delete the DVR to clear everything out and setup again.
1 Like
- Did the reboot
- Installed the card in my windows gaming PC and installed Plex Server for windows 1.25.7.5604. Live TV worked here.
- I’m not sure what version I was on before on Linux 1.25.6.5577. It was pretty close as I update everytime a new one comes out.
I tried deleting my DVR on my Linux install and then readding and scanning, and deleting the Codecs folder with the plex service stopped. Still no dice.
Wow, this is a tough one. At least we know the antennae connection, cable, and tuner card are good. Thank you for verifying.
From your logs you are on Ubuntu 20.04 x64 64 bit. Do you do manual installs of the .deb package for each upgrade? (e.g. download the .deb and issue the commend “dpkg -i plexmediaserver_(version).deb”) If so, do you still have the old .deb packages? If you haven’t manually deleted then they are probably under the Downloads folder of your user home (“cd ~/Downloads” to get there) and you can find and rollback to the previous version just by finding the next-to-newest plexmediaserver*.deb file, and install it just like an upgrade (e.g. “dpkg -i plexmediaserver_(most recent old version).deb”)
If by some luck the rollback works, it would be great to see a full set of logs for a successful tune to compare against the logs of the fails in the .6.5577 version.
Alternately, I see the most recent Plex Server beta has a fix for the port binding issue:
- (DVR) Fix port rebind issue on PTS restart (#12988)
I haven’t tried that version yet (1.25.8.xxxx)
Do you remember if you had to install any drivers for your Hauppauge PCI card when you first set it up on Linux?
1 Like
Sorry for my delay,
I’ve been busy with work.
I do install the updates that way, but unfortunately I wrote a script that just downloads the update to a temp file and then automatically installs it.
Is there a site that you know of that lists the versions? If so I could try to download an older version and try that.
Today I downloaded the new version Linux Plex 1.25.7.5604 and then deleted my DVR and began again, but I still have the same issue. I’ll try to look into installing the beta build 1.25.8.xxxx this weekend
When I got the tuner card I followed the directions from Hauppauge Support | Running WinTV TV tuners and HD PVR 2 under Linux
Here are the packages that sudo apt list | grep hauppauge lists
LinuxDrivers.txt (4.1 KB)
Here are the details of the card in use lspci -v
PCI Device.txt (1.5 KB)
I checked the dmesg sudo dmesg and saw some firmware errors maybe that might be relevant.
Dmesg.txt (5.1 KB)
Thank you again
Found the issue, for some reason around when I updated Plex I also did a linux update. Somehow there was an issue with the Happauge drivers
Ubuntu Forum DVR Issue
The drivers got removed, and redoing the initial setup process for the card fixed it. sudo apt-get install linux-firmware-hauppauge
Afterwards the sudo dmesg gives the following.
[ 4689.999647] si2157 9-0060: Can’t continue without a firmware.
[ 4851.984800] si2157 9-0060: found a ‘Silicon Labs Si2157-A30 ROM 0x50’
[ 4851.984838] si2157 9-0060: downloading firmware from file ‘dvb-tuner-si2157-a30-01.fw’
[ 4853.235385] si2157 9-0060: firmware version: 3.0.5
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
