I think the problem was that the files that were not *.db, were remnants of a movie that was in the root of my videos folder.

Think a good idea would be to have some sort of verbose option, to quicker be able to track which directory is failing [feature request?]

Anyways, it seems to work right now.

OKAY! some success here. I ran find /volume1/video/movie/ -maxdepth 1 -type d -exec echo {} \; -exec filebot -script fn:artwork.tmdb {} -r \; My idea being that it would echo the actual directory being worked on and tell me what directory it started on, before failing. The first directory was a hit ...

I had installed filebot and it worked fine. Then two thing happened. I scheduled the command below and the latest DSM update came in: DSM 5.1-5021 Update 2 I suspect the latter messed something up. But it seems to have done so in the CLI as well. When I run: filebot -script fn:artwork.tmdb /volume1 ...