[ mining os ] nvoc - page 290. | Bitcointalksearch.org

TenaciousJ

full member

Activity: 122

Merit: 100

Quote from: eppy on July 16, 2017, 11:24:56 AM

Hi fullzero,

thank you for keeping this project alive and the constant updates.
I've been running 017 version on z270-hd3p gigabyte motherboard + 3 x 1080TI and a 1070 for almost 2 weeks now with no issues.

meanwhile does anyone have the issue with 018 version not working at all? ewbf does not even start. Most settings have been the same as from the onebash file in 017. Turned off most of the new additional features like watchdog and auto temp.
I've tried booting from an ssd as well as a 32gb sandisk ultra flair thumbdrive; I keep getting the error [Screen is terminating] at the end.

I understand the issue is most likely a configuration somewhere gone wrong, therefore it terminated before even trying to load ewbf miner, but was there such a drastic change from 017 to 018 that I missed out?

Would really like to find out if anyone faced a similar issue, so I iron it out and run ver 018.
Thanks!

I ran into the same problem after using the most current files. No idea what's causing it. I've disabled autotemp, watchdog, set to LOCAL, tried mizer on and off, etc. but nothing fixed it. I see EWBF load for 1/2 a second then that 'screen is terminating' message pops up. I think it might be related to watchdog, even though its disabled in the 1bash file, but I can't figure out how exactly.

TenaciousJ

full member

Activity: 122

Merit: 100

Quote from: ?? on ??

Quote from: OverEasy on July 18, 2017, 02:39:12 PM

Beats me Fullzero. My version of 1bash v. 18 has no way of executing the bash file Watchdog until I added it.
Just saying "yes" to the switch won't start it.

The other stuff does not work as I stated which is why I wrote my own part and edited out some stuff.

Maybe just me and my rig..shrug dunno.

I don't wanna mess up anyone with my crazy changes so I'll just keep em to myself for now unless I see others with similar issues.

This is getting big and complex. Ever consider client side program running in background and controlling stuff via a webpage?

Yes this is planned: monitor / push / update / dashboard app; keep getting sidetracked adding contributions / new coins.

The new 1bash should solve problems / start watchdog and autotemp in a screen when in remote.

Quote from: DJ ACK on July 18, 2017, 02:46:57 PM

Love the v0018 release and all the functionality!

However, POWERLIMIT NIGHTMARES!

I have one major issue, I cannot lower the POWERLIMIT. I run 8 rigs of 1050Ti and 125W is just way to high. I have tried adjusting the base line and the individual POWERLIMIT settings and I am still seeing maximum power being utilized in NVIDIA-SMI and TEMP CONTROL. I thought maybe the TEMP CONTROL was trumping the setting, but I don't think that is the case (at least based on what my 46 year old brain and eye balls looking at the 1bash code understands). I thought maybe it was the correction in line 527, but that didn't change anything.

I tried "NO" for both WATCHDOG and TEMP CONTROL with POWERLIMIT set below MAX for the 1050Ti and I still see max power output.

I did notice during startup, of the three terminal screens that pop-up during startup that the second terminal session has the POWERLIMIT set correctly at 60. However, something happens after the third terminal screen initiates (miner starting) that pushes the POWER back to MAX.

I added another rig of 1050Tis tonight and I saw more unusual behavior from POWER settings again where GPU0 goes to 125W as the max power limit and the rest of the GPUs all complied with my setting of 65Watts. I have no idea what is causing this inconsistency in power limit settings.

I also noticed in the Guake terminal that the TEMP CONTROL module is displaying continuous notifications that 125W is not a valid power limit (even after changing the settings in the module to 60-65).

I normally run all my rigs at 60W, which keeps the current draw low enough to run 3 rigs of 8 GPUs on each 15 AMP circuit. Also, extremely efficient.

I am still hunting for what is causing the forced 125W power setting.

Try the new 1bash and additional files posted on the OP. Let me know if it doesn't solve this for you.

I tried updating to the newest posted 1bash files as you suggested to resolve a problem where I have set the powerlimits for my cards individually, but the script changes one of my 1080ti cards (250w) to the power limit set for the 1070s (140w) so the card is only pulling 550sol instead of the 750 it should be.

