So i been trying to find info what this does and i cant find any.,

I know it indexes, but how does it benefits a user?

On windows i have indexing and it benefits search

But how does running index on unraid can benefit a remote windows PC? or this program is only to index the unraid and than use it on linux VM?

 

 

Thanks

 

Quote

Using diskover, users can identify old and unused files and give better insights into data change, file duplication and wasted space. diskover supports crawling local file-systems, crawling NFS/SMB, cloud storage, etc. Plugins can be used for adding additional meta data.

 

 "Unable to connect to Elasticsearch host elasticsearch:9200. Error: Could not resolve host: elasticsearch"
Has anyone solved this? 

On 4/28/2023 at 8:37 PM, Cyborg said:

 "Unable to connect to Elasticsearch host elasticsearch:9200. Error: Could not resolve host: elasticsearch"
Has anyone solved this? 

This was solved by replacing elasticsearch with actual ip in installation template. 

Hello guys!

 

I finally get the Diskover running on my unraid, i used to index my /music share.

 

Its working, but when i try to type anything on diskover search bar the result screen shows like this:

 

the files are there but not displayed, its a bug? or may be i did something wrong?

 

 

 

I am using the docker images from the APPs of Unraid.

 

All latest version.

 

When i search from the status page, the results appears but, if i click to browse the results, nothing happens like the above image...

 

 

Any help or tip are welcome!

 

Thanks in advance!

 

Just installed diskover and elastic search (5.6.16).

 

Logging in with "diskover" and "darkdata" gives a wrong userid or password message...

 

What could be wrong ?

 

I do not see anything specific in the logs...

13 hours ago, Helmonder said:

Just installed diskover and elastic search (5.6.16).

 

Logging in with "diskover" and "darkdata" gives a wrong userid or password message...

 

What could be wrong ?

 

I do not see anything specific in the logs...

seems like time was the issue.. this morning i can logon.. its asking me to start a crawl... now to find out how that step works 🙂

Quick PSA: I started getting the following error when trying to start an index

There was an error connecting to the database! unable to open database file

and fixed it by adding an additional env var to the container:

DATABASE: /config/diskoverdb.sqlite3

Ref: Github

Edited September 2, 20241 yr by fmeres

Anyone around here still?

Just installed Diskover (2.3.0), got Elasticsearch working (finally) and when going to the Diskover UI I get:

No completed indices found in Elasticsearch. Run a crawl and after it finishes reload select indices page.

I did try running docker exec -u abc -d diskover python3 /app/diskover/diskover.py /data but nothing seems to happen...

Any ideas?

On 10/13/2025 at 12:46 AM, Krakout said:

Anyone around here still?

Just installed Diskover (2.3.0), got Elasticsearch working (finally) and when going to the Diskover UI I get:

No completed indices found in Elasticsearch. Run a crawl and after it finishes reload select indices page.

I did try running docker exec -u abc -d diskover python3 /app/diskover/diskover.py /data but nothing seems to happen...

Any ideas?

I just had to do a new index since it's been a few years. I'm assuming you're running this from UnRaid Docker?

Anyway, did you run the command from the docker itself? When selecting diskover I select ">_Console" from the dropdown. Then I run the following command "python3 /app/diskover/diskover.py -i [Your Index Name] /data -f".

Since it's running inside the container you can drop the previous commands. The "-f" is if you already have an index and need to force an overwrite. This worked for me this morning.

I'm also a little Sad Panda that it seems so quite around here. Is DiskOver dying or dead? I hope not.

Anyway, I'd like to know how it works out for you .

Edited October 26, 2025Oct 26 by mattm1121

17 hours ago, mattm1121 said:

I just had to do a new index since it's been a few years. I'm assuming you're running this from UnRaid Docker?

Anyway, did you run the command from the docker itself? When selecting diskover I select ">_Console" from the dropdown. Then I run the following command "python3 /app/diskover/diskover.py -i [Your Index Name] /data -f".

Since it's running inside the container you can drop the previous commands. The "-f" is if you already have an index and need to force an overwrite. This worked for me this morning.

I'm also a little Sad Panda that it seems so quite around here. Is DiskOver dying or dead? I hope not.

Anyway, I'd like to know how it works out for you .

Thanks for your help, much, much appreciated!

Reading your command it appears you have to have an index ([Your Index Name]) already there, but I don't...

Running the command without an index name gives me:

