Can I read the error log?
Posted: Fri 25 Sep 2020 3:01 pm
Using 1.9.4 (1099) successfully and have built a Windows processor to capture and process the data files to enhance my web site a bit (such as saving/presenting archives, handling news/events etc)
I can't see how to read the error log. I have the web tags for 'error flag set' and 'last error was' but short of building an outboard log file of those entries, I can't see how to read the error file. Any clue as to where it is, please?
My best guess is ..\Cumulus\Diags\Cumulus.nnn files, where the errors such as FTP timeout are reported but they are hidden in a lot of routine status messages and are difficult to extract. The GUI does it - is it from these files or another tucked away somewhere?
Thanks for any leads/ideas
John
PS After experimenting, I found that shutting down Cumulus, when it has a populated error list, results in those errors being forgotten. It suggests, to my mind, that the GUI error log screen is therefore held in the running program's variables, rather than in an external file. The approach that I'm going to try now is to use AutoIT (a Windows manipulation utility) to screen scrape the open error log at regular intervals. It's very Heath Robinson but I've had success doing this with other Windows programs, so it might be a work around. I'll also try reading the /diag/ files to see if I can extract the info without doing screen scraping.... because that's much tidier...
At least I have the advantage that no-one will fiddle with the Cumulus server - it's a dedicated laptop that's running Cumulus (and my utility) exclusively, folded up, in a cupboard. No sticky fingers!
I can't see how to read the error log. I have the web tags for 'error flag set' and 'last error was' but short of building an outboard log file of those entries, I can't see how to read the error file. Any clue as to where it is, please?
My best guess is ..\Cumulus\Diags\Cumulus.nnn files, where the errors such as FTP timeout are reported but they are hidden in a lot of routine status messages and are difficult to extract. The GUI does it - is it from these files or another tucked away somewhere?
Thanks for any leads/ideas
John
PS After experimenting, I found that shutting down Cumulus, when it has a populated error list, results in those errors being forgotten. It suggests, to my mind, that the GUI error log screen is therefore held in the running program's variables, rather than in an external file. The approach that I'm going to try now is to use AutoIT (a Windows manipulation utility) to screen scrape the open error log at regular intervals. It's very Heath Robinson but I've had success doing this with other Windows programs, so it might be a work around. I'll also try reading the /diag/ files to see if I can extract the info without doing screen scraping.... because that's much tidier...
At least I have the advantage that no-one will fiddle with the Cumulus server - it's a dedicated laptop that's running Cumulus (and my utility) exclusively, folded up, in a cupboard. No sticky fingers!