coppit

PM me your log.

You and I both suspect that your password has "special characters" in it that are causing problems. $ " \ are examples of characters that can cause you grief. Example of how you need to put a backslash before those characters: $ OPENSUBTITLES_PASSWORD="\$a'/\"\\" $ echo $OPENSUBTITLES_PASSWORD $a'/"\ If you're still having trouble, I could put a message in the log to show you what password the code sees.

Can you PM me your log? Also mention when a move from /incomplete to /complete happens (timestamp). Edit: Also note that if there is other activity going on in the watched folder, the monitor will wait for MAX_WAIT_TIME for the changes to stop. (Default 1 minute.)

Done. New release soon. Looks like a couple of other people tried "move", and it didn't work. Thanks for finding the issue.

Googling a bit, I see others complaining about the CPU usage too: https://www.filebot.net/forums/viewtopic.php?t=3438 You might explore whether there's a way to run the docker container "nice" so that even if there's 100% CPU, it will give it up to any other process that needs it.

That's a filebot issue, I guess. If you updated your filebot.sh to have "--action move" and it's still not working, you could try deleting the "--action move" entirely. The default action is to move. You could also throw in an "echo 'blah'" to make sure your version of the script is being run.

Oops. Sorry. I was referring to the CLI version. I've now bumped the UI version too. Thanks for this! I've updated the container so that you can map /config to /mnt/cache/applications/filebot/config/, which is hopefully easier for folks.

Log into your server, and run: USERNAME='<username from your conf file>' PASSWORD='<password from your conf file>' DOMAINS='<domains from your conf file>' curl -S -k --user-agent "coppit docker no-ip/.1 $USERNAME" -u "$USERNAME:$PASSWORD" "https://dynupdate.no-ip.com/nic/update?hostname=$DOMAINS" If that works, then check your conf file for correctness, and see if there are any other errors in the container logs. If you can't find any problem, I can add more logging so that we can figure it out.

You've somehow injected some bogus characters at the top of the file, and perhaps elsewhere. I try to scrub out windows line endings, but I'm not sure what to do about those unicode (?) characters. Log into your server and run "nano noip.conf". If there are any characters before the "#", delete them. Then restart your container and see if that clears up the problem.

The container doesn't support monitoring lots of folders and running different scripts. I would recommend simply running multiple containers which different configurations. They're very lightweight. Just point each container to each subdir for the input and output. That said, the default config handles different input types already, putting them into subdirs in the output dir. Did you try it? It only occasionally gets confused and renames a tv show to a movie or vice versa. If you do want to rewrite filebot.sh, what you can do is have multiple commands run in each of the subdirs of the parent input dir. e.g. if the monitor sees a change in input/tv, it will run your filebot.sh, which will process input/tv, input/movies, and all the other subdirs. (Just specify the parent input dir as the one to be monitored.) If you go this route, be sure to leave VERSION as it is in your script. That way if I ever update the default script, it will give you an error so that you can see if the new changes need to be reflected in your script.

I think you meant /mnt/user. You might consider using /mnt/user0 if you have a cache drive. That will bypass the cache drive, which might fill up if you're using it to process a lot of files. BTW, I don't recommend blindly running FileBot on all your files. It can make mistakes that are a PITA to fix.

FYI, I added a link to the template. The web UI is at http://tower:3389/ To be honest I'm kinda shocked that anyone is using the UI version. I never figured out how to get it to save my settings, which was a deal breaker for me. I'm not going to re-enter my crazy formatting string every time I use the thing.

I just updated it to 4.7.2. Check it out and see if it works well for you.

