flyersweb / dhtbay Goto Github PK

View Code? Open in Web Editor NEW

106.0 10.0 18.0 149 KB

A DHT crawler and torrent indexer

License: The Unlicense

JavaScript 97.59% Dockerfile 1.16% Shell 1.25%

torrent dht-crawler javascript aria classifier torrent-indexer docker

dhtbay's People

Contributors

Stargazers

Watchers

Forkers

bhgraham ppproxy duramato kurttomlinson cornboy jongt ishan-marikar skyle97 dinkin rockrockyy t-web totaldesigner frogfork dimatter virloma bdw4bdw la0wei

dhtbay's Issues

More .torrent file sources

Add the possibility to add via a config file, ideally, more sources to download .torrents.
They could be added as they are atm to the config file http://torcache.net/torrent/{DHTHASH}.torrent , so that despite the format the only part that would change would be the DHTHASH, so it could even be http://mydomain.com/download/torrent/{DHTHASH}

question: is there a web ui to see the torrents?

I see the torrents are in MongoDB but I need a REST API to integrate with 3rd party apps like Jackett.
Jackett/Jackett#2684

docker-compose up -d broken.

logs:

MongoError: failed to connect to server [mongo:27017] on first connect [MongoError: connect ECONNREFUSED 172.18.0.3:27017]

Fails to build bitcannon

I'm trying to run bitcannon on docker, but i'm getting:

ngInfiniteScroll#1.2.0 bower_components/ngInfiniteScroll
└── angular#1.3.20

angular-animate#1.6.4 bower_components/angular-animate
└── angular#1.3.20

angular-moment#0.9.2 bower_components/angular-moment
├── angular#1.3.20
└── moment#2.9.0

bootswatch-dist#3.3.0-flatly bower_components/bootswatch-dist
└── jquery#3.2.1

angular-loading-bar#0.9.0 bower_components/angular-loading-bar
└── angular#1.3.20

angular#1.3.20 bower_components/angular

es5-shim#4.5.9 bower_components/es5-shim

ui-router#0.2.13 bower_components/ui-router
└── angular#1.3.20

angular-mocks#1.3.20 bower_components/angular-mocks
└── angular#1.3.20

json3#3.3.2 bower_components/json3

angular-scenario#1.3.20 bower_components/angular-scenario
└── angular#1.3.20

fontawesome#4.2.0 bower_components/fontawesome

jquery#3.2.1 bower_components/jquery

moment#2.9.0 bower_components/moment
Running "newer:jshint" (newer) task

Running "newer:jshint:all" (newer) task

Running "jshint:all" (jshint) task

✔ No problems


Running "newer-postrun:jshint:all:1:/var/www/node_modules/grunt-newer/.cache" (newer-postrun) task

Running "newer:jshint:test" (newer) task

Running "jshint:test" (jshint) task

✔ No problems


Running "newer-postrun:jshint:test:2:/var/www/node_modules/grunt-newer/.cache" (newer-postrun) task

Running "clean:server" (clean) task

Running "concurrent:test" (concurrent) task

    Running "copy:styles" (copy) task
    Copied 1 files

    Done, without errors.


    Execution Time (2017-06-26 22:38:31 UTC)
    loading tasks   42ms  ▇▇▇▇▇▇▇▇▇▇▇ 22%
    copy:styles    146ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 77%
    Total 189ms

Running "autoprefixer:dist" (autoprefixer) task
File .tmp/styles/main.css created.

Running "connect:test" (connect) task
Started connect web server on http://0.0.0.0:9001

