Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy #169

Closed
Moisey777 opened this issue Oct 27, 2021 · 11 comments
Closed

deploy #169

Moisey777 opened this issue Oct 27, 2021 · 11 comments
Labels
Status: Stale The pull request is in need of updates but there has not been a sufficient response.

Comments

@Moisey777
Copy link

Hello, I used Deployer-v2, and tried to register a delegate in my bridgechain on the devnnetwork, but a I have 0 confirmations, so I can't generate new blocks.

@Moisey777
Copy link
Author

How do I check the block explorer?

@ItsANameToo
Copy link
Member

@Moisey777 in order to help in any way, we require more information. This has been requested in ArkEcosystem/core#4517 (comment) and we are still waiting on answers related to logs. We are mostly interested in the logs related to the forging event, as it should indicate why your genesis delegates are unable to generate new blocks. Do you have enough quorum to forge blocks or is there anything in your logs indicating an issue with that?

Regarding the explorer, you can access that on port 4200 on your genesis node, e.g. by navigating to ip:4200 in a browser

Also please refrain from reposting the issue multiple times.

@Moisey777
Copy link
Author

0|neom-cor | [2021-10-27 13:41:10.914] INFO : Blockchain 100% in sync
0|neom-cor | [2021-10-27 13:41:10.914] DEBUG: event 'SYNCFINISHED': {"syncWithNetwork":"end"} -> "idle" -> actions: [checkLater, blockchainReady]
0|neom-cor | [2021-10-27 13:41:18.894] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:18.895] INFO : Network reach is not sufficient to get quorum. Will not forge.
0|neom-cor | [2021-10-27 13:41:26.954] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:26.965] INFO : Network reach is not sufficient to get quorum. Will not forge.
0|neom-cor | [2021-10-27 13:41:34.980] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:34.981] INFO : Network reach is not sufficient to get quorum. Will not forge.

1|neom-core | [2021-10-27 13:41:38.196] DEBUG: Checking ports of 0 peers.
1|neom-core | [2021-10-27 13:41:38.197] INFO : Checking 0 peers
1|neom-core | [2021-10-27 13:41:38.200] DEBUG: Throttling outgoing requests to 194.163.136.60/p2p.peer.getStatus to avoid triggering their rate limit
1|neom-core | [2021-10-27 13:41:40.207] INFO : Couldn't find enough peers. Falling back to seed peers.

1 similar comment
@Moisey777
Copy link
Author

Moisey777 commented Oct 27, 2021

0|neom-cor | [2021-10-27 13:41:10.914] INFO : Blockchain 100% in sync
0|neom-cor | [2021-10-27 13:41:10.914] DEBUG: event 'SYNCFINISHED': {"syncWithNetwork":"end"} -> "idle" -> actions: [checkLater, blockchainReady]
0|neom-cor | [2021-10-27 13:41:18.894] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:18.895] INFO : Network reach is not sufficient to get quorum. Will not forge.
0|neom-cor | [2021-10-27 13:41:26.954] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:26.965] INFO : Network reach is not sufficient to get quorum. Will not forge.
0|neom-cor | [2021-10-27 13:41:34.980] INFO : Checking 0 peers
0|neom-cor | [2021-10-27 13:41:34.981] INFO : Network reach is not sufficient to get quorum. Will not forge.

1|neom-core | [2021-10-27 13:41:38.196] DEBUG: Checking ports of 0 peers.
1|neom-core | [2021-10-27 13:41:38.197] INFO : Checking 0 peers
1|neom-core | [2021-10-27 13:41:38.200] DEBUG: Throttling outgoing requests to 194.163.136.60/p2p.peer.getStatus to avoid triggering their rate limit
1|neom-core | [2021-10-27 13:41:40.207] INFO : Couldn't find enough peers. Falling back to seed peers.

@Moisey777
Copy link
Author

I am very tired and waiting for an explanation why I have been deploying your blockchain for several months???

@Moisey777
Copy link
Author

What other information do you need?

@alexbarnsley
Copy link
Member

Your logs indicate that you don’t have quorum to forge on the network. It also shows that you have 0 peers in your peers list. Have you added your other servers to your peers.json file? You can find it at ~/.config/BRIDGECHAIN_NAME-core/devnet/peers.json (where BRIDGECHAIN_NAME is the name of your bridgechain). There you should add the peers in the following format:

{
	"list": [{
			"ip": "x.x.x.x",
			"port": 1234
		},
		{
			"ip": "y.y.y.y",
			"port": 1234
		},
	],
	"sources": []
}

Are you running separate forgers or is this happening on a genesis node?

@Moisey777
Copy link
Author

We have relay peers, but forgers are not running. The problem is that I can't create a new delegate for forger since there are no blocks for transactions.

@Moisey777
Copy link
Author

What other information do you need?

@alexbarnsley
Copy link
Member

We have relay peers, but forgers are not running

Do you mean you have turned off the genesis forgers? You will need forgers in order to forge the blocks which contain the transactions to register the new delegates. The genesis delegates are necessary to move the chain forward until they are replaced by other delegates. You should have the passphrases for them from one of the deployer steps (usually located here: ~/.config/BRIDGECHAIN_NAME-core/devnet/delegates.json)

You could try following this guide to see if it helps - https://ark.io/blog/ark-deployer-v2-setup-guide-arkio-blog

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale The pull request is in need of updates but there has not been a sufficient response. label Apr 16, 2022
@ItsANameToo ItsANameToo added Status: Stale The pull request is in need of updates but there has not been a sufficient response. and removed Status: Stale The pull request is in need of updates but there has not been a sufficient response. labels Apr 17, 2022
@stale stale bot closed this as completed Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale The pull request is in need of updates but there has not been a sufficient response.
Projects
None yet
Development

No branches or pull requests

3 participants