Data Retention and Cleanup

Data Retention and Cleanup

HashTasker cleans up after itself. Nothing here needs a cron job.

Server

Task	When	What it does
Job auto-delete	10s after startup, then every 12 hours	Deletes jobs older than 45 days with their results and files. Analytics records are kept.
Orphaned file cleanup	20s after startup, then hourly	Removes files in upload_path that belong to jobs that no longer exist
Orphaned record cleanup	Every startup	Removes chunk, progress, and cracked-hash rows whose job is gone
Job file cleanup	When a job completes, fails, or is cancelled	Removes its chunks, uploaded custom wordlist, and generated potfile
Worker offline check	Every 60 seconds	Marks workers that have not checked in for 60s as offline
NFS health check	Every 30 seconds	Checks wordlists_path is readable
Wordlist count warmer	NFS mode: 30s after startup, then hourly	Caches line counts for up to 2 new/changed wordlists per cycle

Worker

Workers delete the hash file, downloaded chunk, custom wordlist, and potfile for a job when it ends, and periodically prune their in-memory record of finished jobs.

Never Deleted

• Anything in the shared NFS wordlist directory
• Anything in wordlists_path or rulesets_path
• Analytics (unless an admin clears it)

Backups

Everything that matters is in hashtasker.db. Stop the server (or accept a crash-consistent copy) and copy the file:

sudo systemctl stop hashtasker-server
cp /opt/HashTaskerGo/hashtasker.db /backup/hashtasker-$(date +%F).db
sudo systemctl start hashtasker-server