Two small bugs in Webinterface 1.3.0
Re: Two small bugs in Webinterface 1.3.0
Hi emcodem
I have installed new binary "server.exe" again and I'm awaiting a new occurence.
There is another strange thing about it: when I've opened the webinterface (after the servive restart with new binary installed) a job from ancient history has appeared in the "Running jobs" list in Incomming state. Data-line of this job is not included in "jobs" file so I wonder where it came from
I have installed new binary "server.exe" again and I'm awaiting a new occurence.
There is another strange thing about it: when I've opened the webinterface (after the servive restart with new binary installed) a job from ancient history has appeared in the "Running jobs" list in Incomming state. Data-line of this job is not included in "jobs" file so I wonder where it came from
- Attachments
-
- Ancient history job.PNG (13.09 KiB) Viewed 4648 times
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Re: Two small bugs in Webinterface 1.3.0
Hey Silicon,
Hehe you should have seen that in earlier webinterface versions too but incoming jobs were broken for a long time and i didnt notice because i dont really use inbuilt watchfolder functionality. They work since webint V 1.3.1.
When the state is Incoming, it means that no job has been started yet for this file, but the file has been "seen" by some watchfolder and the watchfolder is waiting for it to grow or it is waiting until enough slots are free to finally queue the file into job queue (yes, watchfolders have their own "queue", they do not want to overload the real job queue).
However, if a file is stuck in incoming, it mostly means that you disabled or deleted a watchfolder while it had incoming files (i believe), and ffastrans did not clean up the db directory accordingly.
So you can get rid of this file by just deleting the corresponding .json file in some \i\ subfolder under here, search for some part of the filename *mpeg* or such:
..ffastrans_dir\Processors\db\cache\wfs
Basically i know that this can be confusing but i decided that i want to show that something is fishy with the files in the DB directory so administrators have the chance to keep it clean. Maybe at some point in future @admin adds the needed cleanup functionailty into the core software.
But what about the last issue you posted, were you able to check the history api call and confirm what i asked?
Hehe you should have seen that in earlier webinterface versions too but incoming jobs were broken for a long time and i didnt notice because i dont really use inbuilt watchfolder functionality. They work since webint V 1.3.1.
When the state is Incoming, it means that no job has been started yet for this file, but the file has been "seen" by some watchfolder and the watchfolder is waiting for it to grow or it is waiting until enough slots are free to finally queue the file into job queue (yes, watchfolders have their own "queue", they do not want to overload the real job queue).
However, if a file is stuck in incoming, it mostly means that you disabled or deleted a watchfolder while it had incoming files (i believe), and ffastrans did not clean up the db directory accordingly.
So you can get rid of this file by just deleting the corresponding .json file in some \i\ subfolder under here, search for some part of the filename *mpeg* or such:
..ffastrans_dir\Processors\db\cache\wfs
Basically i know that this can be confusing but i decided that i want to show that something is fishy with the files in the DB directory so administrators have the chance to keep it clean. Maybe at some point in future @admin adds the needed cleanup functionailty into the core software.
But what about the last issue you posted, were you able to check the history api call and confirm what i asked?
emcodem, wrapping since 2009 you got the rhyme?
Re: Two small bugs in Webinterface 1.3.0
Hi emcodem
Thanks for hint - I've found the coresponding json file in \i\ subfolder and have deleted it.
As for your question: to be honnest I don't understand what do you mean by "file with a special filename".
Update: so far the new version of Webinterface is working correctly since yesterdays installation.
Thanks for hint - I've found the coresponding json file in \i\ subfolder and have deleted it.
As for your question: to be honnest I don't understand what do you mean by "file with a special filename".
Update: so far the new version of Webinterface is working correctly since yesterdays installation.
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Re: Two small bugs in Webinterface 1.3.0
Great, well at some point in time i should maybe support "cancelling" incoming jobs too, i didn't yet because they would re-appear if the watchfolder decides so. Anyway it would be a good feature just to be able to get rid of old incoming files i guess.
"file with a special filename"
As you said you just don't see newly finished jobs, i was wondering if they are in the database but there is something fishy with the presentation, so i thought you just submit a file with a unique name like "abc123" which you can then search in the webinterface history. This way you would see if it actually IS in the database but the sorting or similar does not display the file.
Anyway, if it works now no need to debug anything
"file with a special filename"
As you said you just don't see newly finished jobs, i was wondering if they are in the database but there is something fishy with the presentation, so i thought you just submit a file with a unique name like "abc123" which you can then search in the webinterface history. This way you would see if it actually IS in the database but the sorting or similar does not display the file.
Anyway, if it works now no need to debug anything
emcodem, wrapping since 2009 you got the rhyme?
Re: Two small bugs in Webinterface 1.3.0
Well, I have bad news for you ... the issue is back again
Since 13:07 finsihed jobs are no falling down to bottom list in WebInterface. But FFAStrans native Status monitor both the app and the webpage are showing them normally. See screenshots.
As far as I can judge the filenames of jobs , which are visible in Status monitor, but invisible in webinterface, are quite normal.
Since 13:07 finsihed jobs are no falling down to bottom list in WebInterface. But FFAStrans native Status monitor both the app and the webpage are showing them normally. See screenshots.
As far as I can judge the filenames of jobs , which are visible in Status monitor, but invisible in webinterface, are quite normal.
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Re: Two small bugs in Webinterface 1.3.0
Screenshots ...
- Attachments
-
- FFAStrans Status monitor web_220713_1353.png (70.53 KiB) Viewed 4605 times
-
- FFAStrans Status monitor app_220713_1306.png (30.89 KiB) Viewed 4605 times
-
- FFAStrans WebInterface_220713_1353.png (137.8 KiB) Viewed 4605 times
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Re: Two small bugs in Webinterface 1.3.0
Great screenshot, thanks!
As i cannot reproduce, could you please send the a from webinterface? You know, just stop the webint service, start commandline:
c:\webinterface\server.exe > c:\temp\log.log
And wait until a job finished and is not showing on the webint gui. then stop server.exe and send me the logs please
As i cannot reproduce, could you please send the a from webinterface? You know, just stop the webint service, start commandline:
c:\webinterface\server.exe > c:\temp\log.log
And wait until a job finished and is not showing on the webint gui. then stop server.exe and send me the logs please
emcodem, wrapping since 2009 you got the rhyme?
Re: Two small bugs in Webinterface 1.3.0
Done.
Don't you want to capture error output (currently written to CMD window only) to other file as well?
Don't you want to capture error output (currently written to CMD window only) to other file as well?
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Re: Two small bugs in Webinterface 1.3.0
sorry, stdout and stderr would be fine
server.exe 2>&1 > c:\temp\log.log
server.exe 2>&1 > c:\temp\log.log
emcodem, wrapping since 2009 you got the rhyme?
Re: Two small bugs in Webinterface 1.3.0
@Silicon did i miss anything here?
emcodem, wrapping since 2009 you got the rhyme?