Absolutely. Attached are tonight’s log files as well as a sample of a file that elicits the playback error. (All 180 episodes of the Seinfeld series present with the same problem.)
I’m also going to need the console logs. Sorry I didn’t think of this earlier.
PMS is showing the socket from it to the client just ‘breaks’ without any reason whatsoever. If there’s something going sideways in transmission, it’s going to badly sideways that it’s not even making it back to the log file.
Nov 24, 2016 19:24:38.514 [0x10ef04000] DEBUG - Content-Length of /Volumes/Drobo3/Television/Seinfeld/Season 8/Seinfeld S08E03.mp4 is 607423656.
Nov 24, 2016 19:24:38.516 [0x10f8ce000] DEBUG - Failed to stream media, client probably disconnected: 32 - Broken pipe
Nov 24, 2016 19:24:38.516 [0x10f8ce000] DEBUG - Completed: [::ffff:127.0.0.1:63938] 200 GET /library/parts/522496/1480033196/file.mp4 (9 live) 12ms 196608 bytes (pipelined: 2)
Nov 24, 2016 19:24:38.557 [0x10f84b000] DEBUG - Failed to stream media, client probably disconnected: 32 - Broken pipe
Nov 24, 2016 19:24:38.558 [0x10f84b000] DEBUG - Completed: [::ffff:127.0.0.1:63939] 200 GET /library/parts/522496/1480033196/file.mp4 (9 live) 46ms 1179648 bytes
Coupled with that, also in the log…
Nov 24, 2016 19:24:12.887 [0x10f8ce000] VERBOSE - We didn't receive any data from ::ffff:192.168.1.23:63815 in time, dropping connection.
Nov 24, 2016 19:24:13.007 [0x10f84b000] VERBOSE - We didn't receive any data from ::ffff:192.168.1.23:63816 in time, dropping connection.
Nov 24, 2016 19:24:13.406 [0x10f8ce000] VERBOSE - We didn't receive any data from ::ffff:192.168.1.23:63814 in time, dropping connection.
Nov 24, 2016 19:24:14.435 [0x10f8ce000] VERBOSE - We didn't receive any data from ::ffff:127.0.0.1:63842 in time, dropping connection.
This is PMS telling us it didn’t get anything back from the client (Safari) and drops it for that reason.
We’ll address the video issue and find out why safari and PMS can’t get along for this. I do suggest you also look at what else is going on with your local clients. Something hogging up the wifi?
Which console logs are needed, the system.log or just PMS logs? Also, not sure about the Wi-Fi—the entire network is hardwired so only iOS devices utilize Wi-Fi. And, aside from these Seinfeld episodes, I didn’t have any problems streaming to my iPad last night.
I’m sorry… Player console logs.
Okay, I’ve reproduced the error again on my iPhone and on the Plex Web Player, using “Seinfeld S08E22” as the test episode. Attached are fresh PMS Logs, Plex Web Player logs, Plex iOS debug logs, and Safari Developer Console logs.
I just did the same test using Fedora with Firefox & chrome with the sample you provided. I am not able to reproduce on anything from 1.1.4 -> 1.3.0
The error in your iOS logs 24-Nov-2016 20:01 are not found in your PMS logs. Probably rolled over due to Verbose logging.
If you can quiesce the server and capture the singular playback , which does show the transcode happening (that’s ok and what I want to see), it would be of great help.
I turned off verbose logging, deleted old logs, and rebooted my PMS machine. Then, I attempted to initiate playback of Seinfeld S08E22 in the Plex Web Player and on my iPhone. Attached are the PMS logs and iOS debug info.
Perfect. Thank you.
Nov 25, 2016 13:14:40.782 [0x111469000] ERROR - Failed to start session successfully.
Nov 25, 2016 13:14:40.782 [0x1108fd000] ERROR - JobManager: child process killed by signal: 10 (Bus error: 10)
Now I have something to go definitively beat on folks with. What’s odd is it doesn’t happen on linux.
Great – thanks again for all your help.
I’ve submitted your info.
As a test, would you go to one of the episodes and ‘Analyze’ it again?
The more I dig into the error (bus error… which is an alignment error) makes me wonder if it’s using the wrong codec or is simply outdated. It is possible a prior version of PMS didn’t analyze it correctly and that’s what is biting us now. Running analysis again will update the results and trigger the proper codec download if not already present.
Analyzing the data wasn’t working—i.e., it wasn’t correctly refreshing/analyzing the data. So I went and did what I didn’t want to do…nuked my library, updated from OS X 10.10 to OS X 10.12 and installed Plex from scratch. This worked—the media analysis on Seinfeld is now correct and I can now view it anywhere, regardless of whether the client is Direct Playing or transcoding.
The only issue I’m seeing is that Plex isn’t automatically analyzing everything in my re-created library. There’s a lot of stuff that has audio: none, video: none just like those Seinfeld episodes did. Fortunately, manually analyzing these files is working, and the media properties to appear after doing so. It may be that the system is overwhelmed trying to analyze 11,000+ tv episodes.
Thanks for that… Unfortunately I cannot speak to the differences / potential problems between OS X versions. For better help, I will have to get some of the OSX guys to help with that.
I have over 7500 episodes in my TV library and don’t have any issues with rebuilds but it also may be precisely the differences between Linux and OS X which matter. Again, OS X isn’t my realm so I’ll get some help to step in.
What I can say about seeing ‘none’ for audio/video tags, I know from using MKV files. Easy tagging is why I use them. I refused to deal with all the issues inherent to MP4. I can easily edit the properties of a MKV without re-writing the entire file. I do not know if this is as easily done for a MP4. Last I looked, it required a re-encode or, minimally, a remux task.
Oh I hear you. My library is 99.99% .mkv because they’re just easier to work with. I only had one of those Seinfeld files as an .mp4 because I was trying to do anything to get Plex to recognize it. Thanks again for your efforts—much appreciated. It’s Ninjas like you that make this community awesome.
thanks.
If you want to spin the mp4 to mkv and then use mkvpropedit to set the appropriate tags one and for all.
ffmpeg -i file.mp4 -c:a copy -c:v copy -c:s copy file.mkv
(yes -c copy should work but some folks have older versions where it doesn’t).
once you have the mkv mkvpropedit filename --edit track:a1 --set language=eng --edit track:v1 --set language=eng
if you have a lot to do (fixing ‘UND’ (undefined) language or video tagging)…
From the top of the media directory:
find . -name \*.mkv -exec mkvpropedit {} --edit track:a1 --set language=eng --edit track:v1 --set language=eng \;
Problem eradicated 
