Here are the logs if anyone can look.
Searched the log package for the word “error”. Found lots–almost 4000. No idea what they mean. Examples with today’s date:
C:\Users\geoff\OneDrive\geoff-DTW7 Profile\Desktop\Plex Media Server Logs_2017-02-25_22-15-00\com.plexapp.agents.htbackdrops.log.1 (386 hits)
Line 90: File “parser.pxi”, line 596, in lxml.etree._raiseParseError (…\src\lxml\lxml.etree.c:72123)
Line 91: XMLSyntaxError: None
C:\Users\geoff\OneDrive\geoff-DTW7 Profile\Desktop\Plex Media Server Logs_2017-02-25_22-15-00\com.plexapp.agents.lastfm.log (2 hits)
Line 90: 2017-02-25 21:49:31,283 (734) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\Albums\1\4cf1c63cc96aa15871c2adf67dab62f7215afca.bundle\Contents\com.plexapp.agents.lastfm
C:\Users\geoff\OneDrive\geoff-DTW7 Profile\Desktop\Plex Media Server Logs_2017-02-25_22-15-00\com.plexapp.agents.localmedia.log (21 hits)
Line 1228: 2017-02-25 21:17:34,648 (24dc) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\TV Shows\0\b146300caee2084197e855db3fec1d4f5a33671.bundle\Contents\com.plexapp.agents.none
Line 1235: 2017-02-25 21:17:34,661 (1c34) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\TV Shows\0\b146300caee2084197e855db3fec1d4f5a33671.bundle\Contents\com.plexapp.agents.localmedia
Line 1266: 2017-02-25 21:18:11,604 (2438) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\TV Shows\9\53475313d1f34f65f7d9a48feaa0f436245eee9.bundle\Contents\com.plexapp.agents.thetvdb
Line 1273: 2017-02-25 21:18:11,618 (af0) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\TV Shows\9\53475313d1f34f65f7d9a48feaa0f436245eee9.bundle\Contents\com.plexapp.agents.localmedia
Line 1318: 2017-02-25 21:18:12,417 (1ffc) : ERROR (model:205) - Cannot read model from C:\Users\Entertainment\AppData\Local\Plex Media Server\Metadata\TV Shows\f\8b7c350e748fbc2e373dc7e1384e65fb69ce2ef.bundle\Contents\com.plexapp.agents.thetvdb
Line 7260: Feb 25, 2017 22:04:21.651 [8688] DEBUG - MDE: Planet Terror (2007): Direct Playing due to no transcode profile
Line 7261: Feb 25, 2017 22:04:21.651 [8688] DEBUG - MDE: Planet Terror (2007): no direct play video profile exists for http/mp4/h264
Line 7262: Feb 25, 2017 22:04:21.651 [8688] DEBUG - MDE: Planet Terror (2007): no direct play video profile exists for http/mp4/h264/aac
Feb 25, 2017 22:01:23.357 [9436] ERROR - [FFMPEG] - decode_slice_header error
Feb 25, 2017 22:01:23.357 [9436] ERROR - [FFMPEG] - decode_slice_header error
Feb 25, 2017 22:01:23.357 [9436] ERROR - [FFMPEG] - no frame!
Feb 25, 2017 22:01:23.357 [9436] ERROR - [FFMPEG] - SPS unavailable in decode_picture_timing
Feb 25, 2017 22:01:23.358 [9436] ERROR - [FFMPEG] - non-existing PPS 0 referenced
Feb 25, 2017 22:01:23.358 [9436] ERROR - [FFMPEG] - SPS unavailable in decode_picture_timing
Feb 25, 2017 22:01:23.358 [9436] ERROR - [FFMPEG] - non-existing PPS 0 referenced
Line 750: Feb 25, 2017 22:01:21.072 [6764] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Line 751: Feb 25, 2017 22:01:21.072 [6764] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Line 752: Feb 25, 2017 22:01:21.072 [6764] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Feb 25, 2017 22:05:31.727 [10028] ERROR - handle_stream_read error 335544539 short read
Feb 25, 2017 22:05:51.736 [10028] ERROR - handle_stream_read error 335544539 short read
Feb 25, 2017 22:05:51.736 [10028] ERROR - handle_stream_read error 335544539 short read
Feb 25, 2017 22:06:11.747 [10028] ERROR - handle_stream_read error 335544539 short read
As soon as I stop/start the Plex Media Server the stuck recordings start recording.
Having the same sort of problems and many others LOL
Intersting how NO Plex Devs are interested in this???
What version you running?
@gadgetgeek2000 said:
Specifically, I have a library called Plex Recorded TV that all my Plex DVR shows get saved into. I have a Windows scheduled task that launches a VBScript to parse these folders, look for any recordings that are finished (not locked for writing), do a Handbrake conversion of the .TS file to .MP4 and output to a different folder on my NAS. That folder is indexed by a separate library called “TV Shows”. I then allow Plex library update learn about the missing/new media files.
FYI - I have been doing something similar to this and have had problems with the DVR not recording shows until I restart Plex. This started around Beta 4. After dealing with this a couple of months, I’ve noticed the failures seem to align with when I remove the files for conversion and then put them back in the system. I’m beginning to think Plex DVR doesn’t handle this well and I have stopped converting files to see if the DVR will keep running. I’ll let you know if this improves my stability.
Question
Are these failures occurring at same chronological times for recordings or are the times of day random??
Maybe related to these two problems I have been having.
@jjrjr1 said:
Having the same sort of problems and many others LOL
Intersting how NO Plex Devs are interested in this???
What version you running?
http://forums.plex.tv/discussion/259283/dvr-beta-5-pms-1-4-1-sporadically-just-plain-fails-to-record-scheduled-recordings#latest
Just because they are not as active as us users are on the forums does not mean they are not aware.
@danjames92
Huh???
What are you saying here???
I believe he is saying that just because the Devs are not posting comments on the forum does not mean they are not aware of the issues being posted.
OIC
Thanks for the interpretation.
IMHO. I respectfully submit that since this post has been un acknowledged by Plex Devs for nearly a month and 1/2 is just plain rude, inconsiderate, and unappreciative.
We are all donating our time (And Have Paid for Plex Pass to volunteer) to Beta test their new product which Plex makes money on.
An Issue like this post (And many others) that seemingly being ignored is plain wrong, being that It goes to the core function of the feature and not a trivial issue.
A Thanks for your help or even a Hmmm. would be considerate of them in light of what we are all doing for them.
It’s sorta like if you were talking to somebody and they looked away from you while you spoke and never replied to your question. How would you feel if someone your were doing a favor for did that to you in real life.
That’s my feelings on the matter.
If you do not agree that is just fine.
But I think @danjames92 needs to take a few Valliums and allow others to have valid impressions or feelings.
Now enough of that said.
Let’s focus on continuing to help Plex get this Train Wreck flying!!!
So I need valium because you couldn’t understand what I was saying? Makes sense!
John got it in one.
Let’s hope it improves soon. This is definitely the buggiest release yet.
LOL
It’s OK
He is just smarter than I am!!
I also hope things get better. And I agree, the bugs are exponentially growing…
I plan to keep trying to help even though the perception sometimes feels like being ignored.
That’s how I will earn my Heavenly Gold Medals… LOL
I’m on Version 1.4.2.3400. I’d love to keep this thread focused on the issues. I know I and others are frustrated and the problems seem to be growing. But I’m willing to do anything to make this a rock-solid product.
Anyways…
There doesn’t seem to be any rhyme or reason. I can restart the Media Server and everything is fine for a while. Then something gets stuck. Even when it’s stuck, sometimes I can start recording something new and it will record fine. There are currently stuck shows in my .grab folder, that are zero bytes. I have proven that I can record shows from both of my HD HomeRun Prime devices. They have a fixed IP address on my network so availability should be fine.
I do have very large media libraries–lots of movies, tv shows, music, videos, photos, etc. I love Plex and how it makes my media available so I put tons of stuff in there. I have friends and family watching shows from my library so hate to keep stopping/starting the media server, and it is so hands-on right now watching for shows to get stuck that it is frustrating to use.
@kandlg said:
@gadgetgeek2000 said:
Specifically, I have a library called Plex Recorded TV that all my Plex DVR shows get saved into. I have a Windows scheduled task that launches a VBScript to parse these folders, look for any recordings that are finished (not locked for writing), do a Handbrake conversion of the .TS file to .MP4 and output to a different folder on my NAS. That folder is indexed by a separate library called “TV Shows”. I then allow Plex library update learn about the missing/new media files.
FYI - I have been doing something similar to this and have had problems with the DVR not recording shows until I restart Plex. This started around Beta 4. After dealing with this a couple of months, I’ve noticed the failures seem to align with when I remove the files for conversion and then put them back in the system. I’m beginning to think Plex DVR doesn’t handle this well and I have stopped converting files to see if the DVR will keep running. I’ll let you know if this improves my stability.
I will be very interested. I can’t do anything with .TS files on my devices, so conversion is paramount to consuming the media.
Version 1.4.2 is experiencing Database Deadlock in certain circumstances
The link I posted above is to a thread where that issue has been discovered.
I sorta think this issue and that one are related.
Dunno but symptoms sound similar to what I have been experiencing.
You might wanna try and make the changes to your server setting that he recommended to me to try and discover what the issue might be.
In that thread you will also see that when I removed files from the recording library while recording the PMS locked up. It was discovered that is was a Database Deadlock issue as well. This is why I think these issues are related
@sa2000
Is working that issue which is why I tried to point you over there.
The .ts files created by DVR are problematic at best.
The good news is the transcoding while recording is getting much closer to working well.
The addition of HW transcoding is coming soon to the mainline release. That might also help this .ts issue as well.
you linked to threads that link to lots of other threads. Which specific thread mentions a deadlock issue/resolution? I don’t find that.
Found it. Big thread. You are working with a developer so that is encouraging.
This is the one where a lot of work is being done.
Sounds Similar to this one.
No resolution yet.
Just testing options.
The devs have logs and Dumps…
@gadgetgeek2000 said:
Here are the logs if anyone can look.
This was my findings:
Feb 25, 2017 20:58:05.924 [7144] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v735?duration=2040
Feb 25, 2017 20:58:05.924 [7144] DEBUG - MediaRecorder: Recording completed with HTTP status 503
Feb 25, 2017 20:58:05.924 [7144] DEBUG - Activity: Ended activity 3d5dc38b-6d4f-4f3f-a139-91029828d273.
Feb 25, 2017 20:58:05.924 [7144] DEBUG - MediaGrabber: Operation for E16 - The Cohabitation Formulation completed with status 5 (The recording was aborted)
Feb 25, 2017 20:58:05.924 [7144] DEBUG - MediaGrabber: Freed a tuner (now 1 available)
Did you manually kill ‘The Cohabitation Formulation’ recording? Is the HDhomerun device’s IP 172.16.10.25?
and some others:
Feb 25, 2017 21:28:05.895 [1124] DEBUG - MediaGrabber: Operation for E13 - The Bat Jar Conjecture completed with status 5 (The recording was aborted)
Feb 25, 2017 19:28:05.902 [8256] DEBUG - MediaGrabber: Operation for E11 - The Pancake Batter Anomaly completed with status 5 (The recording was aborted)
I’d double check that you have the latest firmware on the tuner, too.
Just checked and Plex had quite a few stuck recordings. I restarted the server. Immediately, three recordings started. Parenthood seems to be recording ok. There are two Star Trek Voyager episodes trying to record. Both are stuck at 0 bytes.
2/27/2017 5:15 PM -5:30 PM. Logs attached.
@gadgetgeek2000 said:
Just checked and Plex had quite a few stuck recordings. I restarted the server. Immediately, three recordings started. Parenthood seems to be recording ok. There are two Star Trek Voyager episodes trying to record. Both are stuck at 0 bytes.2/27/2017 5:15 PM -5:30 PM. Logs attached.
Are you on the latest firmware for your tuner?
There’s lots of ‘exit with status 5’ errors.
@gadgetgeek2000 you never answered any of my questions…
Feb 27, 2017 15:58:01.003 [5544] DEBUG - MediaGrabber: Operation for E26 - Hope & Fear completed with status 5 (The recording was aborted)
Feb 27, 2017 15:58:05.813 [8304] DEBUG - MediaGrabber: Operation for E3 - Extreme Risk completed with status 5 (The recording was aborted)
Feb 27, 2017 13:58:05.741 [7368] DEBUG - MediaGrabber: Operation for E5 - Haunt You Every Day completed with status 5 (The recording was aborted)
Feb 27, 2017 14:58:00.787 [8304] DEBUG - MediaGrabber: Operation for E2 - Drone completed with status 5 (The recording was aborted)
Feb 27, 2017 14:58:05.735 [9932] DEBUG - MediaGrabber: Operation for E6 - Kung Fu Fighting completed with status 5 (The recording was aborted)
Feb 27, 2017 11:58:00.780 [6576] DEBUG - MediaGrabber: Operation for E22 - Innocence completed with status 5 (The recording was aborted)
Feb 27, 2017 11:58:05.706 [0940] DEBUG - MediaGrabber: Operation for E19 - Lifesigns completed with status 5 (The recording was aborted)
Feb 27, 2017 12:58:01.338 [8812] DEBUG - MediaGrabber: Operation for E26 - Hope & Fear completed with status 5 (The recording was aborted)
Feb 27, 2017 12:58:06.336 [7368] DEBUG - MediaGrabber: Operation for E4 - The Heart of the Matter completed with status 5 (The recording was aborted)
Feb 27, 2017 10:58:05.807 [0940] DEBUG - MediaGrabber: Operation for E21 - Deadlock completed with status 5 (The recording was aborted)
Feb 27, 2017 15:58:01.002 [5544] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v810?duration=3840
Feb 27, 2017 15:58:05.812 [8304] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v162?duration=3840
Feb 27, 2017 13:58:05.740 [7368] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v795?duration=3840
Feb 27, 2017 14:58:00.787 [8304] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v162?duration=3840
Feb 27, 2017 14:58:05.735 [9932] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v795?duration=3840
Feb 27, 2017 11:58:00.779 [6576] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v162?duration=3840
Feb 27, 2017 11:58:05.705 [0940] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v810?duration=3840
Feb 27, 2017 12:58:01.337 [8812] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v162?duration=3839
Feb 27, 2017 12:58:06.335 [7368] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v795?duration=3839
Feb 27, 2017 10:58:05.806 [0940] DEBUG - HTTP 503 response from GET http://172.16.10.25:5004/auto/v162?duration=3840
Seems like a tuner/network issue.
