Problem: missing instructions for deploying chain-main with Docker image

[tomtau]

@CeruleanAtMonaco mentioned this was required by one of external parties

[Victoryfan]

It doesn't sync data, what's wrong with it?
I just use this way https://crypto.org/docs/getting-started/croeseid-testnet.html#step-3-run-everything to start node.

[Victoryfan]

Or could you provide the official docker image to run node directly?

[allthatjazzleo]

It doesn't sync data, what's wrong with it?
I just use this way https://crypto.org/docs/getting-started/croeseid-testnet.html#step-3-run-everything to start node.

it seems you have no peer in the network.
For state-sync, you may need to set the persistent peer.
Could you check the persistent peer?

[yihuang]

You might also try the nix instructions, it'll setup the state-sync configurations automatically. But you need to install nix in advance.

[Victoryfan]

I resolve it. But the height starts from 1092200, how can i make it start from 0?

[yihuang]

I resolve it. But the height starts from 1092200, how can i make it start from 0?

disable state-sync, it'll sync block one by one from 0.

[Victoryfan]

How can I can make it disable?

[allthatjazzleo]

I resolve it. But the height starts from 1092200, how can i make it start from 0?

For archive node, you need to download the binary of v0.8.1-croeseid first.
you need to clean your state-sync data by
chain-maind unsafe-reset-all --home [YOUR_HOME]
Then, like @yihuang said disable state-sync in config.
When you encounter the upgrade message, you need to upgrade the binary to v0.9.1-croeseid
upgrade guide

[Victoryfan]

How can I uninstall the ./chain-maind command?

[Victoryfan]

Just delete it?

[Victoryfan]

I resolve it. But the height starts from 1092200, how can i make it start from 0?

For archive node, you need to download the binary of v0.8.1-croeseid first.
you need to clean your state-sync data by
chain-maind unsafe-reset-all --home [YOUR_HOME]
Then, like @yihuang said disable state-sync in config.
When you encounter the upgrade message, you need to upgrade the binary to v0.9.1-croeseid
upgrade guide

I use the v0.9.1-croeseid now.

[Victoryfan]

Now it start from 0. But what's the default position of the sync data?

[Victoryfan]

Now it start from 0. But what's the default position of the sync data?

[allthatjazzleo]

Now it start from 0. But what's the default position of the sync data?

~/.chain-maind/data

[Victoryfan]

Ok, I find it. How can I stop it?

Now it start from 0. But what's the default position of the sync data?

~/.chain-maind/data

[Victoryfan]

There is not .chain-maind stop command

[allthatjazzleo]

There is not .chain-maind stop command

ctrl + c will stop the process

[Victoryfan]

Only this way?

[Victoryfan]

There is not .chain-maind stop command

ctrl + c will stop the process

Only this way? If I start it back, how can I stop it? It doesn't have other way to stop?

[Victoryfan]

Now I meet a problem

[allthatjazzleo]

There is not .chain-maind stop command

ctrl + c will stop the process

Only this way? If I start it back, how can I stop it? It doesn't have other way to stop?

follow this, to create systemd service to start or stop

[Victoryfan]

Now I meet a problem

How can I resolve this problem?

[Victoryfan]

And I do this:

[allthatjazzleo]

Now I meet a problem

How can I resolve this problem?

what is the binary version?
./chain-maind version

[Victoryfan]

./chain-maind version

[Victoryfan]

I delete data and sync from 0. Now it is normal.

[allthatjazzleo]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

[Victoryfan]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

[allthatjazzleo]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

[Victoryfan]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

[allthatjazzleo]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

[Victoryfan]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

Bu I use v0.8.1-croeseid also meet this problem

[allthatjazzleo]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

Bu I use v0.8.1-croeseid also meet this problem

As we know, this error happens with v0.9.1-croeseid sync from block 0
can you run
./chain-maind version?

[Victoryfan]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

Bu I use v0.8.1-croeseid also meet this problem

As we know, this error happens with v0.9.1-croeseid sync from block 0
can you run
./chain-maind version?

[allthatjazzleo]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

Bu I use v0.8.1-croeseid also meet this problem

As we know, this error happens with v0.9.1-croeseid sync from block 0
can you run
./chain-maind version?

when you switch to v0.8.1-croeseid, did you run chain-maind unsafe-reset-all --home ~/.chain-maind to sync again?

[Victoryfan]

./chain-maind version

if you want a fullnode from block 0 to latest block, you need to run on the binary of v0.8.1-croeseid first and then switch the binary to v0.9.1-croeseid when encountering the upgrade block.
Otherwise, you can use v0.9.1-croeseid to set up state-sync node with recent block as a starting point.

You mean if I want to start from 0, I must use v0.8.1-croeseid first, then upgrade to v0.9.1-croeseid. If I use v0.9.1-croeseid directly from 0, is not ok?

yes, because this binary of v0.9.1-croeseid contains consensus-breaking changes which should not be used to sync the block ahead upgraded block 905532.

OK, now I use v0.8.1 sync from 0. How can I upgrade it fast? I need delete v0.8.1, then install v0.9.1?

If you would like to build a node will complete blockchain data:
You should begin start with the older version v0.8.1-croeseid of chain-maind and let it sync to block height 905532.
Afterwards, your chain-maind should stop and ask you to upgrade.
You can then restart the node with v0.9.1-croeseid

Bu I use v0.8.1-croeseid also meet this problem

As we know, this error happens with v0.9.1-croeseid sync from block 0
can you run
./chain-maind version?

when you switch to v0.8.1-croeseid, did you run chain-maind unsafe-reset-all --home ~/.chain-maind to sync again?

I delete all the old data and v0.9.1-croeseid, then I install v0.8.1-croeseid to sync from 0.

[Victoryfan]

And when I use this command in v0.8.1-croeseid, it returns error:

[allthatjazzleo]

I am using v0.8.1-croeseid to sync from 0
Didn't encounter the error in block 116426 and can successfully sync

8:46PM INF commit synced commit=436F6D6D697449447B5B3931203234382032313520393620313737203639203534203337203130203231312032303020332032392031393620393920313438203734203233342032203539203233392032333220323336203134362032333620383020343920333820323031203433203234203139365D3A31444635307D
8:46PM INF Committed state appHash=5BF8D760B14536250AD3C8031DC463944AEA023BEFE8EC92EC503126C92B18C4 height=122704 module=state txs=14

[Victoryfan]

I am using v0.8.1-croeseid to sync from 0
Didn't encounter the error in block 116426 and can successfully sync

8:46PM INF commit synced commit=436F6D6D697449447B5B3931203234382032313520393620313737203639203534203337203130203231312032303020332032392031393620393920313438203734203233342032203539203233392032333220323336203134362032333620383020343920333820323031203433203234203139365D3A31444635307D
8:46PM INF Committed state appHash=5BF8D760B14536250AD3C8031DC463944AEA023BEFE8EC92EC503126C92B18C4 height=122704 module=state txs=14

Ok, thank you. Now it's syncing over 116426.

[Victoryfan]

How can I upgrade it to v0.9.1-croeseid? Need I delete v0.8.1-croeseid and then to install it?

[Victoryfan]

I resolve it. Now it is syncing by v0.9.1-croeseid.

[Victoryfan]

How can I move application.db to other workdir when I start?