Multiple, annoying Bugs, which renders this Files useless

[norrington]

I have multiple very annoying showstopper bugs:

- filebot just deletes the files, file is just gone
- filebot copys files, so there are then two instances: one renamed and one with the old name
- filebot renames files correctly, but then the new file is unplayable
- filebot does not delete all folders and files, but only the renamed file

of course, this is not happening with ALL files, but with a LOT, so I really cant use this app.

I'm using the latest version with a synology NAS and I'm using filebot with this sh-script with jdownloader:

Code: Select all

#!/bin/sh
##FileBot benötigt diese Variablen
##/bin/mkdir /volume1/video/Downloads/videos/testordner
LOG="/volume1/amc.log"
EXC="/volume1/amc.txt"
SERIEN="/volume1/video/Serien/{n}/{n}.{s00e00} - {t}"
FILME="/volume1/video/Filme/{n} ({y})"
UNSORTIERT="/path/{file.structurePathTail}" ### Wenn Filebot mal etwas nicht zuordnen kann, dann kannst du es in einen seperaten Ordner verschieben lassen, dann bleibt es im Downloadordner übersichtlich.
##FileBot ausführen
/var/packages/filebot/target/filebot.sh -script fn:amc --lang de --log-file $LOG --action move "$1" --def "seriesFormat=$SERIEN" "movieFormat=$FILME" "animeFormat=$ANIME" "unsortedFormat=$UNSORTIERT" -non-strict --def unsorted=y --def clean=y
## Aufräumen, --def root löscht den Unterordner mit
/var/packages/filebot/target/filebot.sh -script fn:cleaner "$1" --def root=y

How come? Is it possible to stop that? What is wrong with this app?

[rednoah]

Please include logs. Please read How to Request Help.


1.

- filebot just deletes the files, file is just gone
- filebot copys files, so there are then two instances: one renamed and one with the old name
- filebot renames files correctly, but then the new file is unplayable
- filebot does not delete all folders and files, but only the renamed file

What does the log say?
* Does FileBot log the operations that you think FileBot is performing?
* Does FileBot log a successful MOVE operation?

How did you check if files exist or not exist?
* Directly via SSH?
* Indirectly via Windows Network shares from your Desktop? (which may very well show you a cached outdated file system view)

What makes the file unplayable?
* Is the file content different?
* Did you compare checksums?
* Did you compare permissions?


None of this makes sense, which indicates that we're missing something. My educated guess (assuming there's no errors in the logs that indicate otherwise) would be that everything is actually working just fine on device, but you're seeing bad information when you view things via your remote Windows machine.

EDIT: This would also explain files in the original location no longer being playable, because they're not actually there anymore, and not existing most assuredly will make a file not playable.


2.
I recommend using the official amc script manual to get started. Your shell script seems familiar, and has familiar errors, though (1.) would be unrelated to that. Where did you copy it from?

Have you tried FileBot Node yet? If you're not too familiar with Linux and SSH, then that's a good way to get started:
viewtopic.php?t=2663

[rednoah]

If you're not yet using synoindex to notify Synology File Services of file system changes, then calling synoindex after each and every filebot call will likely be the solution:

Code: Select all

synoindex -R all

viewtopic.php?f=13&t=11027