FFAStrans farm creates unwanted json trace files

[Kris]

Hey everyone,

recently some of our workstations in our FFAStrans farm started creating json-files in an unwanted location on our server.
Unfortunately I dont know what these files are and where to change the file path.

Please find two examples of those files in the attachment. COMPUTER01 and COMPUTER02 are the names of our workstations.

We are running on FFAStrans version 1.2.0.0 as application.

Please let me know if you can tell me what these files are and where to change the path.

Thanks and best regards
Kris

[emcodem]

Hey Kris, that is very interesting... could you maybe share the affected workflow too please?

[Kris]

It doesn't seem to be one specific workflow.
If I disable all workflow it still keeps on creating these files. Only when I stop the application the files stop.

[emcodem]

Oh wow, that's interesting. Now i just searched but couldn't find any unwanted trace json's anywhere. Can you tell us in which folder you found those files?

[admin]

Hi Kris,

These are actually log files for running jobs but they should go in the FFAStrans\Processors\db\cache\jobs\<wf_id>\log folder. If they're outside of this folder please let me know.

-steinar

[Kris]

Hi Steinar,

they are outside of this folder.
The files are in the root folder of our server.

-Kris

[admin]

Ok, but do you otherwise have a functioning FFAStrans installation? Does the workflows do what is expected or do you have some erratic behavior (besides the log files)?

-steinar

[Kris]

I have been getting those error message as described here:
https://ffastrans.com/frm/forum/viewtop ... f=4&t=1221

I don't know if it is related to those files, but other than that the workflows work as expected.

[Kris]

Also I did a backup of all workflows and deleted them in ffastrans but the log-files keep on coming.
Seems to me that it might not be workflow related.

[Kris]

Hey there,

I have found the source of the problem. I tried running FFAStrans as application and I read in forum that I need to change the processor.a3x file in ffastrans\Applikation\Processors.

I replaced the processor.a3x file again with the one we originally had and now it works fine.

Anyways thank you for your support. I attached the file that was the cause of the problem.