mist
mist copied to clipboard
ethereum
Ethereum-Wallet-win64-0-11-0 - does not find geth v1.8.11 in Node option
Trying to migrate with standalone version from Ethereum-Wallet-win64-0-10-0 to Ethereum-Wallet-win64-0-11-0.
I run geth.exe (v1.8.11) first because I use a custom location for blockchain data, so geth.exe is running and synced before wallet start.
v0-10-0 finds geth.exe and runs with no issues - shows 'Geth 1.8.11' in Node option menu. All good here.
v0-11-0 doesn't find geth.exe and either hangs, or loads into some default where my accounts have no names, and it is noth syncing. Does not show anything in Node option menu. Just blank.
Using light-client in every instance.
Hey, after you run geth get the IPC path that's outputted and then try launching Mist in the command line with --rpc path/to/geth.ipc
I thought I'd solved it by deleting everything in \AppData\Roaming\Ethereum Wallet, except the \binaries folder where I execute geth.exe from. It worked once after that. Something was messed up in there. But on quitting and starting everything back up again it fails to find peers.
The wallet still says REMOTE and there still nothing in the NODE menu. After clearing the \AppData\Roaming\Ethereum Wallet folder, it syncs and updates from geth.exe running in the background, but only for that instance.
Quitting and trying again, well, it fails.
Do you mean?
IPC endpoint opened
url=\\\\.\\pipe\\geth.ipc
Executing the following from CMD does nothing different:
"Ethereum Wallet.exe" --rpc \\\\.\\pipe\\geth.ipc
Hey. Just try running the wallet by itself, since it manages its own geth instance you don't have to start your own. Unless you want to run it off your own geth, then you'll want to find the exact absolute location of the IPC file then feed it in with --rpc
\\\\.\\pipe\\geth.ipc doesn't seem like a valid system file path
I can't find the path to geth.ipc, even when geth.exe is running. I know it should appear only when geth.exe is running and connected to peers (i.e. working), but geth.ipc is nowhere to be found. The best I have got from the terminal is the \\\\.\\pipe\\geth.ipc and if I --rpc into that it does nothing.
Additionally, now (as in not with v 0-10-0, which worked fine as it was), running Ethereum Wallet.exe by itself does nothing either. Sure, it creates the %appdata% folders (Ethereum Wallet and Etherum) with the corresponding files in one, and the chain data in another, except the chaindata doesn't grow. Spinning circle for eternity. Nothing in node menu.
Both Ethereum Wallet.exe and geth.exe are in the firewall, added, for TCP and UDP incoming.
Oddly, switching from 'light' to 'full' causes the application to do something, although it's unclear what right now. At the top it says REMOTE. It's stuck on 79%. I can't possibly have downloaded 79% of the chain in 10 seconds. Also, in this mode, Geth 1.8.11 shows in the node, but yet no peers, just REMOTE at the top.
Switching back to 'light' mode causes the spinning wheel to go away, and it works after quit/start Ethereum Wallet.exe (still by itself - no separate / custom geth.exe), but still says REMOTE at the top and now no geth in the node menu - just empty.
Even more weirdly, if I copy over my lightchaindata from my custom folder to the one inside %appdata%, and relaunch Ethereum Wallet.exe (no geth), it stops showing REMOTE and now says I have 3 or 4 peers. Still says nothing in the node menu though. No geth in here.
I think I've found a work-around...
Because I'm specifying --syncmode "light" for my geth.exe instance (so that I can specify a custom blockchain location away from the %appdata% folder, I must also specify --syncmode "light" for Ethereum Wallet.exe instance too. If I do this, then they play nicely together.
It doesn't show me any peers, and node menu is blank, but it's syncing. Changes to the geth.exe command line are reflected in the UI for the wallet. It also says REMOTE instead of Peers, but that's probably because it's connecting to an external geth source. I haven't --rpc'd anything.
Clunky! But this will do for now.
Is it possible to specify a custom blockchain path in the wallet UI (other wallets do it, e.g. LTC, BTC) - that would solve all my issues and there are bound to be others like me. I run a small boot SSD, so can't have a blockchain on my SSD.
0.10.0 would automatically connect to an already running geth node. 0.11.0 is not working properly, it does not automatically connect on start. Something is broken in the new release.
Ethereum-Wallet-Installer.exe on Windows 10
I agree... 0.11.0 would not attach to my node even when using --rpc localhost:8545 or --datadir specification as "Target" in the shortcut to Ethereum Wallet.
Switched back to 0.10.0 no issues. New release must have changed something to do with the windows build connecting to running nodes. The little splash screen with "LAUNCH APPLICATION" is gone now as well.
I managed to get geth with custom --data-dir working with 0.11.0 if I specify "light client" option for BOTH geth.exe AND ethereum wallet.exe. The wallet then shows updated blocks, but with a delay, and peers says REMOTE, rather than a number. NODE option in menus always shows (empty) though. It is definitely buggy IMHO.
On Thu, 19 Jul 2018 at 19:58, whizzard [email protected] wrote:
Ethereum-Wallet-Installer.exe on Windows 10
I agree... 0.11.0 would not attach to my node even when using --rpc localhost:8545 or --datadir specification as "Target" in the shortcut to Ethereum Wallet.
Switched back to 0.10.0 no issues. New release must have changed something to do with the windows build connecting to running nodes.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/3994#issuecomment-406380178, or mute the thread https://github.com/notifications/unsubscribe-auth/AX8VkTEte5Rh64n6in2PUBAQtZgc4HZJks5uINbrgaJpZM4VF9-o .
Additionally, with 0.11 I am unable to create NEW ACCOUNT. It works fine with 0.10. If I want a new account in 0.11, I first have to create it in 0.10, then it shows in 0.11. I still cannot make new accounts in 0.11 by itself...I have to use 0.10 to make the accounts. It seems to me that 0.11 is broken.