Two small bugs in Webinterface 1.3.0

[Silicon]

Hi emcodem
No, you did not. Since I have started webinterface in "log capture" mode, it is working coreectly. Curious

[emcodem]

it knows you are watching, like a VW car

maybe it is about something special you need to do on the interface to make it go mad?

[Silicon]

Maybe, but I don't have a clue what magic I should perform to make it mad. Both previous occurances were spontaneous if I remember it correctly.

[Silicon]

Hi emcodem
Update: I have switched webinterface back from "log capture" to normal mode 2 weeks ago and since then it is working correctly

[Silicon]

Hi @emcodem
I think we have identified the root cause of the issue - as you've predicted in your response from July 12, it is caused by "file with a special filename". I'll PM you the API call response dump you've requested earlier.
Now we need to find out who is to blame for creating file names with strange characters.

[emcodem]

Thanks a lot for the infos Silicon.
Well in first place, characters shouldnt matter at all. It is also not yet 100% clear if the problem is really related to a special char or if it's more like a concurrency issue where multiple jobs want to write into ffastrans log.txt (monitor log) simultanous.
Anyway, i catch this issue now in newest release of webinterface and bring up an alert box that tells you to delete the ffastrans job log in ffastrans status monitor and restart ffastrans service to come around the problem.
On ffastrans side we are also taking multiple actions that should prevent this problem to happen again. We most likely end up by just skipping the one affected job but anything is better than it's now. Of course this will only be available in the next ffastrans release early next year or such.