AMC Script stopped running

[fontalamh]

Kia ora

I had an script calling amc running fine until a few days ago when it stopped (r became so slow it might as well not be running.

The script is:

Shell: Select all

filebot -script fn:amc "/home/rob/Downloads/Complete/" --output "/mnt/incoming/" --action move -non-strict --log-file amc.log

It outputs:

Console Output: Select all

Run script [fn:amc] at [Tue Jul 04 00:09:49 NZST 2023]

[PSA] Important Discussion of Proposed Changes:
https://www.filebot.net/forums/viewtopic.php?t=13406

Parameter: excludeList = amc.txt
Parameter: clean = y
Parameter: deleteAfterExtract = y
Parameter: unsorted = y
Argument[0]: /home/rob/Downloads/Complete
Use excludes: /mnt/incoming/amc.txt (43)

then stops (certainly doesn't do anything noticeable).

I had an error about licensing and I re-imported the license file and this is now gone.

I have purged the install and deleted everything I can find, then reinstalled but the problem persists. I've updated to Java 19, the problem persists. I tried the snap and the problem persists.

Running filebot from the command line gives:

Console Output: Select all

Initialize new disk cache: /home/rob/.filebot/cache/1

With an ever increasing number on the end it seems.


amc log:

Console Output: Select all

Argument[0]: /home/rob/Downloads/Complete
Run script [fn:amc] at [Tue Jul 04 00:09:49 NZST 2023]

[PSA] Important Discussion of Proposed Changes:
https://www.filebot.net/forums/viewtopic.php?t=13406

Parameter: excludeList = amc.txt
Parameter: clean = y
Parameter: deleteAfterExtract = y
Parameter: unsorted = y
Argument[0]: /home/rob/Downloads/Complete
Use excludes: /mnt/incoming/amc.txt (43)

One anomaly I noticed is on install, apt said - Storage: none, replicated in sysinfo:

Console Output: Select all

FileBot 5.0.3 (r9760)
JNA Native: 6.1.6
MediaInfo: 22.12
Tools: fpcalc/1.5.1 7z/16.02 unrar/6.21 mkvpropedit/74.0.0
Extended Attributes: OK
Unicode Filesystem: OK
GVFS: PlatformGVFS [/run/user/1000/gvfs]
Script Bundle: 2023-06-26 (r907)
Groovy: 4.0.11
JRE: OpenJDK Runtime Environment 19.0.2
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 4 Core / 4.2 GB Max Memory / 43 MB Used Memory
OS: Linux (amd64)
HW: Linux lr 6.2.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16 12:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
CPU/MEM: Intel(R) Pentium(R) CPU G4560 @ 3.50GHz [MemTotal: 16 GB | MemFree: 618 MB | MemAvailable: 10 GB | SwapTotal: 2.1 GB | SwapFree: 2.1 GB]
[b]STORAGE: NONE
[/b]UID/GID: uid=1000(rob) gid=1000(rob) groups=1000(rob),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),123(lpadmin),132(lxd),133(sambashare),1002(robt)
DATA: /home/rob/.filebot
Package: DEB
License: FileBot License PX29291688 (Valid-Until: 2071-10-02)

Filebot works perfectly as far as I can tell - it's just calling the script that causes problems.

[rednoah]

What happens if you try different input folders? Have you tried a simple test run on a newly created folder with newly created files just to see if that works?



The command that you posted is notably not the command that is running, because the console output clearly shows various --def name=value parameters being set:

Console Output: Select all

Parameter: excludeList = amc.txt
Parameter: clean = y
Parameter: deleteAfterExtract = y
Parameter: unsorted = y

If it stalls after Use excludes: but before Input: then it's likely stuck at listing files from the input file path. Unusual, but possible if the file system itself is extremely slow.

What does find say?

Shell: Select all

find /home/rob/Downloads/Complete/

Shell: Select all

filebot -find /home/rob/Downloads/Complete/

[fontalamh]

Thanks
The command got truncated, it is:

Shell: Select all

filebot -script fn:amc "/home/rob/Downloads/Complete/" --output "/mnt/incoming/" --action move -non-strict --log-file amc.log --def excludeList=amc.txt --def clean=y --def deleteAfterExtract=y --def unsorted=y

I cleared the amc.tx Exclude List because I was re-moving files, tried a fresh folder and it worked - I emptied the original folder of video files and then re-added some to test and it worked fine.

So it looks like it just didn't like something in the folder.

I'll test with untamed files now but it's looking good.

thanks again!

[rednoah]

Hard to say. Most likely an exclusive read/write lock on some folder or file being held by some other process, so FileBot had to wait. Let me know if it happens again. You can do kill -3 <PID> to send a signal to the process and have it dump all the stack traces so that we can see where it's stuck at that point in time.