search

calxibe / StorjMonitor

Node.js script for publishing data from local Storj nodes to Storjstat.com
15 stars 14 forks source link

how do I run this in Linux? #11

Closed aristosv closed 6 years ago

aristosv commented 6 years ago

can anyone explain how to run this on Linux? (Debian) I have storj up and running, all disks are connected. I downloaded StorjMonitor-master.zip, put my API key in storjMonitor.js, chmod +x storjMonitor.sh and run it.

I get a message ./storjMonitor.sh: line 1: /usr/bin/node: No such file or directory which makes sense because /usr/bin/node does not exist.

So how do I run this?

stefanbenten commented 6 years ago

@aristosv Run this script:

git clone https://github.com/calxibe/StorjMonitor.git
cd StorjMonitor
rm -rf node_modules
npm install
chmod +x storjMonitor.sh

Edit the storjMonitor.js and insert your API Key. Then delete the path /usr/bin/ from the storjMonitor.sh and run

sudo apt get install screen -y
screen -dmS SMonitor ./storjMonitor.sh
MrTechGadget commented 6 years ago

ust tryIf you don’t want to install screens, you can just run this...

node storjMonitor.js &

On Sat, Feb 17, 2018 at 12:32 PM aristosv notifications@github.com wrote:

can anyone explain how to run this on Linux? (Debian) I have storj up and running, all disks are connected. I downloaded StorjMonitor-master.zip, put my API key in storjMonitor.js, chmod +x storjMonitor.sh and run it.

I get a message ./storjMonitor.sh: line 1: /usr/bin/node: No such file or directory which makes sense because /usr/bin/node does not exist.

So how do I run this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/calxibe/StorjMonitor/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/AQVLdSfIQPdss8GrVprmIu-v_QKDQajkks5tVw0WgaJpZM4SJY53 .

stefanbenten commented 6 years ago

@audioeng But then you run it on the foreground, which is unfortunate, when you want to use the system

MrTechGadget commented 6 years ago

That’s what the & does, puts it in background On Sun, Feb 18, 2018 at 8:20 AM Stefan Benten notifications@github.com wrote:

@audioeng https://github.com/audioeng But then you run it on the foreground, which is unfortunate, when you want to use the system

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/calxibe/StorjMonitor/issues/11#issuecomment-366519417, or mute the thread https://github.com/notifications/unsubscribe-auth/AQVLdbZ0CfsHkOq4GDXbyankmMZ7yiAaks5tWDGVgaJpZM4SJY53 .

stefanbenten commented 6 years ago

But how do you connect back to it? Its just my recommendation.

MrTechGadget commented 6 years ago

Yes screens can be helpful if you want to connect back to it... I can’t think of a reason you would need to though. I just kill the process and run it again if needed.

You can resume without screens using bg though. https://www.systutorials.com/docs/linux/man/1p-bg/ On Sun, Feb 18, 2018 at 8:24 AM Stefan Benten notifications@github.com wrote:

But how do you connect back to it? Its just my recommendation.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/calxibe/StorjMonitor/issues/11#issuecomment-366519673, or mute the thread https://github.com/notifications/unsubscribe-auth/AQVLdY-VtMGK2hdtGJs2BoGqm_cNrBjxks5tWDKNgaJpZM4SJY53 .

stefanbenten commented 6 years ago

I would like to know why it failed to report. Just putting things into background especially for monitoring software isnt the best programming style imho. Another smart approach can be to create a log and push it into that, then you're correct @audioeng

MrTechGadget commented 6 years ago

Yes, I agree, piping output to a log is preferred.

Personally, I just added logic to send a push notification to my phone using pushover, so I know how much data is being used. I don’t worry about the output of the script, as Storjstat will show a ! on your nodes page if it doesn’t report in a period of time. On Sun, Feb 18, 2018 at 8:40 AM Stefan Benten notifications@github.com wrote:

I would like to know why it failed to report. Just putting things into background especially for monitoring software isnt the best programming style imho. Another smart approach can be to create a log and push it into that, then you're correct @audioeng https://github.com/audioeng

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/calxibe/StorjMonitor/issues/11#issuecomment-366520739, or mute the thread https://github.com/notifications/unsubscribe-auth/AQVLdXVDhcSEHORvAAXqH0ZVD6r6Lop0ks5tWDZ0gaJpZM4SJY53 .

MrTechGadget commented 6 years ago

node storjMonitor.js &> output.log &

Will accomplish that, send it to background and send stdin and stderr to output.log