PMS for Mac 1.28.2.6151 has crashed multiple times,
AND
at ~1:05am – 1:06am PT cut off scheduled recording of OTA Live TV shows (eg, recorded only 28 minutes of 1-hour The Late Show with James Cordon scheduled to air 12:37am – 1:37am; recorded on 66 minutes of 1.5-hour The Carpenters: Close to You (My Music Presents) scheduled to air 12:00am – 1:30am)
AND
began only recording 30second – 2minutes fragments of every scheduled show,
AND
falsely claims to have successfully recorded such scheduled shows.
.
I will try reverting back to 1.28.1.6104.
What a pain in the rear.
Why aren’t there publicly posted detailed version release note histories like most mature software so that users have some hint about version regression?
Sorry to hear this is such a headache especially after you’ve been trying so hard yet we seemingly are stranded on mac island while everyone else is off watching shows.
You asked with understandable concern for a detailed Change Log. There’s a shortlist of fixes with each Plex Media Server release. For example the latest Server beta from today fixes a crash overnight with Clean Bundles.
I realize it’s hard. So I asked for the most common tool, your logs, to see why it’s crashing.
After that next comes a Plex Dance because media assimilation into Plex can abort when there’s a crash, leaving some weirdness with an episode like The Late Show With Stephen Colbert (2015) - S08E15
When there’s cruft associated with a file, upgrading or downgrading would not fix metadata weirdness. The cruft can be caused by a crash or a weird broadcast or unexpected fault. If cruft exists, the solution is to Plex Dance the affected episodes, if not the whole season 08.
I trust what you said at first, that previous versions ran smoothly.
Generally what we do is get you on one of those versions and then locate any remaining issue in your logs and fix it when the common opinion that a certain PMS version works on your hardware. There are many older versions listed on mac filehorse.
When you use words like corruption, you’re using a technical term with respect to Plex because the server runs a massive SQL database. When it gets corruption that’s logged with SQLITE entries in
Without logs I’m out of suggestions besides move your server aside and build a test server until it fails like I do or plex dance every series that’s giving you problems. I personally don’t care about losing watched states because I’ve watched 99% of my stuff.
Hi again. TGIF huh? I got the logs you sent by PM. It’s better to post your logs in the thread here because I’m not an employee.
The first error that stuck out seems big, and I’ve not seen it before even though it sounds easy to cause. In your various Plex Media Server.log files it says
Oct 28, 2022 04:31:09.847 [0x70000ef65000] ERROR - Illegal whitelist covers multiple WAN IPs
Maybe if you screenshot your Settings → General → Network (Show Advanced) so we can see
LAN Networks
Custom server access URLs
List of IP addresses and networks that are allowed without auth
Getting an error with networking could lead to the Live TV errors shown in your logs.
Do you ever Empty Trash, Clean Bundles, and Optimize the DB? I’m seeing a lot of slow queries.
Some repeated errors look like these
Oct 27, 2022 22:30:12.986 [0x700008c2e000] WARN - Subscription: No container available for /tv.plex.providers.epg.cloud:2/metadata/plex%3A%2F%2Fepisode%2F62b91a55db5562779901de06
Oct 27, 2022 22:30:12.987 [0x700008c2e000] ERROR - Subscription: Error refreshing sub: No container found
Oct 27, 2022 22:30:12.994 [0x700008c2e000] ERROR - downloadContainer: expected MediaContainer element, found html
My PMS for Mac Settings (except to temporarily enable debug logging) and LAN configurationhave not changed since original install, so I am skeptical of networking issues, but one never knows.
My Settings > Network > Custom server access URLs field is now and always has been blank.
My Settings > Network > LAN Networks & List of IP addresses and networks that are allowed without auth fields are now and have always been identical: 10.0.0.0/8,{public static IPv4}/24.
(I didn’t notice the forum software didn’t like greater-than & less-than characters—sorry.}
(My routable {public static IPv4}/24 does not overlap with its Internet backbone provider WAN IPv4 /32.)
Both the PMS host Mac and the HDHomeRun tuner effectively have static IPv4 addresses by way of DHCP MAC IPv4 reservations in 10.0.0.0/8, and are both on the same LAN physical Ethernet segment and in the same LAN logical subnet.
(I don’t know that it is significant, but today (and I think previously) I noticed a PMS log error referencing 184.105.148.113 (in Hurricane Electric’s /15 IPv4 allocation) being non-responsive. My firewall has never blocked, nor throttled 184.105.148.113. Nevertheless, I added an explicit firewall hole for 184.105.148.113 today.)
.
No, not manually within Plex, as I don’t know what these functions do.
Using Finder, I have emptied the PMS host Mac Trash twice in the last month after examining the Trash contents.
For what it’s worth, the PMS crashes and failures to record scheduled OTA Live TV shows have occurred around or after 1:00am PT.
PMS does not crash every day.
My wife uses Plex via the Plex for Apple TV app 5 – 12 hours daily. (Several times monthly, I typically only watch a few minutes of Colbert, et al, from finished recordings or recordings in progress using the Plex for iPadOS app.) When she is watching OTA Live TV late night talk shows (eg, Colbert, Kimmel or Fallon, all scheduled to record), she sometimes switches between shows. The next-to-last PMS failure to records shows and then subsequent crash occurred, apparently, while she was watching Colbert, but she does not remember switching shows.
My wife recently told me that the Plex for Apple TV app regularly eventually becomes non-responsive while watching late night talk shows, getting stuck with a spinning pinwheel, whereupon she exits the Plex for Apple TV app and instead begins using the HDHomeRun Apple TV app to watch live TV. (She has found Plex to be so unreliable that she no longer thinks it noteworthy to mention to me.)
Again, though, PMS for Mac had never crashed until after I installed 1.29. Prior to 1.29, the only times I had to restart PMS was after manually quitting PMS, then launching a new PMS version.
(I didn’t notice the forum software didn’t like greater-than & less-than characters surrounding a text string when I replied—sorry.}
It’s not a huge deal but when you reply with computer output or code to place that into a code block (there’s a button that looks like </> in the reply editor). You can also type backticks to make code blocks.
How to use backticks ` to make code blocks
To make a one-liner: pscan --analyze-deeply --item 42 you surround it with backticks like below
`pscan --analyze-deeply --item 42`
To make a multi-line you put 3 backticks above and below it, which looks like ```
for example what I typed below would make what’s below that.
I don’t know the rules, but the error message says
ERROR - Illegal whitelist covers multiple WAN IPs
and I can only imagine it’s complaining that you’ve whitelisted a whole WAN subnet.
Is it being more strict now or is this an actual problem? I don’t know but it can’t be good.
So would it be possible for you to use one address out there like the following?
Nibbles, I appreciate your many postings—thank you. Please do not think I’m being snarky by pointing out that LAN and WAN are acronyms for different terms.
.
Neither the 10.0.0.0/8, nor my public static routable /24 LAN (Local Area Network) networks overlap with either of my WAN (Wide Area Network) IP’s.
10.0.0.0/8 is private and cannot overlap with any public IP. (WAN IP’s are likely to be intrinsically public.)
My public static /24 IPv4 block does not overlap with the server’s primary WAN dynamic IP (for a telco 200Mbps/200Mbps fiber dynamic IP circuit), nor, if the server’s primary Internet connection (ie, associated with that telco fiber dynamic IP circuit) failed, would overlap with the WAN static IP for the fail-over routing of my public static /24 IPv4 block (for a backbone provider 1Mbps/5Mbps DSL static IP circuit).
.
Settings > Network > LAN Networks UI “definition”:
Comma separated list of IP addresses or IP/netmask entries for networks that will be considered to be on the local network when enforcing bandwidth restrictions. If set, all other IP addresses will be considered to be on the external network and will be subject to external network bandwidth restrictions. If left blank, only the server’s subnet is considered to be on the local network.
.
Settings > Network > List of IP addresses and networks that are allowed without auth UI “definition”:
Comma separated list of IP addresses or IP/netmask entries for networks that are allowed to access Plex Media Server without logging in. When the server is signed out and this value is set, only localhost and addresses on this list will be allowed.
.
There is another Network setting that is enabled (but may not need to be):
Settings > Network > Treat WAN IP As LAN Bandwidth UI “definition”:
Treat incoming requests from this network’s WAN IP address as LAN requests in terms of bandwidth. This often occurs when DNS rebinding protection is in place and clients on the LAN cannot contact the server directly but instead have to go through the WAN IP address.
.
My LAN has some hosts & devices with private IP’s, and some hosts with public IP’s. (Until a few years ago, for the previous 20 years or so, all hosts & devices on my LAN had static public IP’s.) It would be a very surprising design error if Plex was incompatible with a public static IP LAN.
.
.
Regardless, all three Network fields have always been exactly the same as now since original Q1_2022 PMS installation, and that no PMS version prior to 1.29 crashed, so the error seems like a red-herring. I could temporarily remove my public static /24 CIDR, but with crashes and recording failure being intermittent, minimizing configuration changes would be prudent.
28 Oct 2022, I reverted back to PMS for Mac version 1.27.2.5929 after 1.28.1.6104 crashed.
It’s important to note that Plex will consider every IP not part of 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 as WAN. Even if it IS under your personal control and can be used as LAN, effectively.
Just to clarify - We do not allow whitelisting of WAN IP addresses
Well - it is allowed but any wan ip address specified to not require authentication is ignored
Only LAN addresses allowed within the strict definition of Private IPv4 Address range as mentioned by @Holger-Kuehn
None of my LAN segments have IP addresses overlapping either of my two WAN IP addresses.
.
Huh?
Are you saying that only Private IPv4 addresses are respected in the not-require-authentication field(s)?
In other words, are all public IP addresses in the not-require-authentication file(s) ignored?
If so, that would be a bizarre architecture error. Until recently, for ~20 years, my LAN had no hosts with private IP addresses—all of my LAN hosts (and devices) had publicroutable IP addresses: Macs, iPhones, iPads, printers and scanners. Some, as I’ve written above still do.
.
.
.
Nevertheless, this questionable log file error message is a red-herring.
There appear to be very serious bugs in PMS 1.29.
For the first time since I installed PMS in March, version 1.29 crashed. Further, it seems to have persistently corrupted my library and or PMS host files. Even having successively reverting back to PMS 1.28.1.6104, even though PMS 1.28.1.6104 has not crashed since being re-installed 27 October, Plex player applications are served bad links to recorded shows.
For example, yesterday, Saturday 12 November, PMS correctly recorded the OTA airing of SNL S48E06 (a new airing) and also an airing of a SNL rerun (being set to record both new and repeat airings).
The filename PMS assigned to the new airing (ie, not rerun) recording is:
Saturday Night Live (1975) - S48E06 - Saturday Night Live.ts
The filename PMS assigned to the rerun recording is:
Saturday Night Live (1975) - 2022-11-12 04 00 00 - Kieran Culkin; Ed Sheeran.ts
PMS wrote both file into the Season 48 directory.
When I tried to play the new S48E06 on my iPad (and Mac) by tapping (clicking) upon the S48E06 thumbnail, Plex played the rerun, even though (as I wrote above) the Get Info source path explicitly listed the new S48E06 file.
All this discussion regarding the whitelist log entry seems to be a completely irrelevant. (I have not yet tried to run Plex on one of my Macs having public addresses, although I did count on eventually so doing later.)
My library isn’t FUBAR, but my wife has yet another Plex annoyance . . . which is, of course, my fault.
The difference in filenames for the recordings is due to the season / episode number not being available in the EPG data at the time for the earlier recording - this could be to interim data provided by Gracenote and updated later on - We do have an issue that is being corrected where updates to EPG metadata for already scheduled recordings are not picked up until the Plex Media Server is restarted.
If this continues to happen, I suggest raising it as per the advice given on this Live TV and DVR pinned forum topic Reporting Plex DVR Lineup Inaccuracies - Live TV & DVR - Plex Forum and for the Plex for iOS mentioned playback issue, also including the Plex for iOS logs and zipped media info xml from the Plex Web Get Info and debug server logs.
Yes - All access to the server from public IP addresses must be authenticated. This has been the case for a long time
Are there any debug server logs captured after a 1.29 PMS crash?
Could you expand on this ? Which hosts files? What corruption
Sorry I have not gone through the whole forum thread - please point me to specific posts
I understand the file naming. I listed the names only to identify the recordings mentioned in my example.
.
.
One of the very serious PMS 1.29 apparent Library corruption bugs is illustrated in my previous posting example. When one attempts to play the new airing recording (Saturday Night Live (1975) - S48E06 - Saturday Night Live.ts) all my Plex players play the wrong show, Saturday Night Live (1975) - 2022-11-12 04 00 00 - Kieran Culkin; Ed Sheeran.ts, the rerun.
This bug has occurred many times, all beginning with installing PMS 1.29.
The Get Info > Media Info > Files lists the S48E06 correct file path, but when I attempt to play S48E06, S48E06 is not correctly played:
(Again), if I make no PMS host file changes, the rerun (ie, wrong) file is played.
If I move the PMS for Mac host rerun file (ie, the wrong recording) to a different directory, the rerun (ie, wrong) episode is played, even though PMS reports successful rescanning of those directories.
If I delete the PMS for Mac host rerun file (ie, the “wrong” recording file) and empty the PMS for Mac host Trash, the iOS, iPadOS and Apple TV apps all fail attempting to play the rerun (ie, wrong) file, even though PMS reports successful rescanning of those PMS host directories. Using Plex for Mac player app, if I attempt to play S48E06, an error message is posted:
Clicking upon Retry results in the error repeating. However, if I click upon Skip (what is to be skipped is not evident to me), S48E06 is correctly played. This error is presented 100% of times Mac Plex player attempts to play S48E06.
After partially playing S48E06 as above using Mac Plex, I then attempt to play using the iPadOS Plex app, I am offered to resume where I exited playing using Mac Plex. Nevertheless, iPadOS Plex still fails playing S48E06 as it explicitly still is trying to play the deleted rerun (wrong) file.
No housekeeping actions I’ve tried results in S48E06 being correctly played using any of my Plex player apps.
