Skip to content

CrackQ Queuing System Explained

f0cker edited this page Nov 10, 2020 · 15 revisions

The Queue System

Docker Diagram

CrackQ uses Redis for queuing, there are currently 3 queues:

  • default - This is the main queue which you see in the GUI.
  • speed_check - This is a hidden queue which runs as soon as a job is added to the main queue. It triggers a pause operation in the main queue while it performs a *show* check and a *speed_only* check on the new job. This information is then used to provide cracked hashes from the profile immediately and also to make the decision on whether or not to use enable the brain. An ETA estimation will likely be added to this in future to help organise jobs for better efficiency.
  • reports - This queue handles the processing of a password analysis report request.
There will be at least one additional queue included at a future date to handle low priority jobs that should only crack during idle time.

If you ever experience any unexpected issues with the queuing, the best workaround is to disable the brain during job creation.

The Job Life-cycle


Further Notes