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
Related
I install GETH on Windows10 but when I execute the command
geth version
it will get an error "geth' is not recognized as an internal or external command,
operable program or batch file."
Sounds like something to do with your environmental variables and dependencies.
Firstly ensure that you have installed all dependencies correctly. Follow the installation steps here
https://github.com/ethereum/go-ethereum/wiki/Installation-instructions-for-Windows
This will ensure that all env paths are set correctly and that geth will be configured into your system variables.
Hope this helps! feel free to message me if you have anymore trouble
I am trying to install minishift on Windows. However, I am facing with below Issue while installing It.I have tried with multiple version of Open Shift
Command Used : minishift.exe start --vm-driver virtualbox
Console Out Put :
-- Downloading OpenShift v3.9.0 checksums ... OKError starting the cluster: Error attempting to download and cache 'oc': Failed to validate hash - expected: 7ed04f7bc411056425d98aa6a10536fab15bdb569549446223f6ed22421ea4e6, actual: 705eb110587fdbd244fbb0f93146a643b24295cfe2410ff9fe67a0e880912663
Is their anyway to skip hash validation Check..?
There is currently no option to disable hash validation check. However there is a workaround for your issue, you can download the binary manually and put it into Minishift home - then Minishift on next start will not attempt to download it.
Download oc v3.9.0 release for Windows from its release page
Extract
Move oc.exe binary to .minishift/cache/oc/v3.9.0/windows/oc.exe
Start Minishift
Similar steps will also apply for other platforms and versions of oc. You can search for all releases by tag at Origin release page.
Reason of failure:
I have checked both Checksum on release and actual sha256sum of the binary and your sum is correct. Is it possible that the CHEKSUM file is cached on your proxy? What is the version of Minishift you are using?
If you are willing to invest some of your time, you can create an issue on Minishift so the team can take a deeper look into the problem.
you might receive a 403 forbidden status from GitHub if your request exceeds the rate limit for your IP address.Instead of waiting for GitHub to reset the limit for your IP address, you can create a Personal API Tokens from your personal GitHub account.
Personal API Token generation URL: https://github.com/blog/1509-personal-api-tokens
You need to set Token to environment variable.
For windows10: set MINISHIFT_GITHUB_API_TOKEN=<token_ID>
For Linux: export MINISHIFT_GITHUB_API_TOKEN=<token_ID>
Then run below command on windows CMD:
minishift.exe start --vm-driver virtualbox
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'
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
I have a working vagrant + ansible setup to provision my digital ocean, it was running on api v1, but when DO deprecated it I got an error message telling me there was no support for v1 anymore. After a research I found out I needed to upgrade to ansible 2.0 + update my digital_ocean.py since the older one was still using client_id and api_key, the new one however now uses the api_token.
Basically I've updated
1.digital_ocean.py which I got from ansible repo module
2. digital_ocean.ini to contain the api_token
3. updated my api token from DO to make sure it's using the new one
but when I execute my ansible playbook I initially got this error
ERROR! The file provisioning/inventory/staging/digital_ocean.py looks like it should be an executable inventory script, but is not marked executable. Perhaps you want to correct this with `chmod +x provisioning/inventory/staging/digital_ocean.py`?
So naturally had to chmod +x it but when I did I get a new error which is
ERROR! The file provisioning/inventory/staging/digital_ocean.py is marked as executable, but failed to execute correctly. If this is not supposed to be an executable script, correct this with `chmod -x provisioning/inventory/staging/digital_ocean.py`.
ERROR! Inventory script (provisioning/inventory/staging/digital_ocean.py) had an execution error:
ERROR! provisioning/inventory/staging/digital_ocean.py:3: Error parsing host definition ''''': No closing quotation
The next one seem to be json parsing related, my only problem is that it's on line 3 which if you check on the code itself are still on the comment side
https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/digital_ocean.py
I received both errors mentioned and solved them with the following:
The dopy related error was due to the fact that my python and pip were installed differently. dopy was installed via pip which was installed via homebrew. I was using the system python. When I installed python via homebrew, the script found dopy just fine.
Regarding the second error, that is the result I got when not setting the DO_API_TOKEN. I set mine in the command itself with:
DO_API_TOKEN=<api_token> ansible -i digital_ocean.py all -m ping