I'm a DAPP beginner, and am trying to get up and running with the Truffle framework. I've been walking through the Truffle docs, but it doesn't work out of the box for me.
Create directory, cd into it, and run 'truffle init'
Run 'truffle compile'
Run testrpc in a second terminal window, same project directory
Run 'truffle migrate'
This is the error I get from truffle:
Running migration: 1_initial_migration.js
Deploying Migrations...
Error encountered, bailing. Network state unknown. Review successful transactions manually.
Error: Server error
at Object.module.exports.InvalidResponse (/usr/local/lib/node_modules/truffle/node_modules/ether-pudding/node_modules/web3/lib/web3/errors.js:35:16)
at /usr/local/lib/node_modules/truffle/node_modules/ether-pudding/node_modules/web3/lib/web3/requestmanager.js:86:36
I get this with Node v5 & v6.
Truffle v2.1.1.
Web3 and ether-pudding are installed as truffle dependencies.
TestRPC/0.8.7/darwin/python2.7.12.
Thanks for the help-
Are you sure you did run testrpc in a second window and let it run? This is important as testrpc in that case is yoir blockchain. If it does not run you will get similar errors as what you describe.
To keep it simple, I also suggest as a start that you do not run another client while running testrpc (geth, parity, mist, ... )
So in short, do a reboot, start testrpc, make sure it does not display errors, then run the truffle migrate command while testrpc still runs in the background.
Truffle migrate does run correctly. I've reposted my issue with testrpc here:
Testrpc error: 'no loggers could be found for logger 'jsonrpc.manager'
Related
I'm trying to migrate my new truffle configs to test a smartcontract in a private network. But when I try to migrate it, I get stuck here:
1_initial_migration.js gets hanging on "Replacing Migrations" forever
Can somebody please help me solving it?
I think I've had this problem. I suspect Ganache is in a bad state. And I swear truffle doesn't incrementally build correctly sometimes. So when in doubt, fully restart Ganache, rebuild with --all and redeploy with --reset .
That is:
Exit Ganche
Check Task Manager, ps, or equivalent and terminate all rogue instances of Ganache that might still be running. Ganache tends to start several child processes. So make sure they aren't lingering around before you restart it.
Restart Ganache with a new workspace.
Recompile with this: truffle compile --all
Redeploy with: truffle deploy --reset
Weird bugs tend to go away when I completely do a full reset as described by these steps. In on case, I just rebooted because port 7575 was locked by something.
I'm trying to setup the gitlab ci shell runner. I've used the docker runner before successfully but now I'd like to use another docker container within my testing routine and therefore switched to the shell runner.
After registering I'm running into an exception:
ERROR: Job failed (system failure): prepare environment: exit status 1. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information
So, I went through the linked material but that didn't cure the problem. Now, I verified that the gitlab-runner user exists and it has access to docker (needed to run the docker test container). Also the gitlab-runner user is part of the docker group. I can also --login, fire up the /bin/bash without problems.
Still, all I get from the runner side is the the enigmatic message above. What other checkups to I need to do to track down this issue?
The careful reader will find the answer:
"A common failure is when you have a .bash_logout that tries to clear
the console."
I'm having an odd issue with the awsebcli package when running it on Gitlab's pipeline CI system.
When I run eb deploy locally, the command succeeds (or fails) much as expected. When I run it as part of the CD scripts I've written, it runs successfully (i.e. returns an exit code of 0) but doesn't actually trigger the deployment. No errors are returned - in fact there's no text output from the command at all.
Can anyone suggest what could be going wrong here?
I'm on Windows trying to connect to Ethereum Testnet via rinkeby.
I downloaded geth 1.8.2 and Ethereum Wallet 0.9.3
I gave 1st command as:
geth --rinkeby --fast --cache=1024
NOTE: after above command, I get the url on cmd as:
url=\\.\pipe\geth.ipc
And 2nd command in another command prompt as:
geth --datadir=./rinkeby attach
The same commands were working earlier.
I uninstalled both geth and Ethereum wallet and installed latest versions. I tried the commands on the earlier versions also where they were working but now they are not.
I also tried connecting to Private net just now, but got the error message on 2nd command prompt as:
Unable to attach to remote geth: no known transport for URL scheme "c"
Thanks in advance!
I think this issue only occurs on Windows.
Refer: https://github.com/ethereum/go-ethereum/issues/15746
Try the following to specify the IPC path
geth attach ipc:\\.\pipe\geth.ipc
It should work on Win10 and v1.8.x-stable
When run the command 'embark run'. I got the error message:
Running "deploy_contracts:development" (deploy_contracts) task
Warning: ==== can't connect to localhost:8101 check if an ethereum node is running Use --force to continue.
Error: ==== can't connect to localhost:8101 check if an ethereum node is running
Could you please give me some help about it?
Before you can run embark, you have to run an ethereum rpc simulator, simply run:
$ embark simulator
Or Alternatively, you can run a REAL ethereum node for development purposes:
$ embark blockchain
By default embark blockchain will mine a minimum amount of ether and will only mine when new transactions come in. This is quite usefull to keep a low CPU. The option can be configured at config/blockchain.yml
You will see a geth node starting in the terminal. Then, open another terminal and type:
$ embark run
This will automatically deploy the contracts, update their JS bindings and deploy your DApp to a local server at http://localhost:8000
Note that if you update your code it will automatically be re-deployed, contracts included. There is no need to restart embark, refreshing the page on the browser will do.
See also newest embark tagged questions on Ethereum Stack Exchange for future reference.
In your embark project directory:
run $ embark blockchain and leave this running on your terminal.
Open a new terminal, cd <yourProject> and run $ embark run
You will now be up and running on your local host at http://localhost:8000