[ mining os ] nvoc

[papampi]

My latest telegram
Fixed miner uptime
With some WTM auto switch and profit check info

LINK

Thx for sharing your ideas  

Just trying to help  👍👍👍👍

[damNmad]

Guys; i just found this new (??) ethash miner, not sure it dual mines but would like someone to test it and see whether it earns place in nvOC??

https://github.com/ethash/eminer-release/releases/


It comes with some gadgets to see the hashrate and stuff, please have a look and put your opinion out. Would suggest to run it on a test RIG (I don;t have one Sorry )


You can also join the discussion here on discord https://discord.gg/trw4c3c

[RobertN]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

[Stubo]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

That is a clear indication that the miner is not mining which can be for a lot of reasons. The watchdog script is not seeing enough GPU utilization so it tries to restart the miner a few times and eventually reboot the box. The watchdog can be particularly annoying this way. Please start by posting what you are trying to mine for and what you have changed in 1bash.

[damNmad]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

It only means, its not mining at all, so because the utilization is '0' 3main restarting the RIG, its just a loop until you fix the problem.

First, what coin you are mining, you sure you have the coin details correct? (check any extra spaces and dot or slash)

Second try to run that coin's individual line based on 3main constraints (ignore this if you don't know what I've said)

I've been trying to answer these sort of questions on our discord channel, feel free to hop in https://discord.gg/8YDFEvY

[damNmad]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

That is a clear indication that the miner is not mining which can be for a lot of reasons. The watchdog script is not seeing enough GPU utilization so it tries to restart the miner a few times and eventually reboot the box. The watchdog can be particularly annoying this way. Please start by posting what you are trying to mine for and what you have changed in 1bash.

You beat me, Thank you so much stubo

[RobertN]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

That is a clear indication that the miner is not mining which can be for a lot of reasons. The watchdog script is not seeing enough GPU utilization so it tries to restart the miner a few times and eventually reboot the box. The watchdog can be particularly annoying this way. Please start by posting what you are trying to mine for and what you have changed in 1bash.

Thanks, im trying to mine Zen. Using suprnova as pool and have created a new worker with password "x".

This is what I´ve changed in 1bash:

COIN:"ZEN"

ZEN_WORKER:"My-new-created-worker"
ZEN_ADRESS:"Wallet-key"
ZEN_POOL:"zen.suprnova.cc"
ZEN_PORT:"3618"

Have not done anything else. What am I missing?

It only means, its not mining at all, so because the utilization is '0' 3main restarting the RIG, its just a loop until you fix the problem.

First, what coin you are mining, you sure you have the coin details correct? (check any extra spaces and dot or slash)

Second try to run that coin's individual line based on 3main constraints (ignore this if you don't know what I've said)

I've been trying to answer these sort of questions on our discord channel, feel free to hop in https://discord.gg/8YDFEvY

Thank you! I'm totally new into this, so I´ll ignore the second option for now But I'll defenetly get back to that if I can't get it to work. I´m learning new stuff everyday thanks to you guys here!

[papampi]

Just downloaded and installed nvOC on my rig for the first time with only 1 card in the pci-e x16 slot to try it out.
I have filled out the Bash1 file with the pool adress etc. (Followed VoskCoins tutorial).

Now i have 2 problems.. (Yes i have searched for answers in this thread, but have not found any solution)

1. When typing in "screen -r miner" in quake terminal i get this message: "There is no screen to be resumed matching miner."

2. The whole rig restarts after about 5 min, and sometimes it just gets in to the busybox instead.

Any ideas? (Sorry if these questions has been answered before)

That is a clear indication that the miner is not mining which can be for a lot of reasons. The watchdog script is not seeing enough GPU utilization so it tries to restart the miner a few times and eventually reboot the box. The watchdog can be particularly annoying this way. Please start by posting what you are trying to mine for and what you have changed in 1bash.

Thanks, im trying to mine Zen. Using suprnova as pool and have created a new worker with password "x".

This is what I´ve changed in 1bash:

COIN:"ZEN"

ZEN_WORKER:"My-new-created-worker"
ZEN_ADRESS:"Wallet-key"
ZEN_POOL:"zen.suprnova.cc"
ZEN_PORT:"3618"

Have not done anything else. What am I missing?

It only means, its not mining at all, so because the utilization is '0' 3main restarting the RIG, its just a loop until you fix the problem.

First, what coin you are mining, you sure you have the coin details correct? (check any extra spaces and dot or slash)

Second try to run that coin's individual line based on 3main constraints (ignore this if you don't know what I've said)

I've been trying to answer these sort of questions on our discord channel, feel free to hop in https://discord.gg/8YDFEvY

Thank you! I'm totally new into this, so I´ll ignore the second option for now But I'll defenetly get back to that if I can't get it to work. I´m learning new stuff everyday thanks to you guys here!

With suprnova you use username not wallet
Make sure you make worker in suprnova setting too

[Stubo]

This is what I´ve changed in 1bash:

COIN:"ZEN"

ZEN_WORKER:"My-new-created-worker"
ZEN_ADRESS:"Wallet-key"
ZEN_POOL:"zen.suprnova.cc"
ZEN_PORT:"3618"

