Closed packet1 closed 3 years ago
Looks like a bug alright. I'll take a look at that later today / tonight. Apologies!
I don't suppose you could supply the journal file that EDScout was processing when that error occurred? Would help me replicate the issue potentially 👌🏻
Nothing displaying for me either. Only thing I can provide is the text from the debug.log: [0124/212901.604:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)
EDScout-2021-02-27-00-56-52.log EDScout-2021-02-27-00-53-39.log EDScout-2021-02-27-00-49-55.log EDScout-2021-02-27-00-49-02.log EDScout-2021-02-27-00-48-00.log EDScout-2021-02-27-02-14-01.log EDScout-2021-02-27-02-09-40.log EDScout-2021-02-27-02-05-53.log EDScout-2021-02-27-02-02-32.log EDScout-2021-02-27-01-37-43.log EDScout-2021-02-27-01-31-19.log EDScout-2021-02-27-01-01-41.log EDScout-2021-02-27-00-58-05.log
Here are my journals from last night
Why do I see a request against port 5001? I run EDscout on port 333.
Why do I see a request against port 5001? I run EDscout on port 333.
5001 is a keepalive channel which is suppoed to ensure that if the web front end is closed, that the backend also closes down.
I see. LMK if you need any more logs, etc.
Found the problem - stupid oversight on my part (should have tested with some unmapped systems!). Will be fixed in 1.8.1
Thanks, Jon!
I'm running with the CLI web server option and I don't see any data on the local GUI or the webserver