Server Version#: 1.31.0.6654
Player Version#: LG Plex App, latest
Hello community!
I got at least 3 error like mentioned in the topic.
What’s the problem?
Best regards
5 Likes
Same error keeps happening on my Synology as well
Now using the latest 1.31.1.6716, but it was the same in the previous 1.31.0.6654 and in the alpha version.
Tried on several shows and movies, always the same error. Intro detection works fine
Feb 15, 2023 16:46:39.238 [0x7fc388cdcb00] INFO - Plex Media Scanner v1.31.1.6716-ca0c45ff8 - Synology DS220+ x86_64 - build: linux-x86_64 - GMT 01:00
Feb 15, 2023 16:46:39.238 [0x7fc388cdcb00] INFO - Linux version: DSM 7.1.1.42962-4, language: en-US
Feb 15, 2023 16:46:39.238 [0x7fc388cdcb00] INFO - Processor: 2-core Intel(R) Celeron(R) J4025 CPU @ 2.00GHz
Feb 15, 2023 16:46:39.238 [0x7fc388cdcb00] INFO - /volume1/@appstore/PlexMediaServer/Plex Media Scanner -C -f /volume2/Media/TV Shows/showxxx/Season 1/xxxxx.mkv --log-file-suffix Credits
Feb 15, 2023 16:47:01.796 [0x7fc388d78b40] ERROR - BufferingLineReader: failed to read line (error: -1)
1 Like
Yep, I’m also getting loads and loads of these errors.
That error message is unfortunately not very useful at the moment as it will get logged even if nothing went wrong. It will get fixed in a future PMS version.
If you have a specific problem then you’ll have to be more specific on what is actually happening.
1 Like
Turn DEBUG logging back on.
Restart PMS
Recreate it
Capture fresh logs ZIP file
Attach the ZIP file here so DrZoidberg can see them
when you turned DEBUG off, you hampered any chance of tracking down where it’s coming from
Well yes, it doesn’t generate a credits marker.
I enabled Debug and tried on a movie and an episode.
Plex Media Server Logs_2023-02-16_21-29-14.zip (1.1 MB)
EDIT: To be clear, generelly it DOES generate credits markers on some files.
It may be related to the timeout issue which is resolved in the latest beta:
In my case even using the latest beta 1.31.1.6716, no credit are detected with the same error . This is going on from the original alpha release, i.e. it never worked properly.
As I already pointed out, Credits detection works fine.
I enclose the latest full logs:
Plex Media Server Logs_2023-02-17_14-58-20.zip (305.5 KB)
You’ll need to enable Debug Logging in order for their to be useful information in the logs.
Same error and no credits does not work as a whole.
Also not exactly sure how to see if any credits got detected, but the recently added stuff has no markers
root@lxt-prod-users-plex01:~# cat Plex\ Media\ Server.log |grep Credits|grep ERROR|wc -l
633
a bit spamy
I am running PMS beta version 1.31.1.6716 from a docker container in a server with an ARM CPU and having the same error.
[Req#2d064/CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
[Req#2d064/CreditsDetectionManager] Job failed: Decryption failed
Image of the error: IMG-20230218-WA0000 hosted at ImgBB — ImgBB
I’m also getting the problem and I think it might be blocking intro detection. I can see a credits Marker being added, but the intro one is missing.
Using Winx64 1.31.0.6654 but it also happens on 1.31.1.6716 as well
Plex Media Scanner Credits.log
Feb 20, 2023 21:48:38.584 [19828] DEBUG - [JobRunner] Jobs: Starting child process with pid 19768
Feb 20, 2023 21:49:20.875 [5904] DEBUG - Jobs: 'C:\Program Files\Plex\Plex Media Server\Plex Transcoder.exe' exit code for process 19768 is 0 (success)
Feb 20, 2023 21:49:20.894 [19828] ERROR - PeekNamedPipe failed: 0x6d
Feb 20, 2023 21:49:20.894 [19828] ERROR - BufferingLineReader: failed to read line (error: -1)
Plex Media Server.log
Feb 20, 2023 21:49:39.967 [12104] DEBUG - Jobs: 'C:\Program Files\Plex\Plex Media Server\Plex Media Scanner.exe' exit code for process 12196 is 0 (success)
Feb 20, 2023 21:49:39.970 [25424] ERROR - [Req#2ea/CreditsDetectionManager] PeekNamedPipe failed: 0x6d
Feb 20, 2023 21:49:39.970 [25424] ERROR - [Req#2ea/CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
Feb 20, 2023 21:49:39.971 [25424] DEBUG - [Req#2ea/CreditsDetectionManager] Activity: updated activity b72475de-28f6-42b0-9cb1-ec50a56d1e6a - completed 75.0% - Detecting Credits
Feb 20, 2023 21:49:39.971 [25424] DEBUG - [Req#2ea/CreditsDetectionManager] Updating part with ID=134191 [M:\Video\TV\The Last of Us (2023) {imdb-tt3581920}\Season 01\The Last of Us (2023) - S01E06 - Kin [HMAX WEBDL-2160p][DV]-NTb.mkv]
Feb 20, 2023 21:49:39.973 [25424] DEBUG - [Req#2ea/CreditsDetectionManager] Doing expensive tags write for 'Kin' because something changed.
Feb 20, 2023 21:49:39.974 [25424] DEBUG - [Req#2ea/CreditsDetectionManager] Successfully processed item 100820
Feb 20, 2023 21:49:39.974 [25424] DEBUG - [Req#2ea/CreditsDetectionManager] Activity: Ended activity b72475de-28f6-42b0-9cb1-ec50a56d1e6a.
Let me know if you want me to try some things
logs.zip (23.7 KB)
Edit: I should also mention that I have it set to local detection only if that makes a difference. I know that it forces it to be recalculated when Analyze is triggered on the video, but not sure if it has other effects.
I tested with the new version 1.31.1.6733 and I still get these error logs:
Feb 21, 2023 12:29:12.161 [0xffffb147a0d0] Error — [Req#1c3/CreditsDetectionManager] BufferingLineReader: failed to read line (error: -2)
Feb 21, 2023 12:29:22.161 [0xffffb147a0d0] Debug — [Req#1c3/CreditsDetectionManager] Killing job.
Feb 21, 2023 12:29:22.161 [0xffffb147a0d0] Debug — [Req#1c3/CreditsDetectionManager] Signalling job ID 1066 with 9
Feb 21, 2023 12:29:22.161 [0xffffb147a0d0] Debug — [Req#1c3/CreditsDetectionManager] Activity: updated activity d5864e7f-3048-4c02-b8eb-a2adc3e60dfb - completed 75.0% - Detecting Credits
Feb 21, 2023 12:29:22.175 [0xffffb147a0d0] Error — [Req#1c3/CreditsDetectionManager] Job failed: Scanner job failed
Feb 21, 2023 12:29:22.178 [0xffffb147a0d0] Debug — [Req#1c3/CreditsDetectionManager] Activity: Ended activity d5864e7f-3048-4c02-b8eb-a2adc3e60dfb.
Also having this issue, except it’s affecting all of my media. I have yet to have a successful credits detection. Here are the credit scanner logs with verbose and debug enabled, doesn’t appear different to others. In case it helps, all my media is H265 in MKV, this is also on the latest plex pass beta
Plex Media Scanner Credits.log (7.0 KB)
1 Like
Updated to the latest 1.31.1.6733 and no change: still credits recognition doesn’t work on any h265 file. Latest logs are enclosed.
In conclusion, at least in my case, Credit recognition only works for the h264 files; it doesn’t work for any HEVC (H265) files: not one of them have the Credits marker tag.
1 Like
I’m seeing the same issues. I only have h264, and it seems to happen with my longer movies primarily (none of my Lord of the Rings extended have completed, but almost everything else has). My logs look very similar to slashking826, where it gets to the 75% complete and then fails with error: -2. If it would be helpful, I can pull some logs. I’m on a Raspberry Pi 4, so I was hopeful that the timeout fix would resolve this for me, but it hasn’t.
I have that same problem with many files. Most of them are x265.mkv, but I have also problems with x265.10bit.mkv or DoVi 2160p ts files. I turned on debug logging, here are last 6 log files (it is possible to incresease this limit?)
Plex Media Scanner Credits.1.log (6.1 KB)
Plex Media Scanner Credits.2.log (7.8 KB)
Plex Media Scanner Credits.3.log (5.9 KB)
Plex Media Scanner Credits.4.log (5.3 KB)
Plex Media Scanner Credits.5.log (6.1 KB)
Plex Media Scanner Credits.log (5.5 KB)
1 Like
Is there any updates with this issue? And is there anything I could do to help? The credits detection hasn’t worked for me yet because of this error 
2 Likes
I was one of the first to raise the issue (2 months ago) and since then I tried any new version but the issue hasn’t been solved yet.
It seems to be specific to Synology NAS
1 Like
Nothing changed.
# cat Plex\ Media\ Server.log |grep CreditsDetection|grep ERROR|wc -l
329
2 Likes
