[OS] nvOC easy-to-use Linux Nvidia Mining

[fullzero]

I am getting errors on V.18
I am SSH ONLY. No monitor. No Guake. No Gnome.

First error is after 1bash tries to stop TeamViewer -


Mon Jul 17 14:26:28 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument

Second error is when Maxximus007_AUTO_TEMPERATURE_CONTROL launches -

LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

process in Guake Tab

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

I have to assume Temp Control has failed and is not working.
Can you consider launching temp control and watchdog NOT in Guake if "REMOTE" is chosen but in screens instead? I will try to change bash myself to make this happen.

Thanks

I will make a conditional execution for the teamviewer block and add the appropriate export cmd in the auto temp block to resolve those errors.

To get auto temp working ( almost positive this is the problem ) add this line:

Code:

EXPORT DISPLAY=:0

I can make each open in a screen when remote is selected.

If you replace the:

Code:

if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]

block with:

Code:

if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]
then

cd /home/m1

rm /home/m1/p0
rm /home/m1/p1
rm /home/m1/p2
rm /home/m1/p3
rm /home/m1/p4
rm /home/m1/p5
rm /home/m1/p6
rm /home/m1/p7
rm /home/m1/p8
rm /home/m1/p9
rm /home/m1/p10
rm /home/m1/p11
rm /home/m1/p12
rm /home/m1/p13
rm /home/m1/t0
rm /home/m1/t1
rm /home/m1/t2
rm /home/m1/t3
rm /home/m1/t4
rm /home/m1/t5
rm /home/m1/t6
rm /home/m1/t7
rm /home/m1/t8
rm /home/m1/t9
rm /home/m1/t10
rm /home/m1/t11
rm /home/m1/t12
rm /home/m1/t13
rm /home/m1/fa
rm /home/m1/pa
rm /home/m1/td
rm /home/m1/rpl

sleep 2

echo $INDIVIDUAL_POWERLIMIT_0 > '/home/m1/p0'
echo $INDIVIDUAL_POWERLIMIT_1 > '/home/m1/p1'
echo $INDIVIDUAL_POWERLIMIT_2 > '/home/m1/p2'
echo $INDIVIDUAL_POWERLIMIT_3 > '/home/m1/p3'
echo $INDIVIDUAL_POWERLIMIT_4 > '/home/m1/p4'
echo $INDIVIDUAL_POWERLIMIT_5 > '/home/m1/p5'
echo $INDIVIDUAL_POWERLIMIT_6 > '/home/m1/p6'
echo $INDIVIDUAL_POWERLIMIT_7 > '/home/m1/p7'
echo $INDIVIDUAL_POWERLIMIT_8 > '/home/m1/p8'
echo $INDIVIDUAL_POWERLIMIT_9 > '/home/m1/p9'
echo $INDIVIDUAL_POWERLIMIT_10 > '/home/m1/p10'
echo $INDIVIDUAL_POWERLIMIT_11 > '/home/m1/p11'
echo $INDIVIDUAL_POWERLIMIT_12 > '/home/m1/p12'
echo $INDIVIDUAL_POWERLIMIT_13 > '/home/m1/p13'

echo $TARGET_TEMP_0 > '/home/m1/t0'
echo $TARGET_TEMP_1 > '/home/m1/t1'
echo $TARGET_TEMP_2 > '/home/m1/t2'
echo $TARGET_TEMP_3 > '/home/m1/t3'
echo $TARGET_TEMP_4 > '/home/m1/t4'
echo $TARGET_TEMP_5 > '/home/m1/t5'
echo $TARGET_TEMP_6 > '/home/m1/t6'
echo $TARGET_TEMP_7 > '/home/m1/t7'
echo $TARGET_TEMP_8 > '/home/m1/t8'
echo $TARGET_TEMP_9 > '/home/m1/t9'
echo $TARGET_TEMP_10 > '/home/m1/t10'
echo $TARGET_TEMP_11 > '/home/m1/t11'
echo $TARGET_TEMP_12 > '/home/m1/t12'
echo $TARGET_TEMP_13 > '/home/m1/t13'

echo $__FAN_ADJUST > '/home/m1/fa'
echo $POWER_ADJUST > '/home/m1/pa'
echo $ALLOWED_TEMP_DIFF > '/home/m1/td'
echo $RESTORE_POWER_LIMIT > '/home/m1/rpl'
echo ""
echo "LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL "

HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
running=$(ps -ef | awk '$NF~"Maxximus007_AUTO_TEMPERATURE_CONTROL" {print $2}')
if [ "$running" == "" ]
then
EXPORT DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
screen -dmS autotemp $HCD
  echo ""
  echo "process in screen autotemp; attach with: screen -r autotemp"
  echo ""
fi

running=""
fi
fi

it should implement this change (but I haven't tested it)

Ok I added export DISPLAY=:0 to fist line of bash and now the script goes further.
But still I am getting the error I have posted below and no additional screens are starting.
Also I just discovered that the switch IAmNotAJeep_and_Maxximus007_WATCHDOG="YES" doesn't do anything! There is no code to go with the switch.
I will try to edit bash and stick it in there. I must be the only person using SSH lol. Why am I the only one finding all these issues?

Also we need discuss the new way to launch the miner using SSH and 2unix and 1bash. The way it's set up now is you use Putty or whatever and SSH to server. Then WITHOUT using a screen you execute " bash '/home/m1/2unix' ". Then what happens is the terminal displays some stuff and just stops when the bash launches the miner. So now you are left with a terminal screen that is just stopped and a miner screen you can't get to. The only way to get to it is terminate the terminal, re-log in and screen -r OR CTRL-c the current terminal screen and then screen -r. I am a Linux noob but seems to me there should be a better way. version 17 was simpler IMO. Open terminal, create a screen and execute bash. I think your doing it this way to automate a screen and miner in the case of a power up or reboot.

So in summary -

A: Watchdog not launching as code is missing
B: Errors on launch trying to execute something it can't find (BTW miner still launches and works in spite of error)
C: No idea if temp control working because I still can't get it to execute it's own screen
D: Funky startup procedure for SSH users

I love your work and really appreciate it. These are not criticisms, just notes to try to help...

dos2unix: converting file /home/m1/1bash to Unix format ...


workername: nv136


rig IP: 10.0.0.136


03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
23:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)


Tue Jul 18 09:47:50 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.47                 Driver Version: 384.47                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:03:00.0  On |                  N/A |
| 79%   58C    P8    12W / 125W |     94MiB /  3012MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 00000000:04:00.0 Off |                  N/A |
| 54%   61C    P8    10W / 125W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:22:00.0 Off |                  N/A |
| 56%   57C    P8    13W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:23:00.0 Off |                  N/A |
| 57%   59C    P8    14W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1293    G   /usr/lib/xorg/Xorg                              69MiB |
|    0      1925    G   compiz                                          21MiB |
|    1      1293    G   /usr/lib/xorg/Xorg                               7MiB |
+-----------------------------------------------------------------------------+


ENVIRONMENTAL VARIBLES SET


Tue Jul 18 09:47:50 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument


LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value
  1000.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value
  1000.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:0]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:1]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:2]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:3]) assigned value 2.

These warnings I have too, but they don't stop the script. What probably doesn't work over ssh is the guake starts. At least you can't see them over ssh. Will try later, have just set up a new rig (but currently with monitor) with V18. I personally change these all to different screens, way easier over ssh.

But the scripts are there thats for sure, pls check again in your home directory. And I think they run as well, in your home directory you'll find the following files: 3_autotemplog and 4_restartlog.
type tail 3_autotemplog to see the last messages.

If you're using ssh, and want to move around, install mc (sudo apt install mc), it is like Norton Commander a looong time ago, but helpful here.

Hey thanks for answering.. I use WinSCP for quick easy getting around.
The code to launch Watchdog was not in the Version 18 bash at all. I added this but am not sure of the correct syntax to make your app actually launch

if [ $IAmNotAJeep_and_Maxximus007_WATCHDOG == "YES" && $LOCALorREMOTE == "REMOTE" ]
then
HCD='/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG'
screen -dmS watchdog $HCD
  echo ""
  echo "process in screen watchdog; attach with: screen -r watchdog"
  echo ""
fi

WATCHDOG ON SSH RESOLVED -

CODE:

if [ $IAmNotAJeep_and_Maxximus007_WATCHDOG == "YES" ]
then
HCD='/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG'
screen -dmS watchdog bash $HCD
  echo ""
  echo "process in screen watchdog; attach with: screen -r watchdog"
  echo ""
fi

This works and watchdog is now running.
All I need to do is add the local remote part of the code in to finish it.

Now to tackle the temp part....

Like Maxximus007 said the code is there and it is launching the processes.

You seem to have missed that I already implemented your request in regards to the autotemp in the code block from my previous response:

Code:

if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]
then

cd /home/m1

rm /home/m1/p0
rm /home/m1/p1
rm /home/m1/p2
rm /home/m1/p3
rm /home/m1/p4
rm /home/m1/p5
rm /home/m1/p6
rm /home/m1/p7
rm /home/m1/p8
rm /home/m1/p9
rm /home/m1/p10
rm /home/m1/p11
rm /home/m1/p12
rm /home/m1/p13
rm /home/m1/t0
rm /home/m1/t1
rm /home/m1/t2
rm /home/m1/t3
rm /home/m1/t4
rm /home/m1/t5
rm /home/m1/t6
rm /home/m1/t7
rm /home/m1/t8
rm /home/m1/t9
rm /home/m1/t10
rm /home/m1/t11
rm /home/m1/t12
rm /home/m1/t13
rm /home/m1/fa
rm /home/m1/pa
rm /home/m1/td
rm /home/m1/rpl

sleep 2

echo $INDIVIDUAL_POWERLIMIT_0 > '/home/m1/p0'
echo $INDIVIDUAL_POWERLIMIT_1 > '/home/m1/p1'
echo $INDIVIDUAL_POWERLIMIT_2 > '/home/m1/p2'
echo $INDIVIDUAL_POWERLIMIT_3 > '/home/m1/p3'
echo $INDIVIDUAL_POWERLIMIT_4 > '/home/m1/p4'
echo $INDIVIDUAL_POWERLIMIT_5 > '/home/m1/p5'
echo $INDIVIDUAL_POWERLIMIT_6 > '/home/m1/p6'
echo $INDIVIDUAL_POWERLIMIT_7 > '/home/m1/p7'
echo $INDIVIDUAL_POWERLIMIT_8 > '/home/m1/p8'
echo $INDIVIDUAL_POWERLIMIT_9 > '/home/m1/p9'
echo $INDIVIDUAL_POWERLIMIT_10 > '/home/m1/p10'
echo $INDIVIDUAL_POWERLIMIT_11 > '/home/m1/p11'
echo $INDIVIDUAL_POWERLIMIT_12 > '/home/m1/p12'
echo $INDIVIDUAL_POWERLIMIT_13 > '/home/m1/p13'

echo $TARGET_TEMP_0 > '/home/m1/t0'
echo $TARGET_TEMP_1 > '/home/m1/t1'
echo $TARGET_TEMP_2 > '/home/m1/t2'
echo $TARGET_TEMP_3 > '/home/m1/t3'
echo $TARGET_TEMP_4 > '/home/m1/t4'
echo $TARGET_TEMP_5 > '/home/m1/t5'
echo $TARGET_TEMP_6 > '/home/m1/t6'
echo $TARGET_TEMP_7 > '/home/m1/t7'
echo $TARGET_TEMP_8 > '/home/m1/t8'
echo $TARGET_TEMP_9 > '/home/m1/t9'
echo $TARGET_TEMP_10 > '/home/m1/t10'
echo $TARGET_TEMP_11 > '/home/m1/t11'
echo $TARGET_TEMP_12 > '/home/m1/t12'
echo $TARGET_TEMP_13 > '/home/m1/t13'

echo $__FAN_ADJUST > '/home/m1/fa'
echo $POWER_ADJUST > '/home/m1/pa'
echo $ALLOWED_TEMP_DIFF > '/home/m1/td'
echo $RESTORE_POWER_LIMIT > '/home/m1/rpl'
echo ""
echo "LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL "

HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
running=$(ps -ef | awk '$NF~"Maxximus007_AUTO_TEMPERATURE_CONTROL" {print $2}')
if [ "$running" == "" ]
then
EXPORT DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
screen -dmS autotemp $HCD
  echo ""
  echo "process in screen autotemp; attach with: screen -r autotemp"
  echo ""
fi

running=""
fi
fi

in regards to using this code:

Code:

if [ $IAmNotAJeep_and_Maxximus007_WATCHDOG == "YES" ]
then
HCD='/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG'
screen -dmS watchdog bash $HCD 
  echo ""
  echo "process in screen watchdog; attach with: screen -r watchdog"
  echo ""
fi

launching like this will result in lots of problems, every restart of 1bash will start a new watchdog instance.

this should work:

Code:

if [ $IAmNotAJeep_and_Maxximus007_WATCHDOG == "YES" ]
then

HCD='/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG'
running=$(ps -ef | awk '$NF~"IAmNotAJeep_and_Maxximus007_WATCHDOG" {print $2}')

