I trying out Ethereum for the first time. I was able to get Ethereum wallet downloaded and installed on my Windows 10 system. Now when I try to launch .exe file I get "Could connect to node? See the logs for". I have attached a screenshot.
Any ideas of how I can resolve this issue?
Thanks!
The mistake I was making, The path that I pointed to the geth.exe in commandline was from a download outside of the Ethereum dir. When I ran geth from ethereum\Ethereum-Wallet-win64-0-6-2\Ethereum-Wallet-win64-0-6-2\resources\node\geth as opposed to desktop/geth that I downloaded separately then Ethereum began to run as expected.
I hope this helps someone else in need!
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.
https://remix.ethereum.org/#optimize=false&version=soljson-v0.4.25+commit.59dbf8f1.js
The Remix editor with the error
Can someone help me go past this error? Why does the contract not compiling?
I am able to deploy the source on my machine, just restart the browser and clean the cache and everything then it should work.
I'm trying to deploy my own .bna file to a business network using
this tutorial.
The only difference is that I am doing this with three organizations.
Everything works fine until I run the step eight because when I run this command:
composer network ping -c alice#trade-network
I got this error:
Error trying to ping. Unexpected end of JSON input.
Does anybody know how can I solve this?
Thank you
I had the same issue, and I knew it was a matter of local configuration since it stopped working suddenly after throwing several commands. So, I fixed it by stopping fabric and tearing it down.
Then, started fabric, created my peer credential and deployed everything again.
Review the commands in here (section: Controlling your dev environment):
https://hyperledger.github.io/composer/v0.19/installing/development-tools.html
I have read the posts similar to this but to no avail.
I am in the midst of a comprehensive tutorial for Angular (5). I am on MacOs High Sierra 10.13.3. I am using Chrome Version 64.0.3282.140 (Official Build) (64-bit).
I just completed one project in the tutorial. I am now trying to complete the next project in the tutorial. The project is set to use the default port 4200 on localhost. All of the projects have executed this way.
I have performed my npm install. My npm start script is simple, = "ng serve". I enter npm start and it serves up the project as expected. I then go to my browser and enter the address localhost:4200. The previous project renders. I can't get the current project to render. These are the things I have tried to remedy the situation:
sudo lsof -i tcp:4200
changing the start script to ng serve --port 4300 and then using the address localhost:4300 (tried it with 5000 too)
Actually the first thing I did was look for an active activity on port 4200 in the Activity Monitor
Clear my Chrome browsing history
Restart my computer.
Tried the same process using Firefox as a browser
Tried it using Brave as a browser
In each and every case when I enter localhost:(anything) I get the previous project. Any ideas?
If I could delete this question I would. I discovered the problem.
I only THOUGHT I was pointing to the new project. In reality, I was pointing at the old project. THAT is why the same thing kept coming up and that is why nothing I tried would work.
I am embarrassed. Clearly, I am still a rookie. I hope no one spent any time on this.
I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.