I've triple checked my individual power limit settings vs. the GPU ID from Nvidia xserver against the powerlimit ID in the script, and they match. But it's not processing properly.

So after updating to the new 1bash fileset, it gets to the point where the fan settings are modified, the script loads the EWBF miner (for HUSH), and promptly crashes with the 'screen is terminated' message. I also have disabled autotemp and watchdog, but the problem persists.

Here's a screen shot of the problem that set this chain in motion showing the power draw of the cards vs. the powerlimit settings in 1bash and the IDs that were used in Xserver to match the powerlimits, and of the current problem.

http://imgur.com/a/zwf2s

I can't figure out what might be causing the miner to crash immediately on load like it is.. I've tried zeroing overclocks in case it was related to that, but that was no help. I ruled out power mizer by disabling that as well, but it crashes still.

I'm also set to LOCAL mode.

lance04

full member

Activity: 462

Merit: 112

Quote from: ?? on ??

Quote from: yun9999 on June 01, 2017, 09:14:19 PM

Which image for MSI Gaming 5 motherboard to support 7 GPU? Not sure if it's an issue with the image or something else but it wouldn't boot up even for the BIOS screen with the GPUs and NVOS flash drive connected when using the TB85 motherboard image.

For an MSI Z170-A GAMING M5 use this image:

Currently each image is unique so I can only ensure they will work for the mobo listed to support.

can use another mobo with 6 pcie ?
any brand ?

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: OverEasy on July 19, 2017, 11:25:51 AM

Quote from: Maxximus007 on July 19, 2017, 10:41:35 AM

Quote from: OverEasy on July 19, 2017, 09:39:07 AM

SSH users and new 1bash. You can no longer start things up by using bash 2unix as all the pastebin stuff is commented out.
You must now start up by SSH in to rig and run 1bash directly. Fullzero has placed the pastebin stuff in 1bash so make sure you edit 1bash first to remote and put your pastebin info in it.

For me personally new v18.1 does not work. Many many errors. Can't afford to have rig down to diagnosis right now so I am back to V.17 that works flawlessly for my purposes.

I would like to suggest making version 17 the "base" build as it works so well and incorporate all the features in as "modules" (separate programs), instead of adding all the code to the 1bash file.

File is getting so big it is hard to diagnosis stuff. Just one noobs opinion lol...

Yes, the 2unix has the pastebin out, and it's indeed quite handy in there to have a fitting 1bash directly. As fullzero already said, it will be modularized and optimized pretty soon, once it's on github. Currently there is just too much in one file, and makes it error prone. I use the new V0018 as a template, and removing parts I don't use.

Perhaps the first step should be separating the variables from the code with something like: source myvariables

It's still not a simple task for fullzero: There are many wishes, and for instance overclock is different per miner/coin etc..

TBH, I don't care too much to have all the possible (obscure) coins in it, if you want it, edit yourself (for now). Once it's split up in modules it's way easier to add additional coins.

I agree completely. Poor Fullzero is working overtime on this and giving it for free. I sure hope everyone is giving him some hash every once in a while. Hey Fullzero you should add your ETH or whatever you want to the code right at the top and comment it out. Most folks just open 1bash and delete yours and paste their address in. You are acknowledging everyone but yourself!

After reading the code: the new upPASTE will automatically update the default 1bash. So just change these lines in 1bash BEFORE booting (in the windows partition):

Code:

_Parallax_MODE="NO" # YES NO

pasteBASH="np9FSHew"

upPASTE_TIMEOUT_IN_MINUTES=30

And your rig will update 1bash within 30 minutes. So you will send a few hashes to fullzero, not a big problem I believe..

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: gyoztes on July 19, 2017, 11:29:03 AM

Quote from: Maxximus007 on July 19, 2017, 11:14:10 AM

Okay, so you are using the autotemp, but did set INDIVIDUAL_POWERLIMIT="NO" ?
This can give a problem, to set autotemp correctly it needs this set to YES.

I set the temp control to set in line 51 and set the individual to yes in line 145 I set all the lines below to 100. I set all the target temp to 60 (this is the old v17 measured value) nand set restore to 20 in line 237.

Question: what does orginal power limit means? The card's default 125? Or powerlimit_watts in line 74?

Thank you!

The original power limit is the one read from the variables set in 1bash. You can see in the autotemp file: echo "INDIVIDUAL_POWERLIMIT_0: ${POWER_LIMIT[0]}". That value is coming from the 1bash file, for instance INDIVIDUAL_POWERLIMIT_0=100.

Please run the autotemp script in a terminal and read the output.

Code:

/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL

gyoztes

newbie

Activity: 16

Merit: 0

Quote from: Maxximus007 on July 19, 2017, 11:14:10 AM

Okay, so you are using the autotemp, but did set INDIVIDUAL_POWERLIMIT="NO" ?
This can give a problem, to set autotemp correctly it needs this set to YES.

I set the temp control to set in line 51 and set the individual to yes in line 145 I set all the lines below to 100. I set all the target temp to 60 (this is the old v17 measured value) nand set restore to 20 in line 237.

Question: what does orginal power limit means? The card's default 125? Or powerlimit_watts in line 74?

Thank you!

OverEasy

sr. member

Activity: 301

Merit: 251

Quote from: Maxximus007 on July 19, 2017, 10:41:35 AM

Quote from: OverEasy on July 19, 2017, 09:39:07 AM

SSH users and new 1bash. You can no longer start things up by using bash 2unix as all the pastebin stuff is commented out.
You must now start up by SSH in to rig and run 1bash directly. Fullzero has placed the pastebin stuff in 1bash so make sure you edit 1bash first to remote and put your pastebin info in it.

For me personally new v18.1 does not work. Many many errors. Can't afford to have rig down to diagnosis right now so I am back to V.17 that works flawlessly for my purposes.

I would like to suggest making version 17 the "base" build as it works so well and incorporate all the features in as "modules" (separate programs), instead of adding all the code to the 1bash file.

File is getting so big it is hard to diagnosis stuff. Just one noobs opinion lol...

Yes, the 2unix has the pastebin out, and it's indeed quite handy in there to have a fitting 1bash directly. As fullzero already said, it will be modularized and optimized pretty soon, once it's on github. Currently there is just too much in one file, and makes it error prone. I use the new V0018 as a template, and removing parts I don't use.

Perhaps the first step should be separating the variables from the code with something like: source myvariables

It's still not a simple task for fullzero: There are many wishes, and for instance overclock is different per miner/coin etc..

TBH, I don't care too much to have all the possible (obscure) coins in it, if you want it, edit yourself (for now). Once it's split up in modules it's way easier to add additional coins.

I agree completely. Poor Fullzero is working overtime on this and giving it for free. I sure hope everyone is giving him some hash every once in a while. Hey Fullzero you should add your ETH or whatever you want to the code right at the top and comment it out. Most folks just open 1bash and delete yours and paste their address in. You are acknowledging everyone but yourself!

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: gyoztes on July 19, 2017, 10:53:10 AM

Quote from: Maxximus007 on July 19, 2017, 10:25:00 AM

Are you using the new V0018? Did you made a new img, or just used a new oneBash? What version did you have before? If you used V0017 or before, perhaps you did not change the autotemp file? The first version had it's own power limits set at 125W.

Can you please try the following:
SSH into your rig or open a guake terminal, and enter:

Code:

sudo nvidia-smi -pl 60

nvidia-smi will give you output, probably telling that the power limits are now set to 60 W. If that's the case, at least you know that setting powerlimits is possible, and it's perhaps the above.

Thank you for the fast reply! Yes I use the newest v18 with the new 1bash. If I set what you mentioned before, it works well. (I set it to 100 because I use 1070 cards.)

My experience: if I set it in the 1bash - and monitor it in another terminal - it works UNTIL the dag reading's end! And after this, it is changing to 125.

In the 1bash it is in the line 522 and (as I see well) there is no setting after this line ith this parameter.

I set the all of the individual card settints to 100 too but set no to induvidual_powerlimit on line 133 and all power limit started from 243 to 100 too (form nicehash but now I do not use it yet).

I try to set on/off the temperature control in line 51 but it is not changing the problem.

What is yor next idea?

Thank you!

Okay, so you are using the autotemp, but did set INDIVIDUAL_POWERLIMIT="NO" ?
This can give a problem, to set autotemp correctly it needs this set to YES.

gyoztes

newbie

Activity: 16

Merit: 0

I continue the above: if I set it with my hand, it is ok BUT just for 1-2 minutes and anything changes it back to 125!

gyoztes

newbie

Activity: 16

Merit: 0

Quote from: Maxximus007 on July 19, 2017, 10:25:00 AM

Are you using the new V0018? Did you made a new img, or just used a new oneBash? What version did you have before? If you used V0017 or before, perhaps you did not change the autotemp file? The first version had it's own power limits set at 125W.

Can you please try the following:
SSH into your rig or open a guake terminal, and enter:

Code:

sudo nvidia-smi -pl 60

nvidia-smi will give you output, probably telling that the power limits are now set to 60 W. If that's the case, at least you know that setting powerlimits is possible, and it's perhaps the above.

Thank you for the fast reply! Yes I use the newest v18 with the new 1bash. If I set what you mentioned before, it works well. (I set it to 100 because I use 1070 cards.)

My experience: if I set it in the 1bash - and monitor it in another terminal - it works UNTIL the dag reading's end! And after this, it is changing to 125.

In the 1bash it is in the line 522 and (as I see well) there is no setting after this line ith this parameter.

I set the all of the individual card settints to 100 too but set no to induvidual_powerlimit on line 133 and all power limit started from 243 to 100 too (form nicehash but now I do not use it yet).

I try to set on/off the temperature control in line 51 but it is not changing the problem.

What is yor next idea?

Thank you!

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: OverEasy on July 19, 2017, 09:39:07 AM

SSH users and new 1bash. You can no longer start things up by using bash 2unix as all the pastebin stuff is commented out.
You must now start up by SSH in to rig and run 1bash directly. Fullzero has placed the pastebin stuff in 1bash so make sure you edit 1bash first to remote and put your pastebin info in it.

For me personally new v18.1 does not work. Many many errors. Can't afford to have rig down to diagnosis right now so I am back to V.17 that works flawlessly for my purposes.

I would like to suggest making version 17 the "base" build as it works so well and incorporate all the features in as "modules" (separate programs), instead of adding all the code to the 1bash file.

File is getting so big it is hard to diagnosis stuff. Just one noobs opinion lol...

Yes, the 2unix has the pastebin out, and it's indeed quite handy in there to have a fitting 1bash directly. As fullzero already said, it will be modularized and optimized pretty soon, once it's on github. Currently there is just too much in one file, and makes it error prone. I use the new V0018 as a template, and removing parts I don't use.

Perhaps the first step should be separating the variables from the code with something like: source myvariables

It's still not a simple task for fullzero: There are many wishes, and for instance overclock is different per miner/coin etc..

TBH, I don't care too much to have all the possible (obscure) coins in it, if you want it, edit yourself (for now). Once it's split up in modules it's way easier to add additional coins.

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: gyoztes on July 19, 2017, 09:17:04 AM

Hi guys,

Is there a solution for this? I got it too (8x1070 and 125W) and can not do anything.

Quote from: DJ ACK on July 18, 2017, 02:46:57 PM

Love the v0018 release and all the functionality!

However, POWERLIMIT NIGHTMARES!

I have one major issue, I cannot lower the POWERLIMIT. I run 8 rigs of 1050Ti and 125W is just way to high. I have tried adjusting the base line and the individual POWERLIMIT settings and I am still seeing maximum power being utilized in NVIDIA-SMI and TEMP CONTROL. I thought maybe the TEMP CONTROL was trumping the setting, but I don't think that is the case (at least based on what my 46 year old brain and eye balls looking at the 1bash code understands). I thought maybe it was the correction in line 527, but that didn't change anything.

I tried "NO" for both WATCHDOG and TEMP CONTROL with POWERLIMIT set below MAX for the 1050Ti and I still see max power output.

I did notice during startup, of the three terminal screens that pop-up during startup that the second terminal session has the POWERLIMIT set correctly at 60. However, something happens after the third terminal screen initiates (miner starting) that pushes the POWER back to MAX.

I added another rig of 1050Tis tonight and I saw more unusual behavior from POWER settings again where GPU0 goes to 125W as the max power limit and the rest of the GPUs all complied with my setting of 65Watts. I have no idea what is causing this inconsistency in power limit settings.

I also noticed in the Guake terminal that the TEMP CONTROL module is displaying continuous notifications that 125W is not a valid power limit (even after changing the settings in the module to 60-65).

I normally run all my rigs at 60W, which keeps the current draw low enough to run 3 rigs of 8 GPUs on each 15 AMP circuit. Also, extremely efficient.

I am still hunting for what is causing the forced 125W power setting.

Are you using the new V0018? Did you made a new img, or just used a new oneBash? What version did you have before? If you used V0017 or before, perhaps you did not change the autotemp file? The first version had it's own power limits set at 125W.

Can you please try the following:
SSH into your rig or open a guake terminal, and enter:

Code:

sudo nvidia-smi -pl 60

nvidia-smi will give you output, probably telling that the power limits are now set to 60 W. If that's the case, at least you know that setting powerlimits is possible, and it's perhaps the above.

keno1234

newbie

Activity: 15

Merit: 0

Thank you very much for making such a wonderful OS.

Does NVOC v0018 have log file when miner restart after GPU soft crash?

OverEasy

sr. member

Activity: 301

Merit: 251

SSH users and new 1bash. You can no longer start things up by using bash 2unix as all the pastebin stuff is commented out.
You must now start up by SSH in to rig and run 1bash directly. Fullzero has placed the pastebin stuff in 1bash so make sure you edit 1bash first to remote and put your pastebin info in it.

For me personally new v18.1 does not work. Many many errors. Can't afford to have rig down to diagnosis right now so I am back to V.17 that works flawlessly for my purposes.

I would like to suggest making version 17 the "base" build as it works so well and incorporate all the features in as "modules" (separate programs), instead of adding all the code to the 1bash file.

File is getting so big it is hard to diagnosis stuff. Just one noobs opinion lol...

gyoztes

newbie

Activity: 16

Merit: 0

Hi guys,

Is there a solution for this? I got it too (8x1070 and 125W) and can not do anything.

Quote from: DJ ACK on July 18, 2017, 02:46:57 PM

Love the v0018 release and all the functionality!

However, POWERLIMIT NIGHTMARES!

I have one major issue, I cannot lower the POWERLIMIT. I run 8 rigs of 1050Ti and 125W is just way to high. I have tried adjusting the base line and the individual POWERLIMIT settings and I am still seeing maximum power being utilized in NVIDIA-SMI and TEMP CONTROL. I thought maybe the TEMP CONTROL was trumping the setting, but I don't think that is the case (at least based on what my 46 year old brain and eye balls looking at the 1bash code understands). I thought maybe it was the correction in line 527, but that didn't change anything.

I tried "NO" for both WATCHDOG and TEMP CONTROL with POWERLIMIT set below MAX for the 1050Ti and I still see max power output.

I did notice during startup, of the three terminal screens that pop-up during startup that the second terminal session has the POWERLIMIT set correctly at 60. However, something happens after the third terminal screen initiates (miner starting) that pushes the POWER back to MAX.

I added another rig of 1050Tis tonight and I saw more unusual behavior from POWER settings again where GPU0 goes to 125W as the max power limit and the rest of the GPUs all complied with my setting of 65Watts. I have no idea what is causing this inconsistency in power limit settings.

I also noticed in the Guake terminal that the TEMP CONTROL module is displaying continuous notifications that 125W is not a valid power limit (even after changing the settings in the module to 60-65).

I normally run all my rigs at 60W, which keeps the current draw low enough to run 3 rigs of 8 GPUs on each 15 AMP circuit. Also, extremely efficient.

I am still hunting for what is causing the forced 125W power setting.

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

very interesting ...

i have yet to try anything - but will do in the near future ...

i dont exactly get the complete picture as to how to run everything yet - but it will come when i get my head around exactly what everything is ...

#crysx

lost_post

newbie

Activity: 13

Merit: 0

I wrote a code that check any income messages to telegram bot from you, and answer you.
Save it as separate file and run it at start.

Quote

source ~/wallets #import wallets
source ~/settings.sh #import settings

cd /tmp
while [ 1 ]
do
rm getUpdates
wget https://api.telegram.org/bot$TELEGRAM_API/getUpdates

INCOME=$(cat ./getUpdates | grep $TELEGRAM_CHAT | tail -1 | awk -F ":" '{print $13}' | cut -d \" -f 2)
INCOME_TIME=$(cat ./getUpdates | grep $TELEGRAM_CHAT | tail -1 | awk -F ":" '{print $12}' | cut -c -10)

LAST_INCOME_TIME=$(cat /home/m1/last_inc_time)

if [ $INCOME_TIME != $LAST_INCOME_TIME ]
then
if [[ $INCOME == "State" || $INCOME == "state" || $INCOME == "STATE" ]]
then
echo state of rig
~/mail.sh 9
else
echo invalid msg!
fi
echo $INCOME_TIME > /home/m1/last_inc_time #first time you must create this file yourself. put any numbers inside.
else
echo no new messeges!
fi
sleep 5
done

To change or add new msg: $INCOME is text of message. ~/mail.sh 9 - is command to do.

Quote

if [[ $INCOME == "State" || $INCOME == "state" || $INCOME == "STATE" ]]
then
echo state of rig
~/mail.sh 9
else
echo invalid msg!
fi

Please add to nvOC .

Avarets

newbie

Activity: 12

Merit: 0

My configuration:
v0018
Biostar TB250-BTC PRO + 12 Zotac P106-100 cards (without output).
When I run it with LOCAL (GT 730 for monitor + 7 P106-100 cards) I see it works.
But when I remove GT 730 adapter and monitor and attach all 12 P106-100 cards and use REMOTE and connect by SSH it doesn't seem to be working.
I tried to run it manually but the OS was rebooted with Xorg error.
Any ideas how to fix it?

P.S. I tried new 1bash - still the same issue.

Code:

m1@m1-desktop:~$ pkill -e miner
m1@m1-desktop:~$ export DISPLAY=:0
m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~$ bash /home/m1/1bash


workername: nv045

Xorg PROBLEM DETECTED

Restoring Xorg

Rebooting in 5

_Parallax_

newbie

Activity: 12

Merit: 0

Quote from: BaliMiner on July 18, 2017, 02:49:07 AM

Hi All,
i made a telegram script to report hash rates and other stats using telegram bot, the stats consists of power draw, temperature and fan speed on my little mining rig.

Hope this script helps...
any suggestion is appreciated

I use telegram bot for sending allerts from zabbix monitoring system - @crierbot
For using it you need to add @crierbot in to your telegramm
(if you use android smart phone go to google play or if use iPhone go to app store, download and install telegram and send command /start )
in replay you will get TOKEN for using in your scripts

My script /home/m1/telegram.sh (need to have chmod +x 755)

#!/bin/bash

PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

/usr/bin/curl -s http://localhost:3333 | sed '/ETH/!d; /Total/!d; /Speed/!d;' | awk {'print $6'} | tail -n 1 >> /tmp/totalhash.log

TOKEN=YOUR-TOKEN
TOTALHASH="$(/bin/cat /tmp/totalhash.log)"
TARGET="$(/bin/cat /home/m1/target.log)"

FAN=$(/usr/bin/nvidia-smi --query-gpu=fan.speed --format=csv)
WATT=$(/usr/bin/nvidia-smi --query-gpu=power.draw --format=csv)
TEMP=$(/usr/bin/nvidia-smi --query-gpu=temperature.gpu --format=csv)
GPUHASH=$(curl -s http://localhost:3333 | sed '/GPU/!d; /Mh/!d' | tr -d font'>
sleep 2

if [[ $TARGET > $TOTALHASH ]]; then
   wget -O /dev/null "http://crierbot.appspot.com/${TOKEN}/send?message=Warning!!!
   host $(cat /etc/hostname) too slow hash
   ip: $(ifconfig | grep inet | grep -v inet6 | grep -v 127.0.0.1 | cut -d: -f2 | awk '{printf $1}')
   $FAN
   $WATT
   $TEMP
   $GPUHASH
Total Hash: $TOTALHASH"
   else
   echo > /dev/null
fi

tee /tmp/totalhash.log < /dev/null
#

Also in directory /home/m1 you need to create file target.log and put in average value - hash your rig.
Then you need to add the record in /etc/crontab
0-59 * * * * m1 /home/m1/telegram.sh

This script fullfils once in a minute and checks the descriase of total hash.
If it descriases it sends message where hostname, IP adress, fan speed, watt, temp and hash of every GPU is shown.

lost_post

newbie

Activity: 13

Merit: 0

I saw post from BaliMiner. Thanks for your post! I decided to split in with my email notification script.
But I decided ti use original telegram-notify tool.

fullzero, please update this too.

Here is my result:

To install telegram-notification may be added to first boot section (from http://bernaerts.dyndns.org/linux/75-debian/351-debian-send-telegram-notification) thanks

Quote

wget https://raw.githubusercontent.com/NicolasBernaerts/debian-scripts/master/telegram/telegram-notify-install.sh
./telegram-notify-install.sh

settings section or file

Quote

EMAIL="YES"

TELEGRAM="YES"
TELEGRAM_API="your-api-key"
TELEGRAM_CHAT="your-chat-id"

start onebash section:

Quote

if [ $TELEGRAM == "YES" ]
then
echo "[general]" > ~/telegram-notify.conf
echo "api-key=$TELEGRAM_API" >> ~/telegram-notify.conf
echo "user-id=$TELEGRAM_CHAT" >> ~/telegram-notify.conf
sudo mv /home/m1/telegram-notify.conf /etc/telegram-notify.conf
fi

mail.sh file :

Quote

#!/bin/bash
MSM_NUM=$1
source ~/wallets
source ~/settings.sh

MSG=""
IMG=""
DOC=""

case $MSM_NUM in
0)
MSG="System was started"
IMG="--success"
;;
1)
MSG="GPU Miner was started"
IMG="--success"
;;
2)
MSG="CPU Miner was started"
IMG="--success"
;;
3)
MSG="GPU miner was crushed and restarting now"
IMG="--error"
DOC="--document "/home/m1/4_restartlog""
;;
4)
MSG="New setiings arrived. Restart now"
IMG="--question"
DOC="--document "/home/m1/wallets.diff""
;;
5)
MSG="Lost GPU so restarting system"
IMG="--error"
DOC="--document "/home/m1/4_restartlog""
;;
6)
MSG="Utilization is too low: so restarting system"
IMG="--error"
DOC="--document "/home/m1/4_restartlog""
;;
7)
MSG="NICEHASH was started just now!"
IMG="--success"
;;
Cool