if [ "$running" == "" ]
then
EXPORT DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal Tab (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
screen -dmS watchdog $HCD
  echo ""
  echo "process in screen watchdog; attach with: screen -r watchdog"
  echo ""
fi

running=""
fi
fi

Also in v0018 1bash kills any existing mining process everytime it launches.  When connecting over SSH you only need to use:

Code:

screen -r miner

to reconnect to the already running process

if you swap out the autotemp and watchdog code blocks here then you can use

Code:

screen -r autotemp

to reconnect to the already running autotemp process

Code:

screen -r watchdog

to reconnect to the already running watchdog

[1714219141]

1714219141

[1714219141]

1714219141

[1714219141]

1714219141

[fullzero]

Can't wait to give v0018 a try - so many cool new features!

@fullzero
In the next version could you add this fix for Intel Hyperthreading being broken on Skylake and Kaby Lake processors - resulting in crashes?  For now people with these processors (Pentium up to Xeon) should disable Hyperthreading until BIOS fix.  Several of my boards don't have a BIOS update, and for Skylake processors, the microcode fix is better than the BIOS update (FYI, this is not Debian specific, but to any OS including Ubuntu, which is based on Deb)

https://lists.debian.org/debian-devel/2017/06/msg00308.html

Instructions are here:
https://wiki.debian.org/Microcode

I will look into this / add it to the list.

[RonaldMcDongle]

Was hoping to be able to mine XVG this release. Oh well, still really appreciate the work as always fullzero!

I may try and hack in XVG on myriad-groestl to the onebash, should it be easy enough?

I will add this to the list.

Start with another myriad-groestl coin selection code block and modify it.

If you get it working please post the code to save me some time.

What pool are you planning on using with this COIN?

I plan on using this pool - http://xvg-mg.idcray.com/

Thanks again for your work! Great resource to the community

[lost_post]

Also, using separate files for settings and for the code allows you to share the settings in any module with a string "source ~/wallets" or "source ~/settings.sh"

[OverEasy]

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?

[DJ ACK]

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.

[lost_post]

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

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

settings section or file

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

start onebash section:

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 :

#!/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"
          ;;
     
     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="<b>"$WORKER_NAME"</b> - "$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.

[_Parallax_]

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'></="#'brcl | awk 'NR==5')

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.

[fullzero]

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.

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.

[fullzero]

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

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

settings section or file

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

start onebash section:

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 :

#!/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"
          ;;
     
     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="<b>"$WORKER_NAME"</b> - "$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.

I used a modified version of your paste updating method in the new 1bash + upPASTE.

I still need to implement a bunch more.  I will make a github repo when most of the requests have been implemented; then focus on optimization. 

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'></="#'brcl | awk 'NR==5')

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.

BaliMiner please provide a BTC address for the next version.

[fullzero]

OP is updated with:

upPASTE_1bash + upPASTE file, updated AUTOTEMP, updated WATCHDOG, updated 2unix

WATCHDOG is relaxed and will only reboot if needed.

It should now work well with SALFTER_NICEHASH_PROFIT_SWITCHING

2unix now kills the current 1bash when it starts

when LOCALorREMOTE="REMOTE" : to attach the mining process to a screen use the cmd:

Code:

screen -r miner

AUTOTEMP opens in a screen named temp when LOCALorREMOTE="REMOTE" :

attach the screen with the cmd:

Code:

screen -r temp

WATCHDOG opens in a screen named wdog when LOCALorREMOTE="REMOTE" :

attach the screen with the cmd:

Code:

screen -r wdog

INDIVIDUAL_POWERLIMIT="YES"  fail is fixed and should now work as intended

AUTOTEMP now has the variable MINIMAL_FAN_SPEED in 1bash to allow setting the bottom value for fanspeed when using Maxximus007_AUTO_TEMPERATURE_CONTROL

upPASTE implements timeout based _Parallax_MODE updating.  If you set:

Code:

_Parallax_MODE="YES" 

       

Code:

pasteBASH="np9FSHew"

  # your paste here

Code:

upPASTE_TIMEOUT_IN_MINUTES=30

  # minutes between checks

upPASTE will automatically check / update / relaunch the mining process with the 1bash from the paste; pasteBASH is set to.

Make sure you Thank lost_post for this if you use it.


I haven't added any COIN selections with this 1bash; I will release another 1bash update with them soon.

[Avarets]

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

[lost_post]

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.

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.

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

Please add to nvOC .

[chrysophylax]

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

[gyoztes]

Hi guys,

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

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.

[OverEasy]

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...

[keno1234]

Thank you very much for making such a wonderful OS.

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

[Maxximus007]

Hi guys,

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

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.

[Maxximus007]

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.

[gyoztes]

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!