Mist: MIST couldnt connect to node even geth is running

Created on 15 Feb 2017  路  17Comments  路  Source: ethereum/mist

System information

Version: Geth 1.5.9 OS & Version: windows 10 Node type: `eth/geth

I'm new to this. I've installed mist and everything working fine. I start farming and i dont see any updates on my wallet. After much google, it might cause by my geth is not sync with my mist. So i've installed GETH 1.5.9 . I've enter Geth -removedb , and i've enter again geth -fast . Alot of txt keep running, it's been a day + , and maybe i've missed any word that shows it's sync. So i try run my mist and this error popup.

Again , i've tried geth.exe --nat=extip:my public ip. it start to run on geth . but i tried to run mist, it still gives me the same error. my mist is 0.8.9 installed version. Please help coz im stucked here .

Triage help wanted v0.8.9

Most helpful comment

Could you please check if any external instance of geth is running. This might cause this error if the path to the geth.ipc file differs from the Mist default and hasn't been adjusted using mist(.exe) --rpc <path/to/geth.ip>.

If Mist doesn't find geth.ipc at the assumed location it will try to start its own instance of geth, which will in turn collide with the running one.

There are efforts to standardize the name and location of this file (to ethereum.ipc). Meanwhile this unhelpful error message will pop up.

All 17 comments

mist error

I tried latest Mist on Windows 10 (64-Bit)
capture 16-02-2017

After downloading and installing new Mist(0.8.9 64-Bit Installer for Windows), I am also getting same error, don't know the reason... I tried everything changing directories, removing chaindata folder but nothing is working, can anyone please help...

is my wallet safe? how do i recover from this issue?

If i remove local database, I get even bigger error message and unable to download from scratch.
I am unable to sync wallet even from older versions of Mist... what should I do now?

new error now...

capture 18-02-2017

I have the exact same error message. I removed the chain data folder because the sync was very slow and after using geth--fast --cache=1024. I get the same error message about the ledger hub.

Could you please check if any external instance of geth is running. This might cause this error if the path to the geth.ipc file differs from the Mist default and hasn't been adjusted using mist(.exe) --rpc <path/to/geth.ip>.

If Mist doesn't find geth.ipc at the assumed location it will try to start its own instance of geth, which will in turn collide with the running one.

There are efforts to standardize the name and location of this file (to ethereum.ipc). Meanwhile this unhelpful error message will pop up.

Oops

Having the exact same issue and error message. There is no other geth instance running. I can't even find geth.ipc where should it be located?

Having the same issue with Ethereum Wallet btw. Staring just geth from the command line works fine however.

Rebooting didn't help. I did move the datadir before this happened but I'm unsure if that is part of the issue.
Getting this exact error just like the user above.

063f7a1e-f625-11e6-9127-c4869159e1f2


System information

Version: `0.0.0` OS & Version: windows/linux/osx Node type: `eth/geth(default)`

Please check the already existing issues to keep duplicates at a minimum.

Furthermore several work-arounds have been collected in the Mist-Troubleshooting-Guide.

If possible add the following to your report:

  • Screenshots

  • Check the console, of Mist (CTRL/CMD + ALT + i) and take a screenshot

  • Log files

    • go to menu -> accounts -> backup -> application data
    • zip and upload node.log and all other node.log.X files

@tinodesigns I added the issue template to your latest post. Could you please fill out as much as possible? Especially the node.log is appreciated.

1)Finally, I deleted all the chaindata... unblocked my Ethereum wallet account using this link:
https://www.myetherwallet.com/#view-wallet-info
2) updated to latest Mist
3) again downloaded all the chaindata from scratch, before chaindata folder size was more than 81 GB, now it is just more than 10 GB :)
4) Problem solved, Mist is working fine now...

Thank you all for helping out...

@luclu thanks a lot for all your support. Sorry about the late reply. Here are my details:

Version: 0.8.9
OS & Version: win 7 professional 64bit
Node type: geth(default)

screenshot_mist_error

The node.log reall only holds this info:
I0317 18:28:37.045182 node/config.go:445] Failed to start Ledger hub, disabling: libusb: not found [code -5]
I0317 18:28:37.088185 ethdb/database.go:83] Allotted 1024MB cache and 1024 file handles to C:\Users\Tino\AppData\Roaming\Ethereum\chaindata

grafik
(couldn't upload the node.log nor as .zip file, it said not supported file format, so I posted the screenshot and full contents. there are just the two lines in the node.log)

The only thing I did change was update to the latest mist and create a symbolic link using mklink in the DOS command prompt (http://www.computerhope.com/mklink.htm), to move the chaindata to a different disk with more space. This worked fine for geth in the command line, I was able to get the latest blocks that way but then Mist doesn't open with the above error.

May be I need to remove the symbolic link and try again? But then it will sync to my system hardrive again, something I need to avoid because of spacing issues.

I'm having the exact same issue with Ethereum Wallet, also Version 0.8.9

Console Screenshot:
grafik

@luclu so removing my symoblic link (mklink in dos) and moving the data back to the original location fixed this error.

But now my question how can I specify a different data directory than the default one? I'd need that space. 12 GB is a lot on 120GB SSD.

Thanks

Again the symbolic links works fine with Geth but not with Mist or Ethereum Wallet

symbolic link do work with latest mist, i just reinstalled the mist and again downloaded the blockchain... it is working fine for now.... don't know what made it corrupt, i think my keydata in wallet was corrupted...

We need help investigating and implementing a potential fix for this. PRs are welcome :)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sluTTYusr picture sluTTYusr  路  3Comments

ibart7 picture ibart7  路  6Comments

Raindownchips picture Raindownchips  路  6Comments

tomtom87 picture tomtom87  路  4Comments

ivica7 picture ivica7  路  6Comments