Did you recently copy your appdata files to a different location? I had to: docker exec -it MineOS bash chown -R minecraft:minecraft /var/games/minecraft/* exit

I'm stumped too. What do you get when you run this sequence?: cat /tmp/plugins/snmp/drive_temps.txt snmpwalk -v 2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutLine."disktemp"' cat /tmp/plugins/snmp/drive_temps.txt /usr/local/emhttp/plugins/snmp/drive_temps.sh cat /tmp/plugins/snmp/drive_temps.txt snmpwalk -v 2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutLine."disktemp"' cat /tmp/plugins/snmp/drive_temps.txt I'm wondering if there's an issue with the caching. Another thought: There's a "sleep 15" in the drive_temps.sh script. I don't remember why. Maybe removing it would allow the script to run faster, solving the problem for you? Try it let me know what happens.

This works nicely, thank you. But is there an easy way to make it permanent so that it survives a reboot? What you could try is putting something like this into your go script: echo "$(/sbin/ifconfig br0 | grep inet | awk '{print $2}') storage" >> /etc/hosts Then use the advanced container options to map /etc/hosts from the docker host to the container. The container will think that localhost is your server, but maybe that's okay?

Check out my FileBot container if you're looking for automated renaming, subtitle downloading, etc. Non-Linux apps can't be converted into docker containers or unraid plugins. Maybe later this year Windows apps might be containerizable though.

It will report failure if there are no files to move. Very confusing, I know. The UI doesn't show the cause of the failure. Please log into your server and run "docker logs FileBot" (use whatever your container name is). If it says "No files selected for processing", then that's to be expected. BTW, I've filed a bug about the UI here: http://lime-technology.com/forum/index.php?topic=47011.0

This seems like a mis-feature of the upgradepkg tool. I add the flag --install-new so that it will install perl if it's not already on the system. But it seems to also force-install the older version if a newer version already exists. If this is a big issue, I suppose I could write my own install tool wrapper that checks versions properly... In the meantime I'll just bump the version of perl to match nerdtools. I doubt it will break things. Let me test it.

Yeah, that's my setup too. You don't want the incomplete dir to be watched by filebot, since it apparently will try to process the file before it's done. Looking at the monitor, I do have it treating "file close" as an event. That's different then "file close after write", so I presume that event would be a "close after read". I haven't watched it closely enough to see if filebot only processes the file after seeding is over, or at least after no seeding has happened for the stabilization time. You could try setting a shorter stabilization time, or setting your seeding ratio lower. You can get FileBot to move instead of copy, but that can be a bit dangerous. Sometimes it mis-detects the files.

No, it doesn't exclude everything. I *processes* everything. As part of that work, it excludes the files it has processed. Are you sure you configured your output directory properly? It's writable? If you don't see any files there, log into your server, run a command to log into the container and look into its /output dir: docker exec -it FileBot bash ls /output If the container's /output has files, but outside of the container there are no files, then you've misconfigured the output dir. Correct. It waits a bit for the directory to stabilize before it runs. See the docs. https://hub.docker.com/r/coppit/filebot/ Within a few minutes it will run. Most likely it did eventually run, but if your output dir was not set right, you might not notice.

See the docs: https://hub.docker.com/r/coppit/filebot/ Specifically, the part about changing "copy" to "rename". Caveat emptor!

Did you mess with the settings in filebot.conf? Here are the defaults: SETTLE_DURATION=10 MAX_WAIT_TIME=01:00 MIN_PERIOD=05:00 Note that the MIN_PERIOD is 5 minutes, meaning that FileBot will at most run once every 5 minutes.

Unfortunately the UNRAID GUI doesn't capture the STDERR of docker logs. Can you guys log into your server and run: docker logs FileBot ? For example, if FileBot has already run and processed some files, it will say: Using excludes: /config/amc-exclude-list.txt (4725) No files selected for processing Failure (°_°) If you check the amc-exclude-list.txt, you would see the files there.

So you're telling the container to wait 3 minutes after the last event before running filebot? But you're also wanting filebot to try to run in 10 seconds? That's odd. Typically MIN_PERIOD would be more than SETTLE_DURATION. Is there any way that your Mac Mini is taking longer than 3 minutes to finish working on the files? One thing I can imagine is that the file is opened, and the container sees that event, but it doesn't see the writes that happen. So it doesn't know that there's still activity going on. I tried running "lsof" to see if we can detect that something outside the container has the file open still, but unfortunately it doesn't see it. As long as there is any duration in the creation of the file, there is going to be a risk that FileBot attempts to process the file. I recommend doing the unpacking in a separate directory, then do an atomic move of the files into the FileBot input directory. You can look for messages like this in the log to see why FileBot was run: Input directory didn't stabilize after $MAX_WAIT_TIME seconds. Triggering command anyway. Input directory stabilized for $SETTLE_DURATION seconds. Triggering command. Waiting an additional $remaining_time seconds before running command If you set DEBUG=1 in the config file, the monitor will dump a lot of information about the events that are detected. That would confirm my theory that it detects the opening of the file for writing, but not all the writes.