Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fatal: Error starting protocol stack
See original GitHub issueSuccessfully ran embark new TokenFactory but if I do embark blockchain, I get this:
Fatal: Error starting protocol stack: listen unix
Full log output here.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Fatal: Error starting protocol stack: Access is denied. #14438
Fatal : Error starting protocol stack: Access is denied. #14438. Closed. swathi08 opened this issue on May 7, 2017 · 12 comments.
Read more >Fatal: Error starting protocol stack: ... Access is denied
This occurs when you have another instance of geth already running. Use your Operating System's process handler to end the process if there ......
Read more >Can not open geth console Fatal Error starting protocol stack ...
Can not open geth console Fatal Error starting protocol stack listen tcp 30303 bind address already in use.
Read more >If IPC is not disabled in second node you may get below error.
Fatal : Error starting protocol stack: Access is denied. Use — ipcdisable parameter when starting second node. geth — datadir data2 — port...
Read more >Fatal: Error starting protocol stack: listen tcp 127.0.0.1:8551: bind
Fatal : Error starting protocol stack: listen tcp 127.0.0.1:8551: bind: Only one usage of each socket address (protocol/network address/port) is ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@PaulRBerg @troydo42
Good news I found the problem. Go-Ethereum doesn’t like long paths… You’ll have to put the project in a shorter path if you intend to use go-ethereum (embark blokchain), at least until the issue is fixed.
e.g:
works:
/Users/iurimatias/Documents/TokenFactory/Users/iurimatias/Projects/tmp/TokenFactorydoesn’t work:
/Users/iurimatias/Documents/projects/ef/dev/src/eth/embark/TokenFactory/In embark 3.1 we detect this situation and show a warning to the user