Spectrometer failure when starting web
Jayathirth, Pramod Raghavendra <pramod.raghavendra.jayathirth@...>
Hi All,
I get the following error when I try to start web. I followed https://opendaylight-spectrometer.readthedocs.io/en/latest/quickstart.html#setup-spectrometer-web and when I try “npm start”, I get the following error.
npm ERR! Linux 4.2.0-42-generic npm ERR! argv "/home/otc/.nvm/versions/node/v4.6.2/bin/node" "/home/otc/.nvm/versions/node/v4.6.2/bin/npm" "start" npm ERR! node v4.6.2 npm ERR! npm v4.0.5 npm ERR! code ELIFECYCLE npm ERR! opendaylight-spectrometer-web@0.0.1 start: `export NODE_ENV=development && node src/server/index.js --progress --colors --profile` npm ERR! Exit status 1
Can anyone point me how to resolve this? Or any work around?
Regards, Pramod Raghavendra Jayathirth
|
|
Thomas Nadeau
Vish is working on pushing some patches that update the base node libs. I wonder if this will fix your issue. —Tom
|
|
Raghuram Vadapalli <raghuram.4350@...>
Hi Jayathirth, Can you check if port 8000 is being used by any other process. Regards, Raghuram On Sat, Jan 14, 2017 at 7:13 PM Thomas Nadeau <tnadeau@...> wrote:
|
|
jaspreet singh
Hi! This is the same error I got. Updating "package.json" to have "react-tap-event-plugin": "^2.0.0" gave warning at installation but ran fine with npm start. Maybe you can try that. @spectrometer-devs Thanks Jaspreet Singh On Sat, Jan 14, 2017 at 7:13 PM, Thomas Nadeau <tnadeau@...> wrote:
|
|
Vasu Srinivasan <vasya10@...>
I am working on a patch to upgrade all package.json to latest npm modules. But that has caused one other issue in the code. Will be submitting the patch soon. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Sun, Jan 15, 2017 at 3:44 AM, jaspreet singh <jaspreetsingh112@...> wrote:
|
|
Vasu Srinivasan <vasya10@...>
Meanwhile, just to get it working, please use Jaspreet's workaround. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Tue, Jan 17, 2017 at 12:01 PM, Vasu Srinivasan <vasya10@...> wrote:
|
|
Thomas Nadeau
Jaspreet, Please hang in there. With the update of packages we now have to make a few fixes. We’re looking at them now and will push a patch shortly to fix this. —tom
|
|