IP=$(cat /home/m1/last_ip)
MSG="webUI was started just now http://$IP/"
IMG="--success"
;;
*)
TEMP=$(/usr/bin/nvidia-smi --query-gpu=temperature.gpu --format=csv)
PD=$(/usr/bin/nvidia-smi --query-gpu=power.draw --format=csv)
FAN=$(/usr/bin/nvidia-smi --query-gpu=fan.speed --format=csv)
LF=$'\n'
PROFIT=$(cat /home/m1/current-profit)
MSG=$TEMP$LF$PD$LF$FAN
#MSG="$WORKER_NAME Error with subject!"
;;
esac
# telegram-notify --success --text "Action *sucessful* with markdown *bold* example"
# telegram-notify --error --title "Error" --text "Error message with a title"
# telegram-notify --question --title "File content display" --text "/tmp/log.txt"
# telegram-notify --icon 1F355 --text "Message with custom icon 1F355 and embedded image" --photo "/tmp/icon.png"
# telegram-notify --text "Result is available in the embedded document" --document "/tmp/result.log"

if [ $EMAIL == "YES" ]
then
sendemail -f $RIG_EMAIL -t $ADMIN_EMAIL -u $WORKER_NAME -m "$MSG" -s $RIG_SMTP -o tls=yes -xu $RIG_EMAIL -xp $RIG_EMAIL_PASS & > /dev/null 2>&1
fi

if [ $TELEGRAM == "YES" ]
then
MSG=""$WORKER_NAME" - "$MSG
telegram-notify ${IMG} --text "${MSG}" ${DOC} --html > /dev/null 2>&1
fi

fullzero, also here is my btc address 1GFTEtLLvvwoa4ogDntD5oaXBgJLYokzTC

Maybe it is time to move with your code to github ? A lot of people what to make some fixes, addons and so on.

Topic: [ mining os ] nvoc - page 290. (Read 418549 times)