OFark

This didn't do anything for me, I still the 504. Heres how I installed ElasticSearch: docker pull docker.elastic.co/elasticsearch/elasticsearch:5.6.9 docker create --name="Elasticsearch-5.6.9" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "discovery.type"="single-node" -e "ES_JAVA_OPTS"="-Xms512M -Xmx512M" -p 9200:9200/tcp -v "/mnt/cache/appdata/elasticsearch5/data":"/usr/share/elasticsearch/data":rw --ulimit nofile=262144:262144 25482cbfd71b Diskover was from CA, modified in this way: docker run -d --name='diskover' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'REDIS_HOST'='192.168.1.51' -e 'REDIS_PORT'='6379' -e 'ES_HOST'='192.168.1.51' -e 'ES_PORT'='9200' -e 'ES_USER'='elastic' -e 'ES_PASS'='changeme' -e 'INDEX_NAME'='diskover-' -e 'DISKOVER_OPTS'='' -e 'WORKER_OPTS'='' -e 'RUN_ON_START'='true' -e 'USE_CRON'='false' -e 'PUID'='99' -e 'PGID'='100' -p '9181:9181/tcp' -p '9999:9999/tcp' -p '8080:80/tcp' -v '/mnt/user/appdata/diskover':'/config':'rw' -v '/mnt/user/Stuff/':'/data':'rw' 'linuxserver/diskover'

I've found the logging under /mnt/user/appdata/diskover/log/ under nginx/error/log is the following two lines: 2018/11/23 14:13:09 [error] 334#334: *20 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.1.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.51:8080", referrer: "http://192.168.1.51/Docker" 2018/11/23 14:14:09 [error] 334#334: *20 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.1.1, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.51:8080" I'm not sure what 127.0.0.1:9000 is pointing to, I don;t see any ports open in unRAID for 9000. Maybe thats not an issue.

Ok, so I've got the index in ElasticSearch. The /mnt/user/appdata/diskover/diskcover.cfg wasn't matching the options in the diskover container. Basically, the hostnames were names rather than IP addresses. That fixed - Kibana is now showing data. Not brilliant for files but I can see data and I can see regular indexing. Diskover web is still showing 504 Bad gateway.

For what it's worth I have Kibana working just fine. Although I don't have any index's yet, just *. Looks like what Diskover does is add drive data to ElasticSearch, so when I specify an index name prefix "diskover-" that isn't supposed to already exist, is it? I've not done anything with ElasticSearch, not configured it in any way. Kibana can't see a diskover-* index.

I was wondering. Still, I've added that now. No more Warn's. Still no page. Gateway 504 Error still. I've had a look in the /mnt/user/appdata/diskover/diskover.cfg and I switched the worker bot logging to 'True', left it pointing to /tmp. Can't see any logs relating. (thanks for your help so far btw)

No the other error is still there: [2018-11-22T17:13:33,802][WARN ][o.e.b.BootstrapChecks ] [XDTClyG] max file descriptors [40960] for elasticsearch process is too low, increase to at least [65536] I tried whaty I thought might change this value, based on the other one in the readme, alas it did not work. I shall try upgrading elasticsearch now.

Ok, so I did think the readme was the right thing, I'm not sure what link I followed but the page I remember was black, with screenshots. However I have now seen that readme, and I've added the sysctl -w vm.max_map_count=262144 option, and that warn has gone. But I'm still getting a 504 bad gateway on 8080. The Diskover log never mentions port 8080, or 80 (I have checked the port is mapped 8080 -> 80), it mentions 9999 and 9181 but not 80 or 8080.

Forgive me I thought I had read the readme. When people say readme and Github I THINK they are referring to the text that Github displays by default. Is there another readme file? Thanks for the info on the vm.max_map_count.

So I'm not getting a response on 8080. Gateway timeout. On :9181 I get the RQ dashboard (no workers or jobs listed) On :9200 I get JSON from the Elasticsearch: name "XDTClyG" cluster_name "docker-cluster" cluster_uuid "rzwTHQOTQNuM32hC1wReCg" version number "5.6.3" build_hash "1a2f265" build_date "2017-10-06T20:33:39.012Z" build_snapshot false lucene_version "6.6.1" tagline "You Know, for Search" The unRAID Docker logs for elasticsearch have two WARN about memory allocation not being big enough: "[2018-11-22T12:43:29,079][WARN ][o.e.b.BootstrapChecks ] [XDTClyG] max file descriptors [40960] for elasticsearch process is too low, increase to at least [65536]" "[2018-11-22T12:43:29,079][WARN ][o.e.b.BootstrapChecks ] [XDTClyG] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]" Not sure how to change that, but it's a warn so I'm kinda ignoring it. The log for Diskover shows no errors or warnings, other than about dev on production. I'm not sure where to look for any other issues, I have checked the logs, Redis gives me a terminal, but I have no idea what it does or how to check it, but it's alive, Elasticsearch is alive, all ports and addresses (direct IP) are correct. Still all I get is a Gateway timed out. Can't find any mention of unraid on the Diskover Github page. Please help.