[EPIC] Agent error handeling and logging

[zyronix]

In case an agent crashes you want that the agent is not marked instantly as failed. Because this sometimes can happen based on user parameters, eg bad hashcat command. If agents fails, move it to the next task if another agent also fails on the same task fail the task and not the agent.

Also you want a bit more clientside logging what failed, maybe catch some of the errors of hashcat?

• [ ] #746

[zyronix]

From #537

Server Publishing task, if there is an unforeseen error, the client will be incorrectly exited, whether the error can be returned to the server to write to the log, skip this wrong task to continue to perform the following tasks. Because in the case of 8 clients or more, it is depressing to need to adjust the task level or delete the task, and then restart all clients, if an unforeseen error is encountered.

[zyronix]

From #692

For some unknown reason the downloaded cracker binary got locked which caused the agent to die: (either antivirus or something was keeping 7za.exe in the process list forever, killing it resolved the issue)

EG: If either the agent itself or some other application is causing some locking in any of the files. How should the agent handle this?