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

Installing geth #583

Closed
JustinDrake opened this issue Mar 27, 2015 · 7 comments
Closed

Installing geth #583

JustinDrake opened this issue Mar 27, 2015 · 7 comments

Comments

@JustinDrake
Copy link
Contributor

I've followed the building instruction for Mac OS X, and got ethereum going.

I now want to try the JavaScript console. Sadly, geth console outputs

-bash: geth: command not found

and ethereum console outputs

[CLI] resource temporarily unavailable

What gives?

@bas-vk
Copy link
Member

bas-vk commented Mar 27, 2015

Ethereum is renamed to geth very recently. Since your are able to run ethereum I believe you are on the wrong branch, not up to date or running a previous build version of ethereum which is somewhere in your path. Pull the latest sources, checkout the develop branch and build cmd/geth. If you already have the geth binary its probably not in your PATH. A go install may help with that depending on your configuration.

The second output might be caused by running the ethereum application multiple times. Stop all running ethereum/geth processes and then start one console instance. You can pass additional arguments and use the javascript console to have a limited administration console.

@JustinDrake
Copy link
Contributor Author

So we have different names across the repository. This seems pretty poor.

Anyway, I've stopped all ethereum processes, and ethereum console now outputs:

[CLI] open console: no such file or directory

What's up with this new error?

I didn't realise how far from production Ethereum actually is.

@zelig
Copy link
Contributor

zelig commented Mar 28, 2015

well, already one step closer with your kind help.
so what you are saying is:

  • improve documentation stressing that the wiki pages are about the development branch.
  • start a trouble shooting page with funny errors like this
  • improve error message for [CLI] resource temporarily unavailable

@JustinDrake
Copy link
Contributor Author

@zelig: Good summary. Also add "improve error message for [CLI] open console: no such file or directory". I have no idea what this means in the context of ethereum console.

@obscuren
Copy link
Contributor

Thanks @JustinDrake. geth will soon be on the master branch as well.

@zelig Don't bother about mentioning develop in documentation. This will soon be obsolete

@zelig
Copy link
Contributor

zelig commented Apr 14, 2015

if you devtype living on the edge follow https://github.com/ethereum/go-ethereum/wiki/Developers%27-Guide
otherwise on MacOS you got brew: brew install ethereum --devel --build-from-source

@zelig zelig closed this as completed Apr 14, 2015
@kristianmandrup
Copy link

Is this still the case? I installed Ethereum Wallet and Mist from MacOSX .dmg files.
When I went to the Readme I'm told there are distributions, but when I click it downloads Mist.dmg which I already installed... Very confusing!
Please make it more clear in the docs. Too many name changes and inconsistent recipes...

ngtuna added a commit to ngtuna/tomochain that referenced this issue Jul 24, 2019
remove timestamp from orderbookitem
tony-ricciardi pushed a commit to tony-ricciardi/go-ethereum that referenced this issue Jan 20, 2022
* added proxy server

* added isproxy field to peer objects

* relay messages proxy receives to validator

* Add addSentry RPC

* Add removeSentry RPC

* Add admin.sentryInfo RPC

* Add --proxied flag

* Don't consider sentry nodes as contributing toward the max peer count

* Don't assume a sentry will never be a validator

* Remove proxied check from api

* Go back to assuming sentry will not be a validator

* Fix eth tests

* Fix eth test lint

* Add max sentry node count as 1

* wip, add val_enode_share

* Remove redundant proxied check

* Add warning if proxied but not mining

* Wip, messages now are received by sentry

* Clean up, add signatures to val enode share msg

* Add sharedValidatorEnode struct

* Use received shared validator enodes, add proxied check for sharing

* Clean up, remove proxied as a variable in istanbul backend

* run go fmt

* Fix tests

* Add val enode share test

* Change GlobalIsSet -> GlobalBool

* Change to val enode share to every minute, fix comment

* Read lock when reading val enode table entries

* got blockchain syncing done via the sentry

* Refactor val enode share to use istanbul message struct

* changes for relayer consensus message handling

* Refactor announce to use istanbul message struct

* peer.Send done in a goroutine

* Add better logging

* Proxied validators do not peer with validators, sentries do

* Don't refresh val set peers if proxy, lock once when upserting upon handling table message

* Fix lint, tests

* fixed lint errors

* made the sentry and proxied command line argument more consistent

* got announce and val_enode_share msgs working

* forwarding of consensus messages now working

* fix the old block seal

* fixed comment

* added test case for 'old block' preprepare

* simplified the logic

* refactored sentry related command line args and moved addsentry and removesentry rpc api to istanbul package

* refactoring the p2p server to remove sentry and validator connections

* moved all validator and sentry peer management from p2p to istanbul

* fixed bugs

* removed the refactoring of core.finalizeMessage, backend.Broadcast, backend.Gossip.  Leave it for later

* changed proxy listen port flag to listen endpoint

* changes in the test files for the new addpeer and addtrusted p2p.server apis

* changed order of params in Gossip to be same as original ordering

* fixed p2p peer test for the new p2p server interface

* lint fixes

* changes to get istanbul related unit tests to pass

* some changes for the unit tests

* removed some debug logging and added some comment

* added some comments to clarify the need for istanbul.backend.NewWork and istanbul.backend.NewChainHead

* set maxpeers to 1 for the internal server interface

* created istanbul forward message

* removed unneeded whitespace

* handled case of no sentry node set in unregisteredpeer

* got sigint to work

* added support for setting sentry nodes via command line

* fixed a bug

* addressed PR comments

* fixed a big and addressed more PR comments

* will now send an announce message at start of new epoch

* refactor istanbul message (ethereum#583)

* refactored istanbul message

* addressed PR comments

* addressed PR comments

* addressed more PR comments

* addressed more PR comments

* change p2p static and trusted peer labels to purposes

* got proxy end to end test working

* changed the purpose from string type to bitmap based type

* removed redundant adding of active validators to the regAndActiveVal set

* fixed a bug

* re-point celo-monorepo to master

* fixed miner unit test to not create the validatorenode db directory in the miner directory

* addressed PR comments from mcortesi

* handled old announce messages

* fixed a bug

* addressed PR comments

* modified UnionOfSeals to return an error instead of panic-ing

* checked for dup or irrelevant entries when process an announce message

* fixed bugs

* don't regossip announce message if it has dups or irrelevent entries
maoueh pushed a commit to streamingfast/go-ethereum that referenced this issue Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants