Plex TV Scanner broken since 1.28.xxx?

The question is, are you doing the Plex Dance between every one of our suggestions, and have you completely removed those files from plex, and not just copied them somewhere else for testing? Plex attempts to detect file renames and preserve association of previous metadata and view history.

If you are using the proper Plex naming schema, and have performed the Plex Dance, the only other reason the files wouldnt show up is if the files where corrupt or not valid video files.

I’ve been doing this dance most likely more than you have ever done and probably ever do the last 2 weeks :slight_smile:
These files are fine and play everywhere, including from other plex server instances.

Can you post updated logs? this is an odd situation

see #19.

A: That was verbose logging and not the server logs I asked for. The entire server log directory has a number of different logs that could be useful.

One random thought, create a new directory for these files and a testing library and see if that changes anything.

I couldn’t find anything other than that hashes.json request which I’ve already reported in this thread.
logs.zip (276.6 KB)

so I’ve installed plex in a linux vm, samba mounted the so called broken,wrong filenames, directories, bla bla and everything works as expected :wink:

so can we finally agree this has nothing to do w/ file and/or directory naming? for whatever OTHER reason the scanner does not scan found files.

Do you have any other logs in your log directory other than Plex Media Server.log or Plex Tuner Service.log files?

nope, that was the complete log dir zipped. I have only excluded the “installer logs”.

What did you set the library type to, and what agent/scanner is being used?

uhmm, all that info is in first post :wink:

Can you take a look at your advanced section of your library (you noted the scanner but not the agent) and make sure it matches this:
Untitled

yes, everything default. you can not change plex tv series agent w/o changing scanner anyways

Im at a loss here, the logs dont have anything useful, and I cant re-produce the issue. When I load those files into my test plex it works just fine.

so am I and hence I am here :slight_smile: Looks like scanner.exe does not get invoked for found files.

I’ve attached debugger to server.exe and did a scan:

Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: std::runtime_error at memory location 0x08E2F808.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: NoRouteException at memory location 0x06BACBF8.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x0756ED3C.
The thread 0x5548 has exited with code 0 (0x0).
Exception thrown at 0x76FD09D2 in Plex Media Server.exe: Microsoft C++ exception: NoRouteException at memory location 0x0756C7E8.
The thread 0x7e44 has exited with code 0 (0x0).

@dane22 Any ideas?

Sorry, but currently swamped with password reset and claim issues :wink:

still busy? I am still having this issue.

Ups, and sorry :wink:
Was posted when we had a “minor” issue with a leak, and after that, I lost track of this thread, so huge thanks for the ping

We sadly have to start all over here, since a lot did happen in a month :frowning:

I need fresh logs in debug mode only, after you upgraded to the latest, and then did a Plex Dance on a troubled item

When posting, also mention the name of the item, so I know what to search for, and not we need the complete zip of logs, and not snips