Skip to content
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.

private-net mode not working under linux? #787

Closed
chiarelli opened this issue Jun 6, 2016 · 18 comments
Closed

private-net mode not working under linux? #787

chiarelli opened this issue Jun 6, 2016 · 18 comments

Comments

@chiarelli
Copy link

Node type: geth
OS: linux
Network type: NULL
Mist version: 0.7.4

O Modo PRIVATE-NET não está funcional em distros linux?
Apenas na compilação destinada para Windows consegui acessar essa funcionalidade, ou seja, inicio o "geth" com as configurações personalizadas e ao iniciar o mist ele roda no modo PRIVATE-NET. Ao fazer o mesmo procedimento na distro linux GNU-Ubuntu ocorre um erro.

@luclu
Copy link
Contributor

luclu commented Jun 6, 2016

from google-translator:

Die PRIVATE-NET-Modus ist in Linux-Distributionen nicht funktionsfähig ?
Nur bei der Erstellung für Windows könnte diese Funktionalität zugreifen, dh den Anfang "Geth" mit benutzerdefinierten Einstellungen und starten Sie den Nebel läuft es in PRIVATE-NET-Modus. Dadurch tritt das gleiche Verfahren in Linux-Distribution Ubuntu GNU-ein Fehler auf.

@luclu
Copy link
Contributor

luclu commented Jun 6, 2016

To use private-nets on any OS you have to externally start geth with the appropiate flags --networkid, etc. and connect Mist/Ethereum-Wallet after that to it.

@chiarelli
Copy link
Author

chiarelli commented Jun 6, 2016

Hello luclu,

I used the same configuration as the geth in both distros:

geth --identity "MyNodeName" --genesis ~/CustomGensis.json --rpc --rpcport "8000" --rpccorsdomain "*" --datadir "/home/raphael/ethereum-private_network" --ipcapi "admin,db,eth,debug,miner,net,shh,txpool,personal,web3" --rpcapi "db,eth,net,web3" --autodag --networkid 1900 --nat "any" console

However, only in the compilation for windows 7 PRIVATE-NET mode is functional, while in GNU-Ubuntu the mist returns an exception.

@luclu
Copy link
Contributor

luclu commented Jun 6, 2016

What kind of exception do you encounter?

@chiarelli
Copy link
Author

chiarelli commented Jun 6, 2016

The following screenshot:

exception-mist

exception-mist-2

However I realize the same procedure and settings in Windows 7 and mist starts normally.

@luclu
Copy link
Contributor

luclu commented Jun 6, 2016

The last line states that the port 30303 is already used. Make sure there is no other instance of geth running - use pgrep geth / pkill geth.

@chiarelli
Copy link
Author

There is no other instance of running geth, I had already seen it before, but the build for Windows 7 this problem does not occur.

@luclu
Copy link
Contributor

luclu commented Jun 6, 2016

Could you try to append geth with the --ipcpath-flag parsing the default location of the ipc-socket.

@chiarelli
Copy link
Author

luclu, I did what you asked adding --ippath but there was the same problem.

@luclu
Copy link
Contributor

luclu commented Jun 7, 2016

What happens when you only start Mist with default settings?

@chiarelli
Copy link
Author

mist starts normally.

@luclu
Copy link
Contributor

luclu commented Jun 7, 2016

Can you try to strip down your geth flags or build them up with --networkid 2 (morden testnet) - to isolate the issue?

@chiarelli
Copy link
Author

Do you believe that this could be a bug in the Linux build?

For now I can only run PRIVATE-NET mode in windows ...

I hope the developer solve this problem in the next update for linux distros.

@luclu
Copy link
Contributor

luclu commented Jun 7, 2016

I don't really thing so, but it could be...

If you want to spare some time helping try to strip down your command-flags one by one - to isolate the issue.

Can you try to strip down your geth flags or build them up with --networkid 2 (morden testnet) - to isolate the issue?

@luclu luclu changed the title O modo PRIVATE-NET está disponível para distros linux? private-net mode not working under linux? Jun 20, 2016
@IvanDePivan
Copy link

I am currently experiencing the same issue. I think the wallet might not be able to find the geth.ipc file, possibly expecting it somewhere else. If it then starts its own geth instance, this will fail due to the port being in use.

@luclu
Copy link
Contributor

luclu commented Sep 19, 2016

@armed10 this might be related to #1165.

@evertonfraga
Copy link
Member

Closing upon inactivity. Please reopen if needed.

@lock
Copy link

lock bot commented Mar 30, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants