License Error: Banned due to abuse

Running FileBot from the console, Groovy / FileBot scripting, shell scripts, etc
Locked
User avatar
rednoah
The Source
Posts: 18642
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

License Error: Banned due to abuse

Post by rednoah » 29 Dec 2018, 06:21

FileBot will regularly activate and check your license during normal operation. However, in some badly designed automated setups, if FileBot application data and caches are not persistent and lost between each call, then some users may inadvertently end up activating their license hundreds of times per day, and thus get themselves auto-banned.

Code: Select all

License Error: Banned due to abuse

:idea: If your license has been Banned due to abuse then please fix your automated setup and then message me your license number (e.g. P1234567) so I can reinstate your license.

:idea: If you don't know why your license might have been flagged by the system (after carefully reading this post) please message me your license number (e.g. P1234567) so I can have a look.



Tips & Tricks for not getting yourself auto-banned next time:


1.
DO NOT activate your license before running FileBot each and every time:

Code: Select all

filebot -license *.psm
filebot ...

2.
DO NOT clear the cache before running FileBot each and every time:

Code: Select all

filebot -clear-cache
filebot ...

3.
DO NOT delete the FileBot application data folder between runs:

Code: Select all

rm -r ~/.filebot
filebot ...

4.
DO NOT forcibly kill the filebot process:

Code: Select all

WARNING: The index for data file *.data is out of date, probably due to an unclean shutdown.
:!: FileBot may not be suitable for shared virtualized environments where the host OS forcibly terminates processes that exceed allotted resource limits.


5.
DO do ensure that there's plenty of free disk space for the FileBot application data folder:

Code: Select all

df -h
:!: FileBot will fail in strange and unexpected ways if it can't reliably read and write application data files.


6.
DO use --log-file so you can figure out what's going on later:

Code: Select all

--log-file filebot.log
:idea: Since FileBot requires a file lock on the log file, this will conveniently ensure that only one filebot instance is running at a time, while other filebot instances spawned in the meanwhile have to wait for that lock. This will ensure optimal cache performance.


7.
DO check your --log-file once in a while to see if everything is in order:

Code: Select all

grep "Activate License" /path/to/log

Code: Select all

Activate License P1234567
:!: Activate License P1234567 MUST NOT show up in your log for each and every filebot call. You will see this message once or twice per month during normal usage. If you see this message hundreds of times per day, then you need to fix your setup.

:!: The FileBot log file does not include system console output. Please read Shell Script Debugging for Beginners on how to collect complete console output including crash dumps and device errors. (NOTE: extremely useful for debugging strange issues)


Additional potential issues:
  • If you're launching FileBot Portable from a network drive, then FileBot may not be able to reliably read / write / lock application data files and fail in strange and unexpected ways.
:idea: Please read the FAQ and How to Request Help.

Locked