(doesn't matter)

EDIT: yeah I'm stupid, that's what actually creates the index. However, I'm getting this - doesn't look too good...

root@74e29f1775e9:/# python3 /app/diskover/diskover.py -i diskover-nas /data
/app/diskover/diskover.py:912: SyntaxWarning: invalid escape sequence '\ '
  / ` | / _| |/ /  \ \ / /  \ '__| /)___(\\
            _ _     _                       
           | (_)   | |                      
         __| |_ ___| | _______   _____ _ __ 
        / ` | / _| |/ /  \ \ / /  \ '__| /)___(\
       | (_| | \__ \   < (_) \ V /  __/ |    (='.'=)
        \__,_|_|___/_|\_\___/ \_/ \___|_|   (\")_(\")
            "Bringing light to the darkness."
            v2.3.1 community edition (ce)
            https://diskoverdata.com
    
2025-10-27 09:46:11,567 - diskover - INFO - Creating index diskover-nas...
2025-10-27 09:46:11,575 - elasticsearch - WARNING - PUT http://10.0.0.100:9200/diskover-nas [status:400 request:0.007s]
2025-10-27 09:46:11,575 - diskover - CRITICAL - FATAL ERROR: an exception has occurred: RequestError(400, 'mapper_parsing_exception', 'Root mapping definition has unsupported parameters:  [end_at : {type=date}] [extension : {type=keyword}] [free_percent : {type=float}] [available : {type=long}] [used : {type=long}] [mtime : {type=date}] [start_at : {type=date}] [type : {type=keyword}] [diskover_ver : {type=keyword}] [size_du : {type=long}] [path : {type=keyword}] [crawl_time : {type=float}] [dir_count_norecurs : {type=long}] [total : {type=long}] [size_norecurs : {type=long}] [file_count_norecurs : {type=long}] [ctime : {type=date}] [parent_path : {type=keyword, fields={text={analyzer=path_analyzer, type=text}}}] [free : {type=long}] [group : {type=keyword}] [file_count : {type=long}] [owner : {type=keyword}] [atime : {type=date}] [available_percent : {type=float}] [nlink : {type=integer}] [size_du_norecurs : {type=long}] [ino : {type=keyword}] [file_size_du : {type=long}] [file_size : {type=long}] [size : {type=long}] [name : {type=keyword, fields={text={analyzer=filename_analyzer, type=text}}}] [dir_depth : {type=integer}] [dir_count : {type=long}]')
Traceback (most recent call last):
  File "/app/diskover/diskover.py", line 1205, in <module>
    create_index(options.index, es)
  File "/app/diskover/diskover_elasticsearch.py", line 297, in create_index
    es.indices.create(index=indexname, body=mappings)
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/client/utils.py", line 168, in _wrapped
    return func(*args, params=params, headers=headers, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/client/indices.py", line 123, in create
    return self.transport.perform_request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/transport.py", line 415, in perform_request
    raise e
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/transport.py", line 381, in perform_request
    status, headers_response, data = connection.perform_request(
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/connection/http_urllib3.py", line 277, in perform_request
    self._raise_error(response.status, raw_data)
  File "/lsiopy/lib/python3.12/site-packages/elasticsearch/connection/base.py", line 330, in raiseerror
    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
elasticsearch.exceptions.RequestError: RequestError(400, 'mapper_parsing_exception', 'Root mapping definition has unsupported parameters:  [end_at : {type=date}] [extension : {type=keyword}] [free_percent : {type=float}] [available : {type=long}] [used : {type=long}] [mtime : {type=date}] [start_at : {type=date}] [type : {type=keyword}] [diskover_ver : {type=keyword}] [size_du : {type=long}] [path : {type=keyword}] [crawl_time : {type=float}] [dir_count_norecurs : {type=long}] [total : {type=long}] [size_norecurs : {type=long}] [file_count_norecurs : {type=long}] [ctime : {type=date}] [parent_path : {type=keyword, fields={text={analyzer=path_analyzer, type=text}}}] [free : {type=long}] [group : {type=keyword}] [file_count : {type=long}] [owner : {type=keyword}] [atime : {type=date}] [available_percent : {type=float}] [nlink : {type=integer}] [size_du_norecurs : {type=long}] [ino : {type=keyword}] [file_size_du : {type=long}] [file_size : {type=long}] [size : {type=long}] [name : {type=keyword, fields={text={analyzer=filename_analyzer, type=text}}}] [dir_depth : {type=integer}] [dir_count : {type=long}]')
2025-10-27 09:46:11,577 - diskover - CRITICAL - CRITICAL ERROR, DELETING INDEX AND EXITING

Edited October 27, 2025Oct 27 by Krakout
typo

Just went through this after many years of running Elastic v5.x
Now running Diskover v2.3.3 with ElasticSearch (Official template) on v8.19.7.
Some notes...

• I had to chmod 777 -Rmy appdata/discover folder to get it to create an active node, 775 didn't work

• Don't forget to chown -R 1000:0 /mnt/user/appdata/elasticsearch/data

• I'm running a macvlan custom bridge, so ES_HOST needed to get updated in the web settings since it didn't seem to come over from the compose template? localhost doesn't work in this instance, as I would have expected.

• Had to configure the elastic user with a password even though I set an env var ELASTIC_PASSWORD using the command line password change ./elasticsearch-reset-password -u elastic -i ... from there the ES_USER and ES_PASS were set in the web settings.

• HTTPS was enabled by default on port 9200

• In my case, I'm not internet facing at all with this setup, so ES_HTTPS was set true with ES_SSLVERIFICATION set false

• I also had to start my index from the docker shell: python3 /app/diskover/diskover.py -i diskover-[crawlindexname] /data

And with that, I'm off to the races. HTH someone.