Pages:
Author

Topic: Closed Thread - page 74. (Read 677703 times)

full member
Activity: 175
Merit: 100
March 05, 2015, 02:35:03 PM
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 (/root/node/index.js:9:38), :1:83006)
    at /root/node/index.js:16:5
    at b (domain.js:183:18)
    at Domain.run (domain.js:123:23)
    at Object. (/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.
full member
Activity: 231
Merit: 100
March 05, 2015, 10:35:24 AM
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)
full member
Activity: 175
Merit: 100
March 05, 2015, 09:55:04 AM
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
legendary
Activity: 1181
Merit: 1018
March 05, 2015, 09:34:38 AM
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?

full member
Activity: 175
Merit: 100
March 05, 2015, 09:23:51 AM
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.
sr. member
Activity: 462
Merit: 250
March 05, 2015, 09:17:37 AM
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
member
Activity: 93
Merit: 10
March 05, 2015, 07:31:01 AM
'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?
full member
Activity: 175
Merit: 100
March 05, 2015, 06:56:02 AM
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
sr. member
Activity: 462
Merit: 250
March 04, 2015, 09:34:10 PM
In my experience running linux host if you have the file - you do not need to log in.
I tried it last week: restarted my service and did not log in - and my node was shown with correct account as a peer.


Well if you don't need to manually log in then keep doing that.  The new version, in my experience, wasn't looking into the clientConfig.js file for the account number so I had to create an SSL port to log in.  Either way, I feel more secure not keeping my account pass in a file that is on a remote VPS.
newbie
Activity: 21
Merit: 0
March 04, 2015, 09:31:07 PM
Wow, I really can't get this to work in Linux. Can't find the 'lib' folder the explanation is talking about. It's not in the repository, so it seems.

https://github.com/nodepay/Docs/blob/master/Instructions.md

The lib folder contains one file clientConfig.js with the following content:

var ClientConfig = (function() {
 return {
  accName: 'YourPasswordGoesHere'
 };
})();

module.exports = ClientConfig;

The new client doesn't include it.  You have to manually log into your client from the main screen.

But before you do that, make sure you set up a secure SSL port for extra security.

In my experience running linux host if you have the file - you do not need to log in.
I tried it last week: restarted my service and did not log in - and my node was shown with correct account as a peer.
sr. member
Activity: 462
Merit: 250
March 04, 2015, 09:29:16 PM
Links for the wallets have finally been fixed.

The link pointing to the block explorer still points to port 19775, it should be 18775.

Question: What is going on with block explorer? It hasn't worked since the port switch to 18775
sr. member
Activity: 462
Merit: 250
March 04, 2015, 09:06:52 PM
Wow, I really can't get this to work in Linux. Can't find the 'lib' folder the explanation is talking about. It's not in the repository, so it seems.

https://github.com/nodepay/Docs/blob/master/Instructions.md

The lib folder contains one file clientConfig.js with the following content:

var ClientConfig = (function() {
 return {
  accName: 'YourPasswordGoesHere'
 };
})();

module.exports = ClientConfig;

The new client doesn't include it.  You have to manually log into your client from the main screen.

But before you do that, make sure you set up a secure SSL port for extra security.
newbie
Activity: 21
Merit: 0
March 04, 2015, 08:35:04 PM
Wow, I really can't get this to work in Linux. Can't find the 'lib' folder the explanation is talking about. It's not in the repository, so it seems.

https://github.com/nodepay/Docs/blob/master/Instructions.md

The lib folder contains one file clientConfig.js with the following content:

var ClientConfig = (function() {
 return {
  accName: 'YourPasswordGoesHere'
 };
})();

module.exports = ClientConfig;
legendary
Activity: 1453
Merit: 1030
March 04, 2015, 07:36:30 PM
Wow, I really can't get this to work in Linux. Can't find the 'lib' folder the explanation is talking about. It's not in the repository, so it seems.

https://github.com/nodepay/Docs/blob/master/Instructions.md
hero member
Activity: 965
Merit: 515
March 04, 2015, 04:34:27 PM

Block height # 11843

Thank you.  That has helped me. I got it working now. Seems you really have to download it without interruption at least if you use the win client. Hope they can fix that because that could create trouble in the future.

And thanks also for the link of the blockchain download.

Now I will wait on Bter
legendary
Activity: 3836
Merit: 4969
Doomed to see the future and unable to prevent it
March 04, 2015, 04:15:33 PM
Besides what happened to NODEclub?  Did they fire him after a couple of months?  Had his hands in the jar full of shekels meant for the goat procurement fund?   Shocked



As koop4u & NODEclub they are busy with personal Affairs , we will give promotional Fund at the disposal of the community. The community will need to choose the main promoter

4 days later and the windows/linux download links in the OP are still reversed. Is the Node team brain damaged or just lazy?

I don't know, koop4u has logged in today. So Huh??
hero member
Activity: 605
Merit: 500
March 04, 2015, 04:07:41 PM
Besides what happened to NODEclub?  Did they fire him after a couple of months?  Had his hands in the jar full of shekels meant for the goat procurement fund?   Shocked



As koop4u & NODEclub they are busy with personal Affairs , we will give promotional Fund at the disposal of the community. The community will need to choose the main promoter

4 days later and the windows/linux download links in the OP are still reversed. Is the Node team brain damaged or just lazy?
full member
Activity: 734
Merit: 109
March 04, 2015, 03:57:56 PM
Hi,

I have a problem. I tried to send to alcurEX some Node, but it has only 2 confirmations. It needed 3. I initiated this transaction am march 2, 2015... 2 days ago.

Incoming transactions:
Currency    Amount    confirmations left    Transaction id
NODE      884.89200000    1    14221985297230183940


What to do?
which NODE version you are using? Latest is 0.9.6
I use win64 - Version 0.9.6
3x2
legendary
Activity: 1526
Merit: 1004
March 04, 2015, 03:49:59 PM
Hi,

I have a problem. I tried to send to alcurEX some Node, but it has only 2 confirmations. It needed 3. I initiated this transaction am march 2, 2015... 2 days ago.

Incoming transactions:
Currency    Amount    confirmations left    Transaction id
NODE      884.89200000    1    14221985297230183940


What to do?
which NODE version you are using? Latest is 0.9.6
full member
Activity: 734
Merit: 109
March 04, 2015, 03:47:21 PM
Hi,

I have a problem. I tried to send to alcurEX some Node, but it has only 2 confirmations. It needed 3. I initiated this transaction am march 2, 2015... 2 days ago.

Incoming transactions:
Currency    Amount    confirmations left    Transaction id
NODE      884.89200000    1    14221985297230183940


What to do?
Pages:
Jump to: