Is there any idea why I am getting this error from time to time? They typically show up for 6AM DVR recordings, but I just had this happen twice for two shows scheduled to air between 6PM and 7PM.
My NAS (unRAID) is constantly running with many TB of empty disk space, so storage being available and ready isn’t an issue.
I have attached the server logs (I hope that is enough, if not then tell me). The show in question is All in the Family. One episode was scheduled to air from 6:00PM to 6:30PM, and the other was scheduled to air from 6:30PM to 7:00PM.
@Endda said:
Is there any idea why I am getting this error from time to time? They typically show up for 6AM DVR recordings, but I just had this happen twice for two shows scheduled to air between 6PM and 7PM.
My NAS (unRAID) is constantly running with many TB of empty disk space, so storage being available and ready isn’t an issue.
I have attached the server logs (I hope that is enough, if not then tell me). The show in question is All in the Family. One episode was scheduled to air from 6:00PM to 6:30PM, and the other was scheduled to air from 6:30PM to 7:00PM.
An issue giving rise to this error is currently being fixed and appears to arise after transcoder job failure
May 26, 2017 18:00:14.362 [0x2ae66d602700] VERBOSE - JobManager: child process with PID 30191 exited
May 26, 2017 18:00:14.362 [0x2ae66d602700] ERROR - JobManager: child process returned: 1 (Operation not permitted)
May 26, 2017 18:00:14.362 [0x2ae66d602700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 30191 is 1
and later
May 26, 2017 18:00:14.363 [0x2ae66d401700] DEBUG - DVR:Grabber: Recording for 'All in the Family - E14 - Birth of the Baby' stopped with status error.
May 26, 2017 18:00:14.363 [0x2ae66d401700] DEBUG - DVR:Grabber: Using recording status.
and led to the error later
I will add your diagnostics to that internal issue.
@Endda said:
Is there any idea why I am getting this error from time to time? They typically show up for 6AM DVR recordings, but I just had this happen twice for two shows scheduled to air between 6PM and 7PM.
My NAS (unRAID) is constantly running with many TB of empty disk space, so storage being available and ready isn’t an issue.
I have attached the server logs (I hope that is enough, if not then tell me). The show in question is All in the Family. One episode was scheduled to air from 6:00PM to 6:30PM, and the other was scheduled to air from 6:30PM to 7:00PM.
An issue giving rise to this error is currently being fixed and appears to arise after transcoder job failure
May 26, 2017 18:00:14.362 [0x2ae66d602700] VERBOSE - JobManager: child process with PID 30191 exited
May 26, 2017 18:00:14.362 [0x2ae66d602700] ERROR - JobManager: child process returned: 1 (Operation not permitted)
May 26, 2017 18:00:14.362 [0x2ae66d602700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 30191 is 1
and later
May 26, 2017 18:00:14.363 [0x2ae66d401700] DEBUG - DVR:Grabber: Recording for 'All in the Family - E14 - Birth of the Baby' stopped with status error.
May 26, 2017 18:00:14.363 [0x2ae66d401700] DEBUG - DVR:Grabber: Using recording status.
and led to the error later
I will add your diagnostics to that internal issue.
wow, that is great news. Thank you for the reply and the details
It is actually a secondary error - so we do need to establish why the transcoder job is failing
May 26, 2017 18:00:14.361 [0x2ae66d200700] ERROR - [Transcoder] Stream map '0:2' matches no streams.
To ignore this, add a trailing '?' to the map.
May 26, 2017 18:00:14.362 [0x2ae66d602700] VERBOSE - JobManager: child process with PID 30191 exited
May 26, 2017 18:00:14.362 [0x2ae66d602700] ERROR - JobManager: child process returned: 1 (Operation not permitted)
May 26, 2017 18:00:14.362 [0x2ae66d602700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 30191 is 1
@sa2000 said:
It is actually a secondary error - so we do need to establish why the transcoder job is failing
May 26, 2017 18:00:14.361 [0x2ae66d200700] ERROR - [Transcoder] Stream map '0:2' matches no streams.
To ignore this, add a trailing '?' to the map.
May 26, 2017 18:00:14.362 [0x2ae66d602700] VERBOSE - JobManager: child process with PID 30191 exited
May 26, 2017 18:00:14.362 [0x2ae66d602700] ERROR - JobManager: child process returned: 1 (Operation not permitted)
May 26, 2017 18:00:14.362 [0x2ae66d602700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 30191 is 1
Is there anything I can do to help troubleshoot the issue?
@sa2000 said:
It is actually a secondary error - so we do need to establish why the transcoder job is failing
May 26, 2017 18:00:14.361 [0x2ae66d200700] ERROR - [Transcoder] Stream map '0:2' matches no streams.
To ignore this, add a trailing '?' to the map.
May 26, 2017 18:00:14.362 [0x2ae66d602700] VERBOSE - JobManager: child process with PID 30191 exited
May 26, 2017 18:00:14.362 [0x2ae66d602700] ERROR - JobManager: child process returned: 1 (Operation not permitted)
May 26, 2017 18:00:14.362 [0x2ae66d602700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 30191 is 1
Is there anything I can do to help troubleshoot the issue?
Any update on this yet @sa2000 ? I just got a PM from another Plex forum member asking if there was any resolution to it since they were experiencing it as well.
It seems real hit or miss. I hadn’t had the issue happen in a week or two, and then it missed one earlier this morning
@Endda said:
Any update on this yet @sa2000 ? I just got a PM from another Plex forum member asking if there was any resolution to it since they were experiencing it as well.
It seems real hit or miss. I hadn’t had the issue happen in a week or two, and then it missed one earlier this morning
Would suggest waiting for version 1.7.4 which should come out within the next 2 weeks and if problem remains, would then look at new logs from that version. A lot of changes have been taking place in this area that will feed into version 1.7.4 and the one after
@Endda said:
Any update on this yet @sa2000 ? I just got a PM from another Plex forum member asking if there was any resolution to it since they were experiencing it as well.
It seems real hit or miss. I hadn’t had the issue happen in a week or two, and then it missed one earlier this morning
Would suggest waiting for version 1.7.4 which should come out within the next 2 weeks and if problem remains, would then look at new logs from that version. A lot of changes have been taking place in this area that will feed into version 1.7.4 and the one after
Time to give 1.7.4 a go and if problem remains please upload logs from 1.7.4 plus details of what was wrong and when
@Endda said:
Any update on this yet @sa2000 ? I just got a PM from another Plex forum member asking if there was any resolution to it since they were experiencing it as well.
It seems real hit or miss. I hadn’t had the issue happen in a week or two, and then it missed one earlier this morning
Would suggest waiting for version 1.7.4 which should come out within the next 2 weeks and if problem remains, would then look at new logs from that version. A lot of changes have been taking place in this area that will feed into version 1.7.4 and the one after
Time to give 1.7.4 a go and if problem remains please upload logs from 1.7.4 plus details of what was wrong and when
Thanks for the heads up, I have it installed. I’ll keep my eye on things and see if it happens again. How soon after the missed recording do the logs need to be? I’ve generally seen it happen in the morning at like 6AM (although it is random), but I don’t get up until 8AM and rarely have time to look at Plex’s calendar view until 10AM