Running "karma:unit" (karma) task
26 06 2017 22:38:32.454:WARN [watcher]: Pattern "/var/www/test/mock/**/*.js" does not match any file.
26 06 2017 22:38:32.552:INFO [karma]: Karma v1.7.0 server started at http://0.0.0.0:8080/
26 06 2017 22:38:32.553:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
26 06 2017 22:38:32.583:INFO [launcher]: Starting browser PhantomJS
26 06 2017 22:38:38.551:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket bSgnGdmIvJZEH_S_AAAA with id 34189137
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  TypeError: undefined is not a function (near '....info({ angularVersion: '...')
  at bower_components/angular-animate/angular-animate.js:4139


Warning: Task "karma:unit" failed. Use --force to continue.

Aborted due to warnings.


Execution Time (2017-06-26 22:38:14 UTC)
jshint:all       371ms  ▇ 1%
concurrent:test    17s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 69%
karma:unit          7s  ▇▇▇▇▇▇▇▇▇▇▇▇▇ 28%
Total 24.8s

ERROR: Service 'bitcannon_front' failed to build: The command '/bin/sh -c npm install -g bower   && npm install -g grunt-cli   && rm -rf node_modules && rm -rf bower-components && rm -rf dist   && npm install   && bower install --allow-root=true --config.analytics=false --config.interactive=false   && grunt' returned a non-zero code: 3

Other info you may need, please do ask.

Also on a side note: i've opened the issue here becouse issues aren't open on it's repo, don't know if that's intended.

crawlDHT.js never announces

When I run crawlDHT.js, it listens and gets ready, but it never proceeds to the next step. The output I get is below:

dht@dht-VirtualBox:~$ node /home/dht/dhtbay/crawlDHT.js
[Sun, 24 Jul 2016 01:10:32 GMT] { '0': 'now listening' }
[Sun, 24 Jul 2016 01:10:32 GMT] { '0': { address: '0.0.0.0', family: 'IPv4', port: 6881 } }
[Sun, 24 Jul 2016 01:10:37 GMT] { '0': 'now ready' }

Updating thirdparty broke crawler

CrawlDHT.js runs, but the log shows :

Saving peer : [object Object]'

instead of the address itself.

PS: Sometimes there is :

{ '0': 'announce' }
[Wed, 13 Jan 2016 10:47:48 GMT] { '0': '[object Object] : �\u0019K{�Lg&'\nPv��U�$'[p' }

How to correct this ?

Include with BitCannon

I'm not sure of the progress you've had on merging the two but I was able to whip a quick implementation up overnight. I'm sure it could be refined : https://github.com/bglopez/dhtbay/tree/aiodht

docker-compose part doesn't work well

So, I got this log when I'm starting dhtbay:

$ docker-compose up
Starting dhtaria2
Starting redis
Starting mongo
Starting dhtbay
Attaching to mongo, redis, dhtaria2, dhtbay
mongo     | 2018-10-23T08:18:20.726+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=65c2c1d6df88
mongo     | 2018-10-23T08:18:20.727+0000 I CONTROL  [initandlisten] db version v3.0.15
mongo     | 2018-10-23T08:18:20.727+0000 I CONTROL  [initandlisten] git version: b8ff507269c382bc100fc52f75f48d54cd42ec3b
mongo     | 2018-10-23T08:18:20.727+0000 I CONTROL  [initandlisten] build info: Linux ip-10-166-66-3 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 BOOST_LIB_VERSION=1_49
mongo     | 2018-10-23T08:18:20.727+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongo     | 2018-10-23T08:18:20.727+0000 I CONTROL  [initandlisten] options: {}
mongo     | 2018-10-23T08:18:20.739+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal
mongo     | 2018-10-23T08:18:20.739+0000 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
mongo     | 2018-10-23T08:18:21.035+0000 I JOURNAL  [durability] Durability thread started
mongo     | 2018-10-23T08:18:21.035+0000 I JOURNAL  [journal writer] Journal writer thread started
redis     | 1:C 23 Oct 08:18:21.617 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis     |                 _._                                                  
redis     |            _.-``__ ''-._                                             
redis     |       _.-``    `.  `_.  ''-._           Redis 3.2.12 (00000000/0) 64 bit
mongo     | 2018-10-23T08:18:21.168+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
redis     |   .-`` .-```.  ```\/    _.,_ ''-._                                   
dhtaria2  | 
dhtaria2  | 10/23 08:18:22 [WARN] Neither --rpc-secret nor a combination of --rpc-user and --rpc-passwd is set. This is insecure. It is extremely recommended to specify --rpc-secret with the adequate secrecy or now deprecated --rpc-user and --rpc-passwd.
dhtaria2  | 
redis     |  (    '      ,       .-`  | `,    )     Running in standalone mode
redis     |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
dhtaria2  | 10/23 08:18:22 [NOTICE] IPv4 RPC: listening on TCP port 6800
redis     |  |    `-._   `._    /     _.-'    |     PID: 1
dhtaria2  | 
redis     |   `-._    `-._  `-./  _.-'    _.-'                                   
dhtaria2  | 10/23 08:18:22 [NOTICE] IPv6 RPC: listening on TCP port 6800
redis     |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis     |  |    `-._`-._        _.-'_.-'    |           http://redis.io        
redis     |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis     |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis     |  |    `-._`-._        _.-'_.-'    |                                  
redis     |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis     |       `-._    `-.__.-'    _.-'                                       
redis     |           `-._        _.-'                                           
redis     |               `-.__.-'                                               
redis     | 
redis     | 1:M 23 Oct 08:18:21.621 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis     | 1:M 23 Oct 08:18:21.622 # Server started, Redis version 3.2.12
redis     | 1:M 23 Oct 08:18:21.622 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis     | 1:M 23 Oct 08:18:21.622 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis     | 1:M 23 Oct 08:18:21.622 * DB loaded from disk: 0.000 seconds
redis     | 1:M 23 Oct 08:18:21.622 * The server is now ready to accept connections on port 6379
dhtbay    | 2018-10-23T08:18:24: PM2 log: Launching in no daemon mode
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [loadDHT:0] starting in -fork mode-
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [loadTorrent:1] starting in -fork mode-
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [loadDHT:0] online
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [loadTorrent:1] online
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [categorize:2] starting in -fork mode-
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [crawlDHT:3] starting in -fork mode-
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [categorize:2] online
dhtbay    | 2018-10-23T08:18:24: PM2 log: App [crawlDHT:3] online
dhtbay    | {"name":"crawler","hostname":"75b1ab7bb2f3","pid":33,"level":30,"msg":"now listening","time":"2018-10-23T08:18:25.675Z","v":0}
dhtbay    | {"name":"crawler","hostname":"75b1ab7bb2f3","pid":33,"level":30,"address":"0.0.0.0","family":"IPv4","port":6881,"msg":"","time":"2018-10-23T08:18:25.681Z","v":0}
dhtbay    | {"name":"loader","hostname":"75b1ab7bb2f3","pid":15,"level":30,"msg":"Subscribed : DHTS","time":"2018-10-23T08:18:26.044Z","v":0}
dhtbay    | (node:27) DeprecationWarning: `open()` is deprecated in mongoose >= 4.11.0, use `openUri()` instead, or set the `useMongoClient` option if using `connect()` or `createConnection()`. See http://mongoosejs.com/docs/4.x/docs/connections.html#use-mongo-client
mongo     | 2018-10-23T08:18:26.471+0000 I NETWORK  [initandlisten] connection accepted from 172.18.0.5:35182 #1 (1 connection now open)
dhtbay    | (node:21) DeprecationWarning: `open()` is deprecated in mongoose >= 4.11.0, use `openUri()` instead, or set the `useMongoClient` option if using `connect()` or `createConnection()`. See http://mongoosejs.com/docs/4.x/docs/connections.html#use-mongo-client
mongo     | 2018-10-23T08:18:26.875+0000 I NETWORK  [initandlisten] connection accepted from 172.18.0.5:35186 #2 (2 connections now open)
dhtbay    | {"name":"categorize","hostname":"75b1ab7bb2f3","pid":27,"level":30,"msg":"All torrents treated","time":"2018-10-23T08:18:30.041Z","v":0}
dhtbay    | {"name":"crawler","hostname":"75b1ab7bb2f3","pid":33,"level":30,"msg":"now ready","time":"2018-10-23T08:18:30.660Z","v":0}

and basically, I can't see any web frontend listening on anything:

$ docker ps 
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                NAMES
75b1ab7bb2f3        dhtbay              "pm2-runtime start..."   10 hours ago        Up About a minute   80/tcp, 443/tcp, 43554/tcp, 0.0.0.0:6881->6881/udp   dhtbay
65c2c1d6df88        mongo:3.0           "docker-entrypoint..."   10 hours ago        Up About a minute   27017/tcp                                            mongo
20a1b0d0b7e8        flyersweb/aria2     "/docker-entrypoin..."   10 hours ago        Up About a minute   0.0.0.0:6900->6800/tcp                               dhtaria2
921f76804829        redis:3             "docker-entrypoint..."   11 hours ago        Up About a minute   6379/tcp                                             redis

as you can see, the dhtbay container basically has only port 6881 redirected, and 80/443 are not bound to anything:

$ docker inspect dhtbay
      "Ports": {
                "43554/tcp": null,
                "443/tcp": null,
                "6881/udp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": "6881"
                    }
                ],
                "80/tcp": null
            },

what am I doing wrong here ?

Crawl JS does not announce infohashes

Hi.

I ran crawl.js and no infohashes were to be found, no matter how much time I let him run.
I opened a network analyser and I saw several packets were sent in the first phase, and then no packets were on the traffic. I also disabled the firewall.

Is it still working now?

Thank you.

No new torrents appearing

I've tried setting this up with the instructions in the readme, but it isn't showing any new ones on bitcannon. What should i input in here https://github.com/FlyersWeb/dhtbay/blob/master/config/database.default.js#L3
if i didn't setup anything with mongodb?, just defaults, does it have any default login? Or do i make it blank?
Currently i have it as uri : 'mongodb://user:[email protected]:27017/bitcannon'

DHTbay and Bitcannon integration

Is there any chance you could go into more detail as to how to get these two communicating with each other? I can only get bitcannon to pull from what is listed in its config.json. How do I make it pull from dhtbay?

Bittorrent-dht

Hi.

How does your algorithm manage to get announces of infohashes?
Bittorrent-dht is for getting peers and nodes and it announces when peers want to download metadata.

Thanks

How is swarm populated in db?

I don’t see it being used in the code anywhere.

Add features list to README

I wish the readme indicated what features this tool supports, compared to other tools like magnetico.

Does this tool show seed/peer numbers?
Does this tool allow sorting by seed/peer numbers?
Does this tool have download rate limiting? Max file size limitting?
Is this tool ready to be deployed public-facing, or is it intended for local/private deployment only?

For a list of other features that you may want to add to the README, see magnetico's feature list.

Warning: API Request failed.

i installed the dht bay docker image then the bitcannon docker image. im getting errors in ssh saying .

ERROR: for mongo Cannot create container for service mongo: b'Conflict. The container name "/mongo" is already in use by container "f8f87cdf0093d69789f65102f010ece48df05d0244207b9be1ad78bd9047e698". You have to remove (or rename) that container to be able to reuse that name.'

Download magnet diferent than expected.

The download magnet's trackers differ from the expected sources from the Sources table.
I don't know if this is intended, but it makes it hard for peering, even tough its avaiable on the DHT network very often those peers are hard to reach and often almost useless

build warnings

npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Use the parse-torrent package instead
npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated [email protected]: this library is no longer supported

npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.