Interesting, it also started happening for me after I bought Plex Pass, though I switched to a different computer at that time as well.
If anyone here is using either of the Windows clients and your Live TV channel has AAC audio youâre gonna get the tuning error.
If this is happening on some channels but not all this is probably why.
A workaround is to transcode the audio on-the-fly to AC3 before the stream hits Plex but that is out of scope for this thread.
Or force the stream to transcode in Plex by selecting a lower bitrate.
There are actually channels that use AAC audio instead of Dolby Digital?
Everything Iâve seen, since 2001, from OTA has been DD with ATSC 1.0. And more recently AC-4 from ATSC 3.0. And with cable, from FiOS and Comcast, Iâve only seen Dolby Digital as well.
Is there a thread regarding this issue with a server running Linux?
This has been an occasional, ongoing problem for at least 9 months now
Currently running server version 1.25.3.5409
OS is Ubuntu 20.04.3 LTS (GNU/Linux 5.13.0-28-generic x86_64), installed as HWE
Tuner is a PCIe card, Hauppage WinTV-quadHD, Model 1609
I am NOT running Hauppaugeâs custom kernel, as I find it seems to work on the default kernel, and the custom kernel seems to not get updates anywhere near the default kernel. (Previous install of OS was non-HWE, with the custom kernel, and the problem existed then, too) Additionally, dmesg on the old non-hwe custom kernel showed errors about the mediatree code being outdated.
Currently, Ubuntu controls services by systemctl [command] [servicename]
When all is well, systemctl status plexmediaserver shows the tuner service is running under a subheading called CGroup::
/usr/lib/plexmediaserver/Plex Tuner Service /usr/lib/plexmediaserver/Resources/Tuner/Private /usr/lib/plexmediaserver/Resources/Tuner/Shared 1.25.3.5409-f11334058 32600
I experienced this problem today, after having no issues for several weeks. When I checked the server status, I noticed that sub-process was not running. restarting the server process apparently fixed it ( systemctl restart plexmediaserver ); I was able to tune OTA again.
The only thing I did differently was I had connected to the server with a different Roku box after changing itâs internet connection. Normally, I always use a Roku Ultra connected via ethernet in my main TV room. I had connected with a Roku Express in the kitchen. Seemed to work, but when I returned to the main TV, it couldnât access itâs tuner. Something had crashed that sub-process.
Anyone else seeing this under Linux?
I have noticed that the most reliable way to replicate the issue is to switch devices (end the stream on one device and try watching on another). Also using Ubuntu 20.04 with a hauppauge wintv-hvr-955q.
The issue affecting tuning channels on vbox using their xmltv feature and with channel identifiers that has spaces / extended characters has been fixed in Plex Web in the hosted app version 4.75 which was released today
The problem led to tuning errors and server logs showed log entry containing (The device does not tune the required channel)
The hosted web app is accessible through https://app.plex.tv/desktop
This bundled app accessed through the Plex Media Server IP Address will get updated sometime in the future
For anyone who ha this issue - please confirm that it is fixed when using the hosted web app (https://app.plex.tv/desktop) and the Vbox xmltv functionality and let me know if the problem does also need fixing in other Plex client apps
Plex Web Release Notice: Plex Web - #380 by bengeorge
- Fix watching live TV channels with special characters in channel ID
Also getting this issue, quite frequently. Can be reproduced consistently; it works OK the first time I try to watch a channel after the computer resets. If I then try to change the channel or go back and watch something else, I get the error everytime I try to watch ANY channel.
Tuner is a Hauppage WinTV-DualHD 1595.
On Ubuntu 20.04.3 LTS. Plex Media Server is 1.25.6.5545.
Plex Log.txt (342.1 KB)
and debug server logs please as well and indication of time of error
Plex Media Server Logs_2022-02-16_10-42-02.zip (4.7 MB)
10:41am 2-16-2022
My server is Linux, not Windows, but I had the same issue.
As a desperation step, I tried replacing the Hauppage tuner card with a new one, and it hasnât unexpectedly topped working or crashed since installation (Monday, 2/14/2022), so that might have been it. As part of the process, I deleted the DVRâs and recreated them, which was a P.I.T.A. in itâs own right. In order to get it to âforgetâ the channel lists & info, I had to set the band selection to Cable, run a scan, which naturally found 0 channels and then set it back to Antenna & scan again. This got me a mostly accurate set of channels. I had to repeat this for both DVRâs. (Hauppage quad tuners show up as two different DVRâs in Plex.)
Obviously, I canât âproveâ itâs fixed, but I think it might be. Granted, Iâm running Linux, but it might help someone scratching their head over this. Maybe the Hauppage tuners can fail in a way that causes the issue?
I can confirm that my VBox works now via the hosted web app. I tried most of the channels and now i can tune them all.
I hope that the fix will come soon for the android clients and self hosted web apps.
Thank you @sa2000 for the involvement in fixing this issue.
Thank you very much
The issue was due to an earlier failure of the Plex Tuner Service process at Feb 16, 2022 07:50:02
Attempt to relaunch it was successful but the tcp port was not freed up so the Plex Tuner Service could not communicate with Plex Media Server and all subsequent attempts to tune failed
The issue has already been logged with the development team and I will add your new evidence to it - until it is fixed, when this happens restart Plex Media Server
The error manifests itself in the Plex Media Server.log with this text appearing in one of the log lines
(Failed to connect to 127.0.0.1 port 32600: Connection refused)
Also the Plex Tuner Sevrice.log would have this entry
WARN - [E] web_server_t: port 32600 is not available
Seeing the same issue on Nvidia Shield running the PMS 1.25.3.5575 with 9.0.1 and Hotfix 1. Makes recording almost impossible as youâre not sure when it will cut out. Seeing the error messages within the log as well.
Yes - we have had reports of that from Shield users
I have asked the development team for a quick change to put a delay on relaunch of the crashing Plex Tuner Service to avoid the secondary port-in-use error which results in all DVR actions failing afterwards - that would alleviate the impact whilst the crashing issue is looked into
Are you able to update us when this is fixed and what version of PMS has the change? Out of interest, how long do you think this will take because itâs a bit unpredictable as to when this will work or not.
I do not know - but this is the next task to work on for one of the developers
@sa2000 any update on timescales at all? Really hit and miss which doesnât mean a lot of recordings can be done with confidence.
1 Like
We will have a fix for the port in use issue on restart of Plex Tuner Service - that is expected to be released in Plex Media Server 1.25.8 - that should reduce the impact - after that release we will try and see if we can find the repro steps for the crashes
I certainly havenât figured out what the cause is. Iâve replaced the tuner card ( Hauppauge WinTV-quadHD PCI Express TV Tuner Card model 1609) to no avail.
The biggest commonality seems to be when I access the server for either live TV or playback of recorded material from different devices.
All of my viewing is done via Roku devices. Primary is a Roku Ultra, using an ethernet connection, but I occasionally watch from the Kitchen, which is a fairly new (6 Mo. or less) Roku Express which is wireless only.
While it certainly doesnât happen every time I use the Roku Express, switching between that device and the primary seems to be the most reliable way to trigger a failure.
When it does fail, it seems to crash the tuner child process. The parent plexmediaserver process does not crash.
I did find the following error in the logs: (Plex Tuner Service.1.log)
Feb 09, 2022 09:00:49.625 [0x7f4b5695ab38] ERROR - Error. Received SIGSEGV: Segmentation Violation.
Seeing as this thread is tagged for Windows servers, I did start my own thread regarding this, there might be something useful in there.
I will have an alpha build shortly of Plex Media Server 1.25.8 which addresses the issue of the tcp port not being released after a failure of the Plex Tuner Service process. This should reduce the impact of the problem - anyone wants to try this alpha build - please let know what the platform is / binary file required - I donât think I will be able to offer an alpha build for docker or Nvidia Shield
2 Likes
