Connected Cluster Peer does not Sync Pins

Help
1

I have a peer successfully connected to a cluster using ipfs-cluster-service, but it does not sync the pinned files.

Here’s ‘ipfs-cluster-ctl peers ls’ showing peer is connected:

12D3KooWHejWj4cfEBe15xDEBSnJtHuBZ24KHKAGdZtdgDiRdzsv | ipfs1.cahlen.org | Sees 1 other peers

Addresses:
- /ip4/127.0.0.1/tcp/9096/p2p/12D3KooWHejWj4cfEBe15xDEBSnJtHuBZ24KHKAGdZtdgDiRdzsv
- /ip4/63.250.44.236/tcp/9096/p2p/12D3KooWHejWj4cfEBe15xDEBSnJtHuBZ24KHKAGdZtdgDiRdzsv

Here’s an example ‘ipfs-cluster-ctl pin ls’ output:

QmfMfM57UHbspaLoVigHVcnVixZ6fLt8YPjVJJHRHXfaPE | | PIN | Repl. Factor: -1 | Allocations: [everywhere] | Recursive | Metadata: no | Exp: ∞

Here’s an example ‘ipfs-cluster-ctl status’ output:

QmYdb6LPPD2eaKqVKAGkffKmYh6TVsaonBG5m9qbbnFkCS: > cahlenipfs001 : PINNED | 2021-11-10T15:08:21.185205349Z

Here are the logs from the systemd startup:

– Logs begin at Tue 2021-11-09 18:24:36 UTC. –
Nov 09 18:24:44 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T18:24:44.874Z ERROR ipfshttp ipfshttp/ipfshttp.go:746 Post “http://127.0.0.1:5001/api/v0/repo/stat?size-only=true”: dial tcp 127.0.0.1:5001: connect: connection refused
Nov 09 18:24:44 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T18:24:44.874Z ERROR p2p-gorpc go-libp2p-gorpc@v0.1.3/call.go:63 Post “http://127.0.0.1:5001/api/v0/repo/stat?size-only=true”: dial tcp 127.0.0.1:5001: connect: connection refused
Nov 09 18:24:44 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T18:24:44.874Z ERROR diskinfo disk/disk.go:108 Post “http://127.0.0.1:5001/api/v0/repo/stat?size-only=true”: dial tcp 127.0.0.1:5001: connect: connection refused
Nov 09 18:24:44 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T18:24:44.874Z WARN monitor pubsubmon/pubsubmon.go:221 discarding invalid metric: &{Name:freespace Peer:12D3KooWHejWj4cfEBe15xDEBSnJtHuBZ24KHKAGdZtdgDiRdzsv Value:0 Expire:1636482314874725198 Valid:false ReceivedAt:0}
Nov 09 23:24:48 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:24:48.417Z ERROR p2p-gorpc go-libp2p-gorpc@v0.1.3/call.go:63 context deadline exceeded
Nov 09 23:24:48 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:24:48.417Z ERROR cluster ipfs-cluster@v0.14.1/cluster.go:954 context deadline exceeded
Nov 09 23:24:48 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:24:48.417Z ERROR service ipfs-cluster-service/daemon.go:221 bootstrap to /ip4/185.130.45.140/tcp/9096/p2p/12D3KooWLE5XfHhBF6X8pzdpYh8VycQ7XDk3wqiyU3oVZC4Tp6tn failed: context deadline exceeded
Nov 09 23:25:00 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:25:00.410Z WARN cluster ipfs-cluster@v0.14.1/cluster.go:430 metric alert for ping: Peer: 12D3KooWHejWj4cfEBe15xDEBSnJtHuBZ24KHKAGdZtdgDiRdzsv.
Nov 09 23:39:42 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:39:42.121Z INFO badger go-ds-badger@v0.2.7/datastore.go:440 Running GC round
Nov 09 23:39:42 ipfs1.cahlen.org ipfs-cluster-service[642]: 2021-11-09T23:39:42.122Z INFO badger go-ds-badger@v0.2.7/datastore.go:442 Finished running GC round

2

This took several days to approve on the forum, and I’ve figured it out in that time.

The issue was launching both ipfs and cluster services via systemd at the same time. Even waiting for ipfs first to launch cluster did not work. I had to make it wait 60s for it to work.

1 Like