Plex Media Scanner Log (more detail required)

Looking through my logs I see a bunch of these errors

Sep 04, 2018 09:05:28.777 [0x7f9d6fad6700] INFO - Plex Media Scanner v1.13.6.5339-115f087d6 - ubuntu PC x86_64 - build: linux-ubuntu-x86_64 - GMT 01:00
Sep 04, 2018 09:05:28.779 [0x7f9d6fad6700] INFO - Linux version: 3.10.0-862.9.1.el7.x86_64 (#1 SMP Mon Jul 16 16:29:36 UTC 2018), language: en-US
Sep 04, 2018 09:05:28.779 [0x7f9d6fad6700] INFO - Processor Intel® Xeon® CPU E5-2690 v2 @ 3.00GHz
Sep 04, 2018 09:05:28.779 [0x7f9d6fad6700] INFO - /usr/lib/plexmediaserver/Plex Media Scanner --scan --refresh --section 1
Sep 04, 2018 09:05:59.318 [0x7f9d67fff700] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Sep 04, 2018 09:05:59.318 [0x7f9d67fff700] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Sep 04, 2018 09:05:59.318 [0x7f9d67fff700] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.
Sep 04, 2018 09:05:59.318 [0x7f9d67fff700] ERROR - [FFMPEG] - Invalid frame dimensions 0x0.

But nowhere in the log file does it tell me which file it is scanning when it sees this error.
Can the filename be added to the debug output please.

Thanks

you probably have debug logging disabled on the server

See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

I guess my point is that the log as it stands isn’t very useful.

If its just a case of a %s in a printf, then can the filename be added. If you are just capturing the STDERR from ffmpeg, and working out the filename is a PITA then I understand the issue.

There are thousands of warning and error log lines that do not have sufficient information in them to troubleshoot a problem if debug logging is disabled.

So it would not be a matter of just changing this log line

Plex Media Server has debug logging by default

If after disabling debug logging you notice an issue, then one would enable debug logging and investigate

I do understand that one can add more info to the error but as I said there are thousands of other error / warning log lines that have the same issue as that

Early 2021 clean-up: implemented/available (debug logs)