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

unable to interpret json file with incubeth privateKey flag #8

Open
ltfschoen opened this issue Jul 20, 2019 · 1 comment
Open

unable to interpret json file with incubeth privateKey flag #8

ltfschoen opened this issue Jul 20, 2019 · 1 comment
Assignees

Comments

@ltfschoen
Copy link
Contributor

ltfschoen commented Jul 20, 2019

this relates to the privateKey flag https://github.com/tincubeth/node/blob/master/docker-compose.yml#L22 that expects a JSON file

but when you follow the steps in the Readme file the output is the following error:

$ docker-compose up --build
Building tor
Step 1/5 : FROM patrickod/tor-hidden-service
 ---> 5852a35f5abc
Step 2/5 : ADD ./start-tor.sh /bin/start-tor.sh
 ---> Using cache
 ---> d64a9316b4fc
Step 3/5 : RUN chmod +x /bin/start-tor.sh
 ---> Using cache
 ---> 0f5e2a6fa77a
Step 4/5 : ADD ./get-tor-hostname.sh /bin/get-tor-hostname.sh
 ---> Using cache
 ---> 9e45edac526c
Step 5/5 : RUN chmod +x /bin/get-tor-hostname.sh
 ---> Using cache
 ---> 163a879e34ba
Successfully built 163a879e34ba
Successfully tagged node_tor:latest
Starting node_incubed-server_1 ... done
Starting node_incubed-parity_1 ... done
Starting node_tor_1            ... done
Attaching to node_incubed-parity_1, node_incubed-server_1, node_tor_1
incubed-parity_1  | Could not load specification file at 0x5: No such file or directory (os error 2)
tor_1             | Jul 20 10:19:04.237 [notice] Tor v0.2.4.20 (git-3cb5c70beec5bf46) running on Linux with Libevent 2.0.16-stable and OpenSSL 1.0.1.
tor_1             | Jul 20 10:19:04.237 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
tor_1             | Jul 20 10:19:04.237 [notice] Read configuration file "/etc/torrc".
tor_1             | Jul 20 10:19:04.239 [notice] Opening Socks listener on 127.0.0.1:9050
node_incubed-parity_1 exited with code 1
incubed-server_1  | no config found (Error: ENOENT: no such file or directory, open 'config.json')! using defaults
incubed-server_1  | Error starting the server : Could not decode the private : ethUtil.sha3(...).replace is not a function { port: 8500,
incubed-server_1  |   chains: 
incubed-server_1  |    { '0x5': 
incubed-server_1  |       { rpcUrl: 'http://incubed-parity:8545',
incubed-server_1  |         privateKey: '/secure/keystore.json',
incubed-server_1  |         minBlockHeight: 6,
incubed-server_1  |         registry: '0x85613723dB1Bc29f332A37EeF10b61F8a4225c7e',
incubed-server_1  |         registryRPC: '',
incubed-server_1  |         privateKeyPassphrase: 'p',
incubed-server_1  |         autoRegistry: [Object] } },
incubed-server_1  |   logging: { colors: true } }
incubed-server_1  | error: Error starting the server Error: Could not decode the private : ethUtil.sha3(...).replace is not a function port=8500, rpcUrl=http://incubed-parity:8545, privateKey=/secure/keystore.json, minBlockHeight=6, registry=0x85613723dB1Bc29f332A37EeF10b61F8a4225c7e, registryRPC=, privateKeyPassphrase=p, url=http://in3.server:8500, deposit=2, colors=true

need to ask why its happening by creating an issue on the in3 https://github.com/slockit/in3 github repo

@ltfschoen
Copy link
Contributor Author

Depends on blockchainsllc/in3-legacy#52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants