Brandon Langley

Troubleshooting — Windows (Task Worker)OverviewOn Windows, Diskover runs only the Task Worker (diskoverd). The full Diskover stack (Elasticsearch, nginx, diskover-admin, diskover-web) must be runni...

Troubleshooting — Scan TasksOverviewA Diskover scan (crawl) is initiated by diskoverd, which launches diskover.py as a subprocess. The crawler walks a directory tree (or alternate storage backend),...

Troubleshooting — RabbitMQOverviewRabbitMQ is the message broker for the Diskover platform. It acts as the communication layer between diskover-admin (which submits jobs) and the Celery workers run...

Troubleshooting — Diskover on RHEL / Rocky / CentOSOverviewRHEL, Rocky Linux, and CentOS hosts can run the full Diskover stack or act as dedicated indexer nodes. This guide covers the most common ...

Troubleshooting — KibanaOverviewKibana is the web-based UI for Elasticsearch. For Diskover, its primary use is Index Lifecycle Management (ILM) — defining advanced policies that automatically manag...

Troubleshooting — ElasticsearchOverviewElasticsearch is the search and analytics engine at the core of the Diskover platform. Every file and directory crawled by Diskover is stored as a document in...

Troubleshooting — Diskoverd Task-WorkerOverviewDiskoverd is the Diskover worker daemon. It runs on each indexer host and is responsible for:Receiving and executing crawl tasks — accepts jobs from t...

Troubleshooting — Diskover-AdminOverviewdiskover-admin is the Python-based administrative backend for the Diskover platform. It serves two roles:Admin UI — configuration management, task management...

Troubleshooting — CeleryOverviewCelery is the distributed task queue that powers Diskover's background processing. It runs as a worker service on each indexer machine and is responsible for executi...

Importing the OVADiskover provides identical OVA builds for both VMWare Workstation and VirtualBox. These OVAs can easily be imported into either of these hypervisors and booted up to run Diskover!...