No bootsrap address specified

I’m trying to start new storagenode.

Followed guide,
but getting this error in the log:

2019-08-28T03:30:19.997Z WARN kademlia kademlia/kademlia.go:156 No bootsrap address specified {“STORAGE”: “12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU”}
storj.io/storj/pkg/kademlia.(*Kademlia).Bootstrap
/go/src/storj.io/storj/pkg/kademlia/kademlia.go:156
storj.io/storj/storagenode.(*Peer).Run.func2
/go/src/storj.io/storj/storagenode/peer.go:382
golang.org/x/sync/errgroup.(*Group).Go.func1
/go/pkg/mod/golang.org/x/sync@v0.0.0-20190423024810-112230192c58/errgroup/errgroup.go:57

and here is dashboard output:

Storage Node Dashboard ( Node Version: v0.0.0 )

======================

ID           12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU
Last Contact OFFLINE
Uptime       16m52s

                   Available     Used     Egress     Ingress
     Bandwidth       40.0 TB      0 B        0 B         0 B (since Aug 1)
          Disk        1.4 TB      0 B

Bootstrap 
Internal  127.0.0.1:7778
External  deb10b.slavikf.com:28967

Neighborhood Size 0

Any idea why my storagenode may not have bootstrap URL defined?

Your storage node is offline, according to the dashboard.

Can you do the checks mentioned on Node stopped responding overnight. Still shows OFFLINE after restart

Please, post your docker run command too.

my docker command:

docker run -d --restart unless-stopped \
    -p 28967:28967 \
    -p 14002:14002 \
    -e WALLET="0x277b6D64AF9a1D0BA1E8Be24Bb657409B0de8363" \
    -e EMAIL="slavikCA+deb10b@gmail.com" \
    -e ADDRESS="deb10b.slavikf.com:28967" \
    -e BANDWIDTH="40TB" \
    -e STORAGE="1400GB" \
    --mount type=bind,source="/home/slavik/.local/share/storj/identity/storagenode",destination=/app/identity \
    --mount type=bind,source="/var/storj",destination=/app/config \
    --name storagenode \
    storjlabs/storagenode

There is no firewall.
I can SSH and ping using it’s hostname deb10b.slavikf.com
Identity looks ok.

not sure, what else can go wrong…

By the way, there is one more error present, every time I’m starting node:

WARN storagenode/main.go:164 Failed to initialize telemetry batcher: process error: telemetry disabled
main.cmdRun
/go/src/storj.io/storj/cmd/storagenode/main.go:164
storj.io/storj/pkg/process.cleanup.func1.2

And my storagenode has internet connection, as far as I can see:

slavik@deb10b:~$ sudo docker exec storagenode wget -q -O - ifconfig.co
142.44.185.104
slavik@deb10b:~$ sudo docker exec storagenode wget -q -O - https://storj.io | head
<!DOCTYPE html>
<html lang="en">
  <head>
        <meta name="generator" content="Hugo 0.53" />
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta name="description" content="Decentralized cloud storage that is automatically encrypted, easily implemented, highly performant, exceptionally economical, and ridiculously resilient.">

I’m a bit curious why you have 2 different port paramaters:

docker run -d --restart unless-stopped \
-p 28967:28967 \
-p 14002:14002 \

Is there a reason for this?

Can you try removing the second
-p 14002:14002

port 14002 is for dashboard.

Tried without it: no difference.

Try to remove the config.yaml and restart the node docker restart -t 300 storagenode

no difference.

Here is complete log since restart:

2019-08-28T21:17:38.617Z        INFO    process/exec_conf.go:89 Got a signal from the OS: "terminated"
2019-08-28T21:17:40.838Z        DEBUG   process/debug.go:51     debug server listening on 127.0.0.1:38459
2019-08-28T21:17:40.983Z        INFO    process/exec_conf.go:229        Configuration loaded from: /app/config/config.yaml
2019-08-28T21:17:40.995Z        INFO    kademlia/config.go:78   Operator email: slavikCA+deb10b@gmail.com
2019-08-28T21:17:40.995Z        INFO    kademlia/config.go:92   operator wallet: 0x277b6D64AF9a1D0BA1E8Be24Bb657409B0de8363
2019-08-28T21:17:41.244Z        WARN    storagenode/main.go:164 Failed to initialize telemetry batcher: process error: telemetry disabled
main.cmdRun
        /go/src/storj.io/storj/cmd/storagenode/main.go:164
storj.io/storj/pkg/process.cleanup.func1.2
        /go/src/storj.io/storj/pkg/process/exec_conf.go:262
storj.io/storj/pkg/process.cleanup.func1
        /go/src/storj.io/storj/pkg/process/exec_conf.go:280
github.com/spf13/cobra.(*Command).execute
        /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:762
github.com/spf13/cobra.(*Command).ExecuteC
        /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:852
github.com/spf13/cobra.(*Command).Execute
        /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:800
storj.io/storj/pkg/process.Exec
        /go/src/storj.io/storj/pkg/process/exec_conf.go:72
main.main
        /go/src/storj.io/storj/cmd/storagenode/main.go:296
runtime.main
        /usr/local/go/src/runtime/proc.go:200
2019-08-28T21:17:41.245Z        INFO    db.migration    migrate/versions.go:115 Latest Version  {"version": 19}
2019-08-28T21:17:41.245Z        INFO    bandwidth       bandwidth/service.go:50 Performing bandwidth usage rollups
2019-08-28T21:17:41.245Z        WARN    kademlia        kademlia/kademlia.go:156        No bootsrap address specified   {"STORAGE": "12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU"}
storj.io/storj/pkg/kademlia.(*Kademlia).Bootstrap
        /go/src/storj.io/storj/pkg/kademlia/kademlia.go:156
storj.io/storj/storagenode.(*Peer).Run.func2
        /go/src/storj.io/storj/storagenode/peer.go:382
golang.org/x/sync/errgroup.(*Group).Go.func1
        /go/pkg/mod/golang.org/x/sync@v0.0.0-20190423024810-112230192c58/errgroup/errgroup.go:57
2019-08-28T21:17:41.245Z        INFO    storagenode/peer.go:411 Node 12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU started
2019-08-28T21:17:41.246Z        INFO    storagenode/peer.go:412 Public server started on [::]:28967
2019-08-28T21:17:41.246Z        INFO    storagenode/peer.go:413 Private server started on 127.0.0.1:7778
2019-08-28T21:17:41.246Z        INFO    piecestore:monitor      monitor/monitor.go:89   Remaining Bandwidth     {"bytes": 40000000000000}

Please, make sure that you pulled the storjlabs/storagenode:alpha image, not the latest

1 Like

that was it!

it works now:


Storage Node Dashboard ( Node Version: v0.19.0 )

======================

ID           12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU
Last Contact 0s ago
Uptime       5m52s

                   Available     Used     Egress     Ingress
     Bandwidth       40.0 TB      0 B        0 B         0 B (since Aug 1)
          Disk        1.4 TB      0 B

Bootstrap bootstrap.storj.io:8888
Internal  127.0.0.1:7778
External  deb10b.slavikf.com:28967

Neighborhood Size 142

Hi
As I was going through the same error, after reading and implementing this thread I solved my issues with Prometheus (-ad removed-). I was curious about different port parameters but the solved the problem.
Thank you all.