Have not done anything else. What am I missing?

Your ZEN_ADDRESS (note the extra D) for suprnova should correspond to your login name, not an actual wallet address. The pool and the port are correct. The next thing to consider is that 3main will use "x" for you miner password. I am not sure if suprnova is a pool that allows anything for password or not but I just wanted to point it out.

You can also look at the logging to figure out what is happening using this command:

Code:

tail -f screenlog.0

This will show the output of the miner (and other things if REMOTE) as it tries to start and connect.


Hope this helps.

[leenoox]

Guys; i just found this new (??) ethash miner, not sure it dual mines but would like someone to test it and see whether it earns place in nvOC??

https://github.com/ethash/eminer-release/releases/


It comes with some gadgets to see the hashrate and stuff, please have a look and put your opinion out. Would suggest to run it on a test RIG (I don;t have one Sorry )


You can also join the discussion here on discord https://discord.gg/trw4c3c

It seems this miner is using OpenCL, not CUDA. Should be ok for AMD cards but not so much for Nvidia.

[RobertN]

Your ZEN_ADDRESS (note the extra D) for suprnova should correspond to your login name, not an actual wallet address. The pool and the port are correct. The next thing to consider is that 3main will use "x" for you miner password. I am not sure if suprnova is a pool that allows anything for password or not but I just wanted to point it out.

You can also look at the logging to figure out what is happening using this command:

Code:

tail -f screenlog.0

This will show the output of the miner (and other things if REMOTE) as it tries to start and connect.


Hope this helps.

Thank you! That has to be the problem, i'll replace that wallet key as soon as I solve my new problem.. it won't boot anymore, now I'm ending up at BusyBox at every startup.. Need to reinstall, hopa this will work Thanks for your help guys!

[leenoox]

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

I used to use same cmd, fixed it with this one for 1.4:

Code:

nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1

Here is even more optimized code, less cycles, no need to use pipe:

Code:

nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits

every one has GPU0 plugged in so we can query only one GPU to get the total number of GPU's instead of querying all GPU's to return the same number then pipe it trough tail

[papampi]

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

I used to use same cmd, fixed it with this one for 1.4:

Code:

nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1

Here is even more optimized code, less cycles, no need to use pipe:

Code:

nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits

every one has GPU0 plugged in so we can query only one GPU to get the total number of GPU's instead of querying all GPU's to return the same number then pipe it trough tail

Totally correct and thanks for the help 👍👍👍

[papampi]

Bios question!

Is it better to change  PEG0, PEG1,...  Max link speed to GEN1, GEN2 GEN3 in nvOC and Linux or those are only for windows ?

[kk003]

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

I used to use same cmd, fixed it with this one for 1.4:

Code:

nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1

Here is even more optimized code, less cycles, no need to use pipe:

Code:

nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits

every one has GPU0 plugged in so we can query only one GPU to get the total number of GPU's instead of querying all GPU's to return the same number then pipe it trough tail

Totally correct and thanks for the help 👍👍👍

I've never understood why in this query every GPU shows the total number of GPUs instead of just the number of GPUs.!!!

[damNmad]

Guys; i just found this new (??) ethash miner, not sure it dual mines but would like someone to test it and see whether it earns place in nvOC??

https://github.com/ethash/eminer-release/releases/


It comes with some gadgets to see the hashrate and stuff, please have a look and put your opinion out. Would suggest to run it on a test RIG (I don;t have one Sorry )


You can also join the discussion here on discord https://discord.gg/trw4c3c

It seems this miner is using OpenCL, not CUDA. Should be ok for AMD cards but not so much for Nvidia.

How on earth i missed that point 

I only saw NVIDIA from this line; "Fully support AMD and NVIDIA OpenCL devices".

Thanks @leenoox

[Stubo]

Watchdog Improvement?

