Closed lurenjia528 closed 5 years ago
The api /peers
is defined in the feature version 0.4
, it's not used by 0.3.x
. You could find the supernode api used by dfget
here.
It seems that your nginx configuration may be not correct(your supernode is listened on port 8083) from the error message 502 Bad Gateway
.
Could you paste your nginx configuration?
worker_rlimit_nofile 100000;
events { use epoll; worker_connections 20480; }
http { include mime.types; default_type application/octet-stream; root /home/admin/cai/htdocs; sendfile on; tcp_nopush on;
server_tokens off;
keepalive_timeout 5;
client_header_timeout 1m;
send_timeout 1m;
client_max_body_size 3m;
index index.html index.htm;
access_log off;
log_not_found off;
gzip on;
gzip_http_version 1.0;
gzip_comp_level 6;
gzip_min_length 1024;
gzip_proxied any;
gzip_vary on;
gzip_disable msie6;
gzip_buffers 96 8k;
gzip_types text/xml text/plain text/css application/javascript application/x-javascript application/rss+xml application/json;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Web-Server-Type nginx;
proxy_set_header WL-Proxy-Client-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
proxy_buffers 128 8k;
proxy_intercept_errors on;
server {
listen 8001;
location / {
root /nas/dragonfly/data/repo;
}
}
server {
listen 8002;
location / {
proxy_pass http://192.168.40.92:8083;
}
}
}
thanks!
which supernode should I use?
build the binary supernode or supernode.jar?
https://github.com/dragonflyoss/Dragonfly/blob/v0.3.0/cmd/supernode/main.go
or
https://github.com/dragonflyoss/Dragonfly/tree/v0.3.0/src/supernode
Could you telnet 192.168.40.92 8083
on your host which deploy nginx to verify whether the supernode can be connected?
build the binary supernode or supernode.jar
The supernode.jar
is available for now.
@lowzj thanks
it alreay work In my supernode machine , the nginx.conf is as blow : server { listen 8002; location / { proxy_pass http://127.0.0.1:8083; } } and i change to as blow : server { listen 8002; location / { proxy_pass http://192.168.40.92:8083; } }
it works
/close
the peer registry fail
supernode log
version:release-v0.3.0 build on arm64
source code: the supernode api "/peer/registry"
https://github.com/dragonflyoss/Dragonfly/blob/v0.3.0/src/supernode/src/main/java/com/dragonflyoss/dragonfly/supernode/rest/controller/PeerController.java#L51 https://github.com/dragonflyoss/Dragonfly/blob/v0.3.0/src/supernode/src/main/java/com/dragonflyoss/dragonfly/supernode/rest/controller/PeerController.java#L70
client the post interface "/peers" https://github.com/dragonflyoss/Dragonfly/blob/v0.3.0/client/peer_create.go#L27
the api do not match , Is it a bug?