Hi, I’m having issues syncing a grin node on google cloud following the instructions:
https://github.com/mimblewimble/docs/wiki/How-to%3A-Run-a-Grin-node-on-Google-Cloud-for-free
Connecting peers remains at zero and it is stuck in running state, any ideas or anyone else experiencing this issue?
I have the same issue on my local machine with the release “grin-v0.4.2-464718698-osx.tgz”.
Also tried to change the seeding type to “List” and hardcoded some seeds. But didn’t help.
From the log:
20181228 12:57:08.288 DEBUG grin_servers:
:seed - monitor_peers: on 0.0.0.0:13414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
20181228 12:57:08.288 DEBUG grin_servers::seed - monitor_peers: no preferred peers
20181228 12:57:08.288 DEBUG grin_servers::seed - monitor_peers: no dandelion relay updating
20181228 12:57:08.288 DEBUG grin_p2p::peers - Could not update dandelion relay
20181228 12:57:13.194 WARN grin_servers::sync::syncer - sync: no peers available, disabling sync
You can try setting
seeding_type = “DNSSeed”
peers_preferred = [“35.157.67.48:13414”, “204.48.26.36:13414”, “35.203.155.51:13414”, “104.248.18.227:13414”, “153.169.74.3:13414”, “89.101.91.246:13414”, “35.246.154.78:13414”, “167.99.87.54:13414”, “51.175.188.119:13414”, “217.182.192.59:13414”, “35.227.48.174:13414”, “84.94.235.161:13414”, “95.236.53.34:13414”, “162.244.80.115:13414”, “167.99.53.226:13414”, “119.237.58.248:13414”, “68.107.96.202:13414”, “76.21.112.249:13414”]
in your grin-server.toml
Thank you, but it still won’t connect. Here is what I did (maybe you spot my mistake):
Download the latest pre-compiled file from https://github.com/mimblewimble/grin/releases (osx)
Edit the grin-server.toml file (Location: [user home]/.grin) and add the “peers_preferred”.
Start the node with RUST_BACKTRACE=1 ./grin
Then it switches to “waiting for peers” and after 40-60s to “Running” but nothing happens.
Connected to peers stays at 0.
Floonet has been relaunched and the seed servers floonet.seed.grin-tech.org seems to be downed for a while. Upgrade to 0.5.0 and try again.
@codeb2cc @0xenophilius Do I need to rebuild 0.5.0 from source to upgrade from 0.4.2 or is there an easier way?
