embark icon indicating copy to clipboard operation
embark copied to clipboard

embark run geth error: Incorrect Usage. flag provided but not defined: -wsport

Open suifeng1120 opened this issue 4 years ago • 3 comments

Bug Report

Summary

Current behavior

How to reproduce

Expected behavior

If you encounter an error, please create a logfile using the following command and post the output here

$ embark run --nodashboard --logfile log.txt --loglevel trace

Please provide additional information about your system

OS: Embark Version: Node Version: NPM Version:

Sometimes issues are related to Embark's installation. Can you provide information on how Embark was installed?

suifeng1120 avatar Apr 19 '21 08:04 suifeng1120

I have the same question and I supposed that the latest version of geth(go-ethereum) changing its usage caused such issue. Thus, I try to downgrade my geth, however, when I make the [email protected] from source code, some fatal errors occur to me. So, we need the help of embark's developer on edge.

aibot88 avatar May 25 '21 03:05 aibot88

I am having that problem. This is a fresh install of ubuntu 20 in amazon aws for this purpose and followed the steps here https://framework.embarklabs.io/docs/installation.html going into each installation guide. You can see the full teck stack with versions at the bottom. I am brand new to smart contracts so I may have done something stupid but willing to try out different things if you want. Right now, it seems like the way to get this working is to manually downgrade geth? Also note $ embark blockchain works fine.

the log.txt file was empty (but created). The output on the screen was embark info invoked /home/ubuntu/.nvm/versions/node/v10.17.0/lib/node_modules/embark/bin/embark embark info located /home/ubuntu/embark_demo/node_modules/embark/bin/embark embark info Switching from [email protected] to [email protected]

===== locale C detected but not supported, default: en ===== pid 250732 listening on /tmp/embark-81ae7976/embark.ipc

Welcome to Embark 6.0.0

add check: Embark add check: Webserver loaded plugins: embark-ipfs, embark-swarm, embark-whisper-geth, embark-geth, embark-parity, embark-profiler, embark-graph, embark-basic-pipeline startMonitor

/home/ubuntu/embark_demo/node_modules/embark-logger/src/index.js:54 if (isDebugOrTrace) origin = ${DELIM}${task.origin.match(/^at\s+.*(\(.*\))/)[1] || '(unknown)'}; ^ TypeError: Cannot read property '1' of null at call.task (/home/ubuntu/embark_demo/node_modules/embark-logger/src/index.js:54:49) at Array.forEach () at Logger.writeToFile.async.cargo (/home/ubuntu/embark_demo/node_modules/embark-logger/src/index.js:48:12) at Object.process (/home/ubuntu/embark_demo/node_modules/async/dist/async.js:1427:21) at setImmediate$1 (/home/ubuntu/embark_demo/node_modules/async/dist/async.js:1285:23) at Immediate.defer (/home/ubuntu/embark_demo/node_modules/async/dist/async.js:73:45) at runCallback (timers.js:705:18) at tryOnImmediate (timers.js:676:5) at processImmediate (timers.js:658:5) at process.topLevelDomainCallback (domain.js:126:23)

OS Version Ubuntu 20.04.2 LTS Embark version 6.0.0 Node Version: v10.17.0 npm version 6.11.3 ipfs version 0.8.0 Geth Version: 1.10.3-stable

sk8ermeb avatar Jun 09 '21 23:06 sk8ermeb

Just FYI downgrading geth to version listed in the tutorial 1.8.15, while a huge headache to get working, did fix the problem

sk8ermeb avatar Jun 10 '21 04:06 sk8ermeb