gDHT
gDHT copied to clipboard
Olament
Build error
DEBIAN 9
root@lamp ~/gdht/gDHT# uname -r 4.9.0-12-amd64
error:
Step 8/12 : RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build ---> Running in c26e86e0b7d6 /go/pkg/mod/google.golang.org/[email protected]/internal/channelz/types_linux.go:26:2: missing go.sum entry for module providing package golang.org/x/sys/unix (imported by google.golang.org/grpc/internal/channelz); to add: go get google.golang.org/grpc/internal/[email protected] ERROR: Service 'server' failed to build: The command '/bin/sh -c CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build' returned a non-zero code: 1
I shut down the demo site due to potential legal concerns.
Looks like the error is caused by go.mod out of sync. I will look into the issue once I get back to home.
ok, thank you
If you still have a torrent base, you can share it with me, I will write a link to your project everywhere on my project. (Data provided by gDHT, something like this)
ps Now I'm making a system for defining bots, like captcha. I need a lot of site visitors to check this.
I use Elasticsearch to store all torrent information (torrent name, sha-1 hash, and file list) across multiple machines, so I would be hard for me to retrieve all information at once and it would be pretty large. If you are just looking for torrent information, I recommend you to take a look of this project.
Do you mind explain a bit more of your project? I failed to see the connection between torrent information and bot detection system.
I have a lot of space on hdd ) If it is not possible to export data, perhaps it will be possible to make access via api? (I will cache the data on my server, but I still think the load on your server will be big, and the speed on my site is low)
My project is a new generation captcha, I need a site with a large number of visits, each user, when downloading a torrent, will receive a captcha: "Are you not a robot? Please go through the captcha"
if interested, write your email I will write in more detail
ps did you find what was the problem with the docker build?