8000 Failed to start DWH · Issue #1174 · sonm-io/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Failed to start DWH #1174

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.

Sign up for GitHub

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

Jump to bottom
Open
chen0031 opened this issue Jul 8, 2018 · 7 comments
Open

Failed to start DWH #1174

chen0031 opened this issue Jul 8, 2018 · 7 comments

Comments

@chen0031
Copy link
chen0031 commented Jul 8, 2018

When I deployed the contracts to my private geth chain, I cannot start dwh services. The error is ：

Failed to serve DWH: failed to create NewAPI: failed to setup contract registry: abi: unmarshalling empty output
@nikonov1101
Copy link
Member

Hello! Seems like you should set the registry contract address in the DWH config, like this

blockchain:
  contract_registry: <your_contract_address_here>

@chen0031
Copy link
Author

@sshaman1101 Thanks for your reply. Actually, I have added the contract_registry address in the config file, but I don't know whether it is correct. Because I didn't find the contract registry address in the deployed contract list, so I use market contract address as the contract registry address. That's why I got that result. By the way, I didn't find any contents related to contract registry address in the blockchain/source/migration doirection. I guess you may miss something.

@nikonov1101
Copy link
Member

@sokel @quasisamurai can you please join the discussion and help with the ContractRegistry?

@quasisamurai
Copy link
Collaborator
quasisamurai commented Jul 13, 2018 •
edited
Loading

@chen0031 Hi. You can't replace one contract by another, that's why DWH fails.
Key of you problem is in migrations. While /migrations dir store deploy scripts for a local testing, it doesn't contains ContractRegistry (this is a code name, contract called AddressHashmap.sol) that is only live realise contract.
There is two ways to solve your problem:

  • Write your own deploy script for contract registry, and fill it yourself (it's better to do this in the deploy script to automate it). Try it on and if you need help, you can ping me.

  • Go to feat: deployment scripts for livenet #1087 and modify those migrations as you wish. It should take a few time to understand what is going on there, but it can be easier for someone than first way.

If you have more quesions - feel free to ask.

@chen0031
Copy link
Author

@quasisamurai Thanks for your advice. I can run SONM with the default contract registry. Currently, I am trying SONM in a private chain environment with Ethereum. But I came across some problems. Therefore, could your provide some guides to set up a test private chain and deploy the contracts on it? Thanks a lot!

@quasisamurai
Copy link
Collaborator

@chen0031

set up a test private chain

What does you mean by? Setup our chain or your own?
Btw, You can't deploy any contracts to our blockchain due we don't allow this by design. So if you want setup your own blockchain, visit geth repo and google more information.

@chen0031
Copy link
Author

@quasisamurai . I will not deploy any contracts on your blockchain. I have my own test Ethereum private chain and a sidechain. But I cannot make it work although the contracts have been deployed successfully. The DWH service cannot sync blocks between the low data store and the sidechain bock data. I am still thinking what's the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nikonov1101 @chen0031 @quasisamurai
0