Closed Thread

[kevinkk525]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

[Nexxie]

'Blockchain verified complaite, wait synced blocks'
What does it mean?

It should be changed to :
'Blockchain verification complete, waiting for synched blocks'
Has been addressed several times to devs...

You have downloaded the latest version?

yes I think so...
Where can I find the latest Mac client?

[LemonAndFries]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

[kevinkk525]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

[l8orre]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

 I needed to do 'SUDO npm -g install forever' maybe that is your problem?

[kevinkk525]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

I needed to do 'SUDO npm -g install forever' maybe that is your problem?

no I'm running it as root.
what I did until now: installing nodejs 10.36, npm
downloading and extracting latest client,adding lib folder and clientConfig.js (as mentioned in the last posts)
npm -g install
npm -g install forever
forever start index.js --> shortly starts a nodejs process
forever stop index.js --> error: no process with id: index.js

[rramires]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

I needed to do 'SUDO npm -g install forever' maybe that is your problem?

no I'm running it as root.
what I did until now: installing nodejs 10.36, npm
downloading and extracting latest client,adding lib folder and clientConfig.js (as mentioned in the last posts)
npm -g install
npm -g install forever
forever start index.js --> shortly starts a nodejs process
forever stop index.js --> error: no process with id: index.js

You are giving these commands in the root folder where the node is extracted, where is index.js file?

To see the processes running under the "forever":
forever list


(The print is the windows, but the command is the same on Linux. Too lazy to enter the server now)

[kevinkk525]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

I needed to do 'SUDO npm -g install forever' maybe that is your problem?

no I'm running it as root.
what I did until now: installing nodejs 10.36, npm
downloading and extracting latest client,adding lib folder and clientConfig.js (as mentioned in the last posts)
npm -g install
npm -g install forever
forever start index.js --> shortly starts a nodejs process
forever stop index.js --> error: no process with id: index.js

You are giving these commands in the root folder where the node is extracted, where is index.js file?

To see the processes running under the "forever":
forever list


(The print is the windows, but the command is the same on Linux. Too lazy to enter the server now)

with that command I now found a log. and I was executing the commands in the same folder as index.js. It even starts shortly.

Code:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Cannot find module 'step'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at run (eval at <anonymous> (/root/node/index.js:9:38), <anonymous>:1:83006)
    at /root/node/index.js:16:5
    at b (domain.js:183:18)
    at Domain.run (domain.js:123:23)
    at Object.<anonymous> (/root/node/index.js:5:14)
    at Module._compile (module.js:456:26)
error: Forever detected script exited with code: 7

That is the error log of forever.

[michaelf77]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

I needed to do 'SUDO npm -g install forever' maybe that is your problem?

no I'm running it as root.
what I did until now: installing nodejs 10.36, npm
downloading and extracting latest client,adding lib folder and clientConfig.js (as mentioned in the last posts)
npm -g install
npm -g install forever
forever start index.js --> shortly starts a nodejs process
forever stop index.js --> error: no process with id: index.js

You are giving these commands in the root folder where the node is extracted, where is index.js file?

To see the processes running under the "forever":
forever list

http://s8.postimg.org/bmncsrgbp/forever.jpg
(The print is the windows, but the command is the same on Linux. Too lazy to enter the server now)

with that command I now found a log. and I was executing the commands in the same folder as index.js. It even starts shortly.

Code:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Cannot find module 'step'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at run (eval at <anonymous> (/root/node/index.js:9:38), <anonymous>:1:83006)
    at /root/node/index.js:16:5
    at b (domain.js:183:18)
    at Domain.run (domain.js:123:23)
    at Object.<anonymous> (/root/node/index.js:5:14)
    at Module._compile (module.js:456:26)
error: Forever detected script exited with code: 7

That is the error log of forever.

From /root/Node run :
npm install
npm update

(note: no -G )

[kevinkk525]

I always had no problem getting node running on my linux vps. but with this version it does not work even after adding the lib folder with clientConfig.js... I start it with forever start index.js - no error.. but also no process. forever stop index.js gives an error "Forever cannot find process with id: index.js".
Did I miss something?
My nodejs version is 10.36

Same issue I had at first.
Do this again:

 9) npm -g install forever

sadly this did not work. Same problem as before. No logs or additional errors.

I needed to do 'SUDO npm -g install forever' maybe that is your problem?

no I'm running it as root.
what I did until now: installing nodejs 10.36, npm
downloading and extracting latest client,adding lib folder and clientConfig.js (as mentioned in the last posts)
npm -g install
npm -g install forever
forever start index.js --> shortly starts a nodejs process
forever stop index.js --> error: no process with id: index.js