I have been reading over the watchdog script and seen what I think is an opportunity for improvement. The current logic loops every 10 seconds and looks for GPU utilization below a threshold (90%), if it finds this, it begins incrementing one counter (JEEP) and decrementing another (COUNTER,  initially set to 6*#GPU) for each occurrence [per GPU]. My issue is that the current logic has to wait 6*#GPU*10 seconds, or a minute per GPU before it will attempt a miner restart.

My thinking is why not just check for the existence of a miner process - if none is found, we can just skip the rest if the countdown and get right to attempting to restart the miner. This can save many minutes of lost mining time. The downside is that it is so much faster than the existing that if you do have a configuration issue, it will be launching miners and rebooting at a much faster rate. So, maybe this is more of an expert mod.

Anyway, I have been running a modified version of IAmNotAJeep_and_Maxximus007_WATCHDOG that has this additional logic and it work great for ME. In the existing 19-1.4 version of the script, starting at line 98, I added this:

Code:

   # Begin Stubo Mod
   # Look for no miner screen and get right to miner restart
   if [[ `screen -ls |grep miner |wc -l` -eq 0 ]]
   then
      COUNT=0
	  echo "Found no miner, jumping to 3main restart" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
   fi	  
   # End Stubo Mod

By setting COUNT=0 for the "no miner found" condition, I am effectively removing the delay in decrementing COUNTER all of the way down before the script takes action.

Thoughts?

[papampi]

Watchdog Improvement?

I have been reading over the watchdog script and seen what I think is an opportunity for improvement. The current logic loops every 10 seconds and looks for GPU utilization below a threshold (90%), if it finds this, it begins incrementing one counter (JEEP) and decrementing another (COUNTER,  initially set to 6*#GPU) for each occurrence [per GPU]. My issue is that the current logic has to wait 6*#GPU*10 seconds, or a minute per GPU before it will attempt a miner restart.

My thinking is why not just check for the existence of a miner process - if none is found, we can just skip the rest if the countdown and get right to attempting to restart the miner. This can save many minutes of lost mining time. The downside is that it is so much faster than the existing that if you do have a configuration issue, it will be launching miners and rebooting at a much faster rate. So, maybe this is more of an expert mod.

Anyway, I have been running a modified version of IAmNotAJeep_and_Maxximus007_WATCHDOG that has this additional logic and it work great for ME. In the existing 19-1.4 version of the script, starting at line 98, I added this:

Code:

   # Begin Stubo Mod
   # Look for no miner screen and get right to miner restart
   if [[ `screen -ls |grep miner |wc -l` -eq 0 ]]
   then
      COUNT=0
	  echo "Found no miner, jumping to 3main restart" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
   fi	  
   # End Stubo Mod

By setting COUNT=0 for the "no miner found" condition, I am effectively removing the delay in decrementing COUNTER all of the way down before the script takes action.

Thoughts?

Amazing idea,
What I was testing is to just restart miner instead of restart 3main which will take 2-3 minutes, by using a separate miner start file which I use for WTM switcher
You can check it in ~/z_papampi_versions/wtm-miner
It has the 3main miner startup lines ( without salfter, zpool, mph) and I use that instead of restarting 3main

instead of :

Code:

       echo "WARNING: $(date) - Utilization is too low: restart 3main" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
    # If miner runs in screen 'miner' kill the screen to be sure it's gone
    pkill -e miner
    bash '/home/m1/telegram'
    # Best to restart oneBash - settings might be adjusted already
    target=$(ps -ef | awk '$NF~"3main" {print $2}')
    kill $target #| tee -a ${LOG_FILE}
    echo "" #| tee -a ${LOG_FILE}
    RESTART=$(($RESTART + 1))
    REBOOTRESET=0
    COUNT=$GPU_COUNT

I use :

Code:

       echo "WARNING: $(date) - Utilization is too low: restart 3main" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
    # If miner runs in screen 'miner' kill the screen to be sure it's gone
    pkill -e miner
    sleep 1
    bash /home/m1/wtm-miner
    bash '/home/m1/telegram'
    RESTART=$(($RESTART + 1))
    REBOOTRESET=0
    COUNT=$GPU_COUNT

Can you please tell me where you add your edit?
I made so many edits that line 98 doesnt look like the correct place


Update: I think that wtm-miner included in 1.4 is missing a done or exit at the end.

[Stubo]

papampi:

I don't have a wtm-miner. That is another reason that I beautify any scripts my miners run with beautify_bash.py. Mismatches like that are trivial to find with the proper indentation. As for the mod I did, here is more of it:

Code:

<cut>
   #IAmNotAJeep MOD from V002
   if [ $JEEP -gt 0 ]
   then
      echo "Debug: JEEP=$JEEP, COUNT=$COUNT, RESTART=$RESTART"
      
      # Begin Stubo Mod
      # Look for no miner screen and get right to miner restart
      if [[ `screen -ls |grep miner |wc -l` -eq 0 ]]
      then
         COUNT=0
	 echo "Found no miner, jumping to 3main restart" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
      fi	  
      # End Stubo Mod

      if [ $COUNT -le 0 ]
      then
         INTERNET_IS_GO=0
<cut>

With this in place, an 8 GPU rig miner restart by the watchdog is reduced from 8 minutes to ~ 10 seconds.

[papampi]

papampi:

I don't have a wtm-miner. That is another reason that I beautify any scripts my miners run with beautify_bash.py. Mismatches like that are trivial to find with the proper indentation. As for the mod I did, here is more of it:

Code:

<cut>
   #IAmNotAJeep MOD from V002
   if [ $JEEP -gt 0 ]
   then
      echo "Debug: JEEP=$JEEP, COUNT=$COUNT, RESTART=$RESTART"
      
      # Begin Stubo Mod
      # Look for no miner screen and get right to miner restart
      if [[ `screen -ls |grep miner |wc -l` -eq 0 ]]
      then
         COUNT=0
	 echo "Found no miner, jumping to 3main restart" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
      fi	  
      # End Stubo Mod

      if [ $COUNT -le 0 ]
      then
         INTERNET_IS_GO=0
<cut>

With this in place, an 8 GPU rig miner restart by the watchdog is reduced from 8 minutes to ~ 10 seconds.

Thanks mate
Can you please have a look at the ~/z_papampi_versions/wtm-miner
and see why it wont exit when done?
I tried with done, exit, exit 0, .... and it stays running in the background