Webinterface

[artjuice]

Hi emcodem,

But man, really, you got 30 gig ram usage from job json file caching in a few days? How many jobs you run through every day?

It's about 300-500 files per day.

@artjuice regarding "multiple systems in shown in one webint", this is the first version that attempts to do this. In network config, you can supply multiple "API Hosts", each of it must be an installation of webinterface. E.g. if you have multiple ffastrans systems, you install at least one webint per installation and set the list of webint hostnames in API Hosts like: host1,host2,host3...

Wow, such a great news!!!
Thx!

[DCCentR]

@DCCentR thanks again for all the insights you provided on the hanging running job display issue. After reviewing everyghing we were still not certain about the details how it came into this situation. However steinar implemented something that should workaround the problems. After all its just a matter about how ffastrans deals with concurrent file access in the /db folder and there are many solutions for one problem possible Not sure if he will or can deliver a patch for 1.4.0.7 version so you can verify the solution @admin, what you think'?

I'm willing to test the fix if it's done

BTW some more observations on my issue, task hangs also happen on other worflows (also on Custom FFmpeg processors). All hung tasks were executed on the same NAS09 server.
I looked up what might be wrong with this server and remembered that the directory with FFAStrans was originally sharded from it. Then I moved the directory (with same name "FF_Install") to SRV-CINEGY1 without turning off the network share of the original folder (it's empty) on NAS09.
I deleted this folder on NAS09 and turned off network share and the current stuck jsons in the monitor directory disappeared immediately
I don't see how this could be related - but it helped with stuck tasks at this time, maybe some residual information about network folders in Windows

I'll continue my observations.

[emcodem]

I deleted this folder on NAS09 and turned off network share and the current stuck jsons in the monitor directory disappeared immediately
I don't see how this could be related - but it helped with stuck tasks at this time, maybe some residual information about network folders in Windows

Thank you so much for keeping an eye on it!
Very intersting that it was always NAS09 that might have initiated the faulty behaviour. What you describe about disabling the share and the locked files disappearing feels kind of scary but if one day we understand why it will for sure be of great help.
Of course unfortunately from what you describe nobody can currently make any sense of it but maybe we finally have finally found the first breadcrumbs for what's the real cause?
Let's see if now after you disabled the share on nas09 we still see the blocked monitor json files...