You are giving these commands in the root folder where the node is extracted, where is index.js file?

To see the processes running under the "forever":
forever list


(The print is the windows, but the command is the same on Linux. Too lazy to enter the server now)

with that command I now found a log. and I was executing the commands in the same folder as index.js. It even starts shortly.

Code:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Cannot find module 'step'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at run (eval at <anonymous> (/root/node/index.js:9:38), <anonymous>:1:83006)
    at /root/node/index.js:16:5
    at b (domain.js:183:18)
    at Domain.run (domain.js:123:23)
    at Object.<anonymous> (/root/node/index.js:5:14)
    at Module._compile (module.js:456:26)
error: Forever detected script exited with code: 7

That is the error log of forever.

From /root/Node run :
npm install
npm update

(note: no -G )

Thanks a lot! That did it. Finally it works.

[kevinkk525]

When will be able to put our AccountID in the clientConfig.js and not our private passphrase? This is getting a greater security problem as node gets more valuable and may be worth for some to try to hack those systems.

[TheRealSilk]

When will be able to put our AccountID in the clientConfig.js and not our private passphrase? This is getting a greater security problem as node gets more valuable and may be worth for some to try to hack those systems.

In the next version

[kevinkk525]

When will be able to put our AccountID in the clientConfig.js and not our private passphrase? This is getting a greater security problem as node gets more valuable and may be worth for some to try to hack those systems.

In the next version

Very good! Thanks.

[Thiball]

Sorry to bother you but I bought a Raspberry Pi 2 and I don't know how to use the wallet on it.

Can someone does a full and update explanation please ? Could be great for the future.

Thank you

[Nexxie]

'Blockchain verified complaite, wait synced blocks'
What does it mean?

It should be changed to :
'Blockchain verification complete, waiting for synched blocks'
Has been addressed several times to devs...

You have downloaded the latest version?

yes I think so...
Where can I find the latest Mac client?

where can I find the latest Mac client? thanks

[kevinkk525]

Sorry to bother you but I bought a Raspberry Pi 2 and I don't know how to use the wallet on it.

Can someone does a full and update explanation please ? Could be great for the future.

Thank you

This was the way I managed to run NODE on my RPi 2:
Follow this instructions to install node and npm: http://weworkweplay.com/play/raspberry-pi-nodejs/
After that download the client and go to the extracted folder with index.js and run the commands: "npm install" and "npm update"
Then "npm -g install forever" and "forever start index.js" (like the node instructions)

But be aware, the NODE client takes ~250MB of RAM which is already 25% of what we have.
And the GUI is quite slow so don't expext to see the latest blocks within 20 sec ;-)
And download the bloackchain before. Verification still takes ages.

[CryingMidget]

Nodes are getting super cheap on Alcurex, managed to pick some nodes up at around 70 satoshi today.  Buy now if you want some cheap coins.

[Seedeer]

Nodes are getting super cheap on Alcurex, managed to pick some nodes up at around 70 satoshi today.  Buy now if you want some cheap coins.

...or sell if you think it will go lower

[whitecloud]

Nodes are getting super cheap on Alcurex, managed to pick some nodes up at around 70 satoshi today.  Buy now if you want some cheap coins.

...or sell if you think it will go lower

...yes, sell! 

[Thiball]

Sorry to bother you but I bought a Raspberry Pi 2 and I don't know how to use the wallet on it.

Can someone does a full and update explanation please ? Could be great for the future.

Thank you

This was the way I managed to run NODE on my RPi 2:
Follow this instructions to install node and npm: http://weworkweplay.com/play/raspberry-pi-nodejs/
After that download the client and go to the extracted folder with index.js and run the commands: "npm install" and "npm update"
Then "npm -g install forever" and "forever start index.js" (like the node instructions)

But be aware, the NODE client takes ~250MB of RAM which is already 25% of what we have.
And the GUI is quite slow so don't expext to see the latest blocks within 20 sec ;-)
And download the bloackchain before. Verification still takes ages.

Thank you very much. I think it's working, I've done the "forever start index.js" thing and my CPU is working around 25% for 10 minutes. But I don't see the GUI. I suppose it's normal ?

And I didn't download the blockchain by myself because I just don't know how to do and use it ^^

Edit : I downloaded the blockchain from here : https://mega.co.nz/#!AxhXiDAb!7yyUoUJOl1O6BOZZSZtQQsHt3rD0VOQc9YCU1o-mMtM
I put it into my db files and reboot. I suppose I just have to wait a little bit...