The last crash at 14:57 MT was uploaded to Plex:
Sep 08, 2019 14:57:52.855 [0x7f3caaae8740] INFO - Successfully reported 7589e734-50fc-5ebe-251781b7-42459e4b
dmesg from crash:
[81714.886374] traps: Plex Media Scan[16132] general protection fault ip:7f84f1290097 sp:7f84d729afe0 error:0 in libcrypto.so.1.0.0[7f84f117f000+204000]
The crash at 14:57 is recorded in Plex Media Server.1.log
That makes no sense other than what I’ve seen in Fedora 30 itself.
I use Fedora 28 here because I cannot use 29 or 30 for production. They are far too unstable.
For libcrypto to trap, this makes no sense. Do you have a custom certificate?
Plex Media Scanner.log:1677:Sep 08, 2019 15:17:49.652 [0x7f5301a74740] ERROR - Exception caught determining whether we could skip 'Doctor.Who' ~ Null value not allowed for this type
and I find a handful of FFmpeg errors like these:
Plex Media Scanner.2.log:18170:Sep 08, 2019 15:17:48.653 [0x7fa9c77fe700] ERROR - [FFMPEG] - moov atom not found
Plex Media Scanner.2.log:18172:Sep 08, 2019 15:17:48.653 [0x7fa9c77fe700] ERROR - Exception analyzing media file '/local/clinton/Download/mirc/Outcast.S01E06.WEB-DL.x264-FUM.mp4' (Could not parse /local/clinton/Download/mirc/Outcast.S01E06.WEB-DL.x264-FUM.mp4 (error=-1094995529): Invalid data found when processing input)
Plex Media Scanner.2.log:18180:Sep 08, 2019 15:17:48.700 [0x7fa9c77fe700] ERROR - [FFMPEG] - moov atom not found
Plex Media Scanner.2.log:18182:Sep 08, 2019 15:17:48.700 [0x7fa9c77fe700] ERROR - Exception extracting thumbnail from media file '/local/clinton/Download/mirc/Outcast.S01E06.WEB-DL.x264-FUM.mp4' (Could not parse /local/clinton/Download/mirc/Outcast.S01E06.WEB-DL.x264-FUM.mp4 (error=-1094995529): Invalid data found when processing input)
Can we remove the offending files from PMS and try again?
I used a command like this (on macOS):
@sclintow Please stick with Chuck on this.
I was eager to point out the ERROR messages I saw in the logs you uploaded.
I shouldn’t have asked you to move files before you finished following his direction.
Not that moving a few files is bad, but he knows better
Moving suspected bad files to a different area is a good idea.
The scanner isn’t infallible. If the media files are damaged, it could cause a problem. A libcrypto fault (meaning a wild memory pointer) is not what I would expect though from data)
After searching for error 4 in libcrypto.so.1.0.0 for another post,
I came across a Github project that resolved the same error message in their project,
narrowing it down to an interaction with SSL. Would someone familiar with C++
let us know if this looks promising?
Found version plexmediaserver_1.15.4.993-bb4a2cb6c_amd64.deb and downgraded.
It would be great if there were a repository available for easy downgrading.
Thanks for a fantastic product - keep up the great work! I know you guys will get this fixed eventually.
