Troubleshooting Guide
Resolve SSDEEP Tasks in Hangfire
3 min
when your ssdeep tasks are taking longer to process (up to over 24 hours), and you receive errors like this one from the hangfire page you may have also attempted to drop the hangfire jobgraph collection db hangfire jobgraph drop() but that still does not resolve the issue then you will need to modify the loopback time in the python integration script the loopback time is used to create a record filter then a “for loop” will run through the filter and process the data if there are thousands of records that come up in the search filter, this may cause the task to be stuck in a loop for hours, causing a huge queue the loopback time variable is set to 24 hours (1 day) by default set this to fewer hours, like between 1 and 12 hours then, comment out the lines for deduped email and tracking id lines in the fuzzymatch at times, depending on what you get from the logs, you may need to comment out the lines for not eq for deduped email and tracking id mongo profiler logs indicate that using the not eq boolean was causing the indexing to fail and was slowing mongo lookup in the records in hangfire, causing a huge processing queue comment the lines out and replace both lines with the “for loop” statements below limiting the sleep times in the code should help the overall performance, as well update all sleep timer in the code to sleep for less than 3 seconds the default may be (0, 3) which will indicate sleep between 0 and 3 seconds reduce all to (0 5, 1)