Ignoring corrupted log zips

Avatar
Steve Sommers
  • updated
  • Under review
In the scheduler, or anywhere for that matter, is there a way to skip over corrupt zip files and log or email the file that was skipped?

I'm analyzing a cluster of servers and the process takes about two hours to complete. Every now and then I get a corrupted zip in the mix where my daily logs reside and this terminates the entire process. I do not know of this until people start complaining about the missing reports. Completing the report and possibly emailing me the skipped log zips would be a great feature.
Replies 4
Avatar
0
Michael
We are aware of a problem with empty zip files, we are going to fix it in the next version of the program (so these empty zips will be ignored). Do you have the problem with empty zips too, or are there non-empty corrupted zip files that appear in your case?
Avatar
0
Steve Sommers
To answer your question: Yes. Most of the issues I was dealing with were actually corrupted zip files where opening them up with WinZip generated an error. There was one however that was simply an empty zip file and I was surprised to see that that generated an identical premature termination.
Avatar
0
Steve Sommers
In the original question I meant to say "log or email the file name that was skipped", not the actual zip file.
Avatar
0
Michael
Thank you for the clarification. We are going to fix the issue with the empty ZIPs in the next version and we'll consider adding an option to ignore corrupted ZIPs.

Customer support portal powered by UserEcho