Quorum 7nodes example all of sudden gave fatal error unable to attach to remote geth. Problem: can't attach to geth node Every time I import metamask account to geth node (using personal.importRawKey("private key", "password")) to use that account to interact with Dapp using metamask. when i restart the machine and try to open geth node I am unable to access that particular geth node(let say node 1) but all other nodes work fine.

PFA screenshot enter image description here

  • 1
    Are you running this using Vagrant + VirtualBox? If so, one thing would be to check the available memory in your virtual environment. Do the IPC endpoints actually exist under the qdata/dd<x>/ directories? – Richard Horrocks Oct 11 at 10:04
  • yes I am using vagrant and VirtualBox , and i can see a file names geth.ipc under the qdata/dd<x> folder. – Surbhi Audichya Oct 12 at 5:40

This sounds like a memory issue, but you should look into the logs available in qdata/logs folder.

Latest quorum-examples updates memory requirement to 6GB, tho the minimum is 4GB for all 7nodes to run simultaneously.

  • This problem occurred after I imported metamask account to Quorum geth node/s (using personal.importRawKey) . after restart only those node stopped working in which i imported account. – Surbhi Audichya Oct 19 at 9:35
  • This is odd, probably best to join our Slack and debug in real time with the devs or maybe open an issue on github – fixanoid 3 hours ago

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.