-
Notifications
You must be signed in to change notification settings - Fork 20k
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
starting multiple geth console #1714
Comments
Each geth instance will open a named pipe on the Windows platform where clients can attach to. Since you already have one instance running the second instance cannot create the named pipe since it already exists. There are 2 options:
|
Tried your first option and got the following error. Fatal blockchain db error: The process cannot access the file because it is used by another process. |
I will write (or update if such page already exists) a wiki page which explains how to run multiple geth instances and replace this comment with a link to it. |
@meetreks You need to also supply a different datadir, I believe if you do that the ipcpath will automatically be different. See instructions here. |
I tried that as well first and did not work. Which is why I reached out to the forum to try my luck. I think we need detailed instructions on how to run 2 geth nodes. |
You might need to specify a different port with |
First of all:
Doesn't connect to the main net. If you provide a custom networkid your node will not be able to connect to nodes which are on the network. If you use a recent version of geth (and you should) you can omit the genesis argument since its embedded in geth. Your command should somewhat like this
If you want to start a second node which you can use for development, testing and deployment you can setup a private network. Each geth instance needs its own datadir, unique ports and unique ipc endpoint. In your case you choose to disable the ipc interface which makes it a bit easier. And second you might want to use a custom genesis block for your private network. See https://github.com/ethereum/go-ethereum/wiki/Private-network for instructions and an example genesis file which you can adapt to your personal needs. The command for you private instance will look something like: If you want to do some DApp development and need the JSON RPC HTTP interface you must add the You can find more instructions here: https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-network-or-local-cluster. If you need more help just visit the gitter channel, there are people who can help you with this. |
Considering this resolved. Please reopen is your issue persists. |
### Description Observed `cmd/geth TestRegistryInGenesis` test failed intermittently on CI while running fine on my laptop. Given that the failures ends with a timeout from what I observed, I'm suspecting CI's cpu cannot spinning up `geth` within current 5s timeout. So I set timeout to 15s, and managed run it 1000 times on CI without failure. ### Other changes - Deletes redundant `datadir` setup in the test. ### Tested Run `TestRegistryInGenesis` 1000 times under CircleCI job `test-TestRegistryInGenesis-1000-times`, no single failure. https://app.circleci.com/pipelines/github/celo-org/celo-blockchain/7107/workflows/342b4446-0a25-4c77-835c-d89dc5c29e84/jobs/70510 ### Backwards compatibility Yes, only modifies CircleCI config.
Hi,
I started geth mainnet using the following.
geth --networkid=12345 --genesis C:\Users\106862\genesis.json --datadir C:/Users/106862/.ethereum_experiment console
I also tried to get a private network going like the following.
geth --genesis example_genesis.json console
When I tried the above, I got a error to say Error String IPC: Access is denied.
I also tried forcing it to a different port like
geth --genedid example_genesis.json --port=35555 console
But i still got the same error.
Currently I have stopped the mainnet and running only the private network. This is making deploying contracts very difficult.
The text was updated successfully, but these errors were encountered: