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

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: CryptAtomeTrader44 on September 27, 2017, 05:54:07 PM

Quote from: papampi on September 24, 2017, 05:21:40 AM

Updated my telegram and it will be pushed in v0019-1.2
Here it is if you want to get it sooner :
https://pastebin.com/w3T4BcKm

replace it with existing one
This is what you get if you set the timer :

Code:

Worker: nv102
Boot Time: 2017-09-24 06:11:41
System Up Time: up 7 hours, 1 minute
Miner Uptime: 06:59:02
GPU Count: 7
GPU Utilization:
99 100 97 97 100 97 99

Temp, Fan, Power:
GPU 0, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 135.25
GPU 1, Target temp: 75, Current: 68, Diff: 7, Fan: 65, Power: 137.36
GPU 2, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 136.05
GPU 3, Target temp: 75, Current: 72, Diff: 3, Fan: 65, Power: 133.92
GPU 4, Target temp: 75, Current: 57, Diff: 18, Fan: 65, Power: 136.58
GPU 5, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 137.50
GPU 6, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 132.73

And these are IAmNotAJeep watch dog alerts in case any thing goes wrong:

Code:

date-time - Starting miner restart script.

Code:

date-time - Lost GPU so restarting system.
reboot in 10 seconds

Code:

date-time - Utilization is too low: restart 3main

Code:

date-time - Utilization is too low: reviving did not work so restarting system in 10 seconds

If you have slow/small usb it will clear temp and wdog logs after every message is sent

can you add the last three or five lines of the algo_log file to this monitoring telegram for those using the MPH-Profit_Switching?

This gives an idea of what mine the rig has been for at least 2 hours, at what price and how much time for each line.

This one is with the current mining damNmad suggested working with all nicehash, mph and solso coin
I'm not using salfter switch, so send me your algo_log
So I can see what I should add.

Latest telegram

mikespax

full member

Activity: 362

Merit: 102

I've seen some people mention this coin called Bitcore BTX that's more profitable than what's on top of the whatttomine charts. Perhaps someone could help me out with the code to add it? I believe it's on ccminer

https://whattomine.com/coins/202-btx-timetravel10?utf8=✓&hr=600&p=3000&fee=0.0&cost=0.1&hcost=0.0&commit=Calculate

pckuching

newbie

Activity: 3

Merit: 0

Dear Sir,

how to initial run Zcash under nicehash with v0019 , TQ

leenoox

full member

Activity: 200

Merit: 101

Quote from: crazydane on September 27, 2017, 09:58:37 PM

Quote from: leenoox on September 27, 2017, 09:30:09 PM

You are duplicating "workername", the workername is included in ZENADDR variable, why adding it again? Delete the part listed in orange or you will get something like address.worker.worker instead of address.worker

Those are nice looking stats, where did you get this api? Is it pool specific, miner specific, nvOC specific??? How do you connect to it? You are supplying local network ip address... hrmm... care to share more info about the api?

Thanks. Good catch. I was playing around with the environment variables earlier and forgot to change that back. I know have this, which is generic enough to deploy on all my rigs:

Code:

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEN_POOL --user $ZENADDR --pass z --port $ZEN_PORT --api $IP:42000;

Adding the --api $IP:42000 allows you to point a browser from any machine in your lan, to the ip:port of the miner and get a nice little display showing how that rig is doing. This is a feature built into ewbf. I did open an issue on Github for this (the api stopping working if the pool drops out), but since the author of ewbf seems to have run off for the last month or so, I'm not sure if it will ever get resolved.

Enabling --api kinda makes --pec redundant since it passes the same information to the api, especially if you run your rig monitor less and don't plan to teamview into it.

Oh, I never used ewbf, hence my lack of knowledge about it... thanks for the info though, if/when i start using ewbf i will try it.

It seems it's ewbf linux bug... if it works for 10 hours you can use crontab to restart the miner every 10 hours... it's not the best solution, but if you must use the api it seems it's the only solution until the developer fixes the bug... or you can maybe try older version of ewbf that might not be affected by this bug

crazydane

full member

Activity: 558

Merit: 194

Quote from: leenoox on September 27, 2017, 09:30:09 PM

You are duplicating "workername", the workername is included in ZENADDR variable, why adding it again? Delete the part listed in orange or you will get something like address.worker.worker instead of address.worker

Those are nice looking stats, where did you get this api? Is it pool specific, miner specific, nvOC specific??? How do you connect to it? You are supplying local network ip address... hrmm... care to share more info about the api?

Thanks. Good catch. I was playing around with the environment variables earlier and forgot to change that back. I know have this, which is generic enough to deploy on all my rigs:

Code:

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEN_POOL --user $ZENADDR --pass z --port $ZEN_PORT --api $IP:42000;

Adding the --api $IP:42000 allows you to point a browser from any machine in your lan, to the ip:port of the miner and get a nice little display showing how that rig is doing. This is a feature built into ewbf. I did open an issue on Github for this (the api stopping working if the pool drops out), but since the author of ewbf seems to have run off for the last month or so, I'm not sure if it will ever get resolved.

Enabling --api kinda makes --pec redundant since it passes the same information to the api, especially if you run your rig monitor less and don't plan to teamview into it.

leenoox

full member

Activity: 200

Merit: 101

Quote from: CryptAtomeTrader44 on September 27, 2017, 05:33:58 PM

Thank you very much.
With this pseudo, it is easy to recognize you as seasoned linuxien.

Are you bearded !? Wink

I am joking with the caricatures of unixians / linuxians ....

The first export command allowed me to run the nvidia-settings....

Ha ha ha, I had a good laugh... my beard is only 14 inches long Wink

I'm glad it worked, I am a bit rusty in *nix now... it's been about 17 years since I played with it... used to administer few irc, shell, web servers, all *nix based... slowly getting back into shape... I wish I could have more time though...

leenoox

full member

Activity: 200

Merit: 101

Quote from: crazydane on September 27, 2017, 03:53:27 PM

So I have this little bit of custom code added to my 3bash file on all my rigs:

ZENADDR="$ZEN_ADDRESS.$ZEN_WORKER"

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEN_POOL --user $ZENADDR.$WORKERNAME --pass z --port $ZEN_PORT --api 10.0.1.110:42000;

I have 3 rigs that run nvOC (for now) and others that run windows 10. All are mining with EWBF 0.34b. What happens is that after about 10 hours, the nvOC rigs all drop the api functionality at the same time and my browser windows starts showing disconnected for the miner and server, yet they are still mining away. The windows boxes just keep trucking along. I thought is was something with my setup, but a buddy of mine is seeing the exact same thing on the rigs he switched over the ncOC as well.

Killing the miner and restarting it brings the API back to life. This is happening on both 0019 and 0019.1-2 rigs.

Any ideas?

Alternatively, is there a better "single pane of glass" to give me a view similar to this?

img

Thanks

You are duplicating "workername", the workername is included in ZENADDR variable, why adding it again? Delete the part listed in orange or you will get something like address.worker.worker instead of address.worker

Those are nice looking stats, where did you get this api? Is it pool specific, miner specific, nvOC specific??? How do you connect to it? You are supplying local network ip address... hrmm... care to share more info about the api?

leenoox

full member

Activity: 200

Merit: 101

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

If you haven't tried this already, go into bios, under the "Boot" tab you have setting for "Fast Boot", set this to "Disabled". You can also increase "Setup Prompt Timeout" to 2 or 3 seconds. If that doesn't help you would have to try another USB stick (or buy the cheapest SSD).

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: CryptAtomeTrader44 on September 27, 2017, 05:54:07 PM

Quote from: papampi on September 24, 2017, 05:21:40 AM

Updated my telegram and it will be pushed in v0019-1.2
Here it is if you want to get it sooner :
https://pastebin.com/w3T4BcKm

replace it with existing one
This is what you get if you set the timer :

Code:

Worker: nv102
Boot Time: 2017-09-24 06:11:41
System Up Time: up 7 hours, 1 minute
Miner Uptime: 06:59:02
GPU Count: 7
GPU Utilization:
99 100 97 97 100 97 99

Temp, Fan, Power:
GPU 0, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 135.25
GPU 1, Target temp: 75, Current: 68, Diff: 7, Fan: 65, Power: 137.36
GPU 2, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 136.05
GPU 3, Target temp: 75, Current: 72, Diff: 3, Fan: 65, Power: 133.92
GPU 4, Target temp: 75, Current: 57, Diff: 18, Fan: 65, Power: 136.58
GPU 5, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 137.50
GPU 6, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 132.73

And these are IAmNotAJeep watch dog alerts in case any thing goes wrong:

Code:

date-time - Starting miner restart script.

Code:

date-time - Lost GPU so restarting system.
reboot in 10 seconds

Code:

date-time - Utilization is too low: restart 3main

Code:

date-time - Utilization is too low: reviving did not work so restarting system in 10 seconds

If you have slow/small usb it will clear temp and wdog logs after every message is sent

can you add the last three or five lines of the algo_log file to this monitoring telegram for those using the MPH-Profit_Switching?

This gives an idea of what mine the rig has been for at least 2 hours, at what price and how much time for each line.

I know its not the same thing, but i'm using this as of now;

Code:

CURRENT_COIN=$(head -n 1 /home/m1/current-profit)
MSG=" Worker: $WORKERNAME
Currently Mining: $CURRENT_COIN

crazydane

full member

Activity: 558

Merit: 194

Had the API stop working again on the rigs running EWBF on nvOC. So the trigger is a momentary loss of connectivity to the pool The windows rigs running EWBF recovers within seconds, but the nvOC rigs never get the API back up again, but they do go back to mining.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi on September 24, 2017, 05:21:40 AM

Updated my telegram and it will be pushed in v0019-1.2
Here it is if you want to get it sooner :
https://pastebin.com/w3T4BcKm

replace it with existing one
This is what you get if you set the timer :

Code:

Worker: nv102
Boot Time: 2017-09-24 06:11:41
System Up Time: up 7 hours, 1 minute
Miner Uptime: 06:59:02
GPU Count: 7
GPU Utilization:
99 100 97 97 100 97 99

Temp, Fan, Power:
GPU 0, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 135.25
GPU 1, Target temp: 75, Current: 68, Diff: 7, Fan: 65, Power: 137.36
GPU 2, Target temp: 75, Current: 70, Diff: 5, Fan: 65, Power: 136.05
GPU 3, Target temp: 75, Current: 72, Diff: 3, Fan: 65, Power: 133.92
GPU 4, Target temp: 75, Current: 57, Diff: 18, Fan: 65, Power: 136.58
GPU 5, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 137.50
GPU 6, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 132.73

And these are IAmNotAJeep watch dog alerts in case any thing goes wrong:

Code:

date-time - Starting miner restart script.

Code:

date-time - Lost GPU so restarting system.
reboot in 10 seconds

Code:

date-time - Utilization is too low: restart 3main

Code:

date-time - Utilization is too low: reviving did not work so restarting system in 10 seconds

If you have slow/small usb it will clear temp and wdog logs after every message is sent

can you add the last three or five lines of the algo_log file to this monitoring telegram for those using the MPH-Profit_Switching?

This gives an idea of what mine the rig has been for at least 2 hours, at what price and how much time for each line.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi on September 27, 2017, 04:10:28 AM

Salfter, damNmad or any one else good with python ...
I'm trying to fork salfter_mph_switch to use it with whattomine .... and have very little knowledge on python and stuck at the beginning

Code:

#!/usr/bin/env python2.7

import requests;

# grab something from a website
data = requests.get("https://whattomine.com/coins.json");

#print data
coinsData = data.json()['coins'];
coins = coinsData.keys();

includeTags = [ 'HUSH', 'ZEC', 'ZEN']

filterdCoins = {k: v for k, v in coinsData.iteritems() if v['tag'] in includeTags}
coins = filterdCoins.keys()
#print len(filterdCoins)
#print filterdCoins

sort={}
for i in data:
sort[i["tag"] + i["algorithm"] + i["btc_revenue"]]
sort = sorted(sort.items(), key=lambda x:x[1], reverse=True)
print sort

gives me this error :

Code:

python2.7 wtm_switch.py
Traceback (most recent call last):
File "wtm_switch-2.py", line 28, in
sort[i["tag"] + i["algorithm"] + i["btc_revenue"]]
TypeError: string indices must be integers

Why not redo a script in bash directly?

I think there are competent people for this on this forum thread, do not you think?

Fullzero or IAmNotAJeep but also Leenoox.Maxximus and certainly some readers who only pass read the thread to find solutions to their problems.

Scott Alfter stops responding?

I think extracting data from the JSOn once downloaded with wget is not the most difficult, no, I feel that it is the sorting function and associated presentation that is.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: leenoox on September 26, 2017, 07:10:02 PM

Quote from: CryptAtomeTrader44 on September 26, 2017, 12:53:40 PM

Quote from: leenoox on September 25, 2017, 07:26:16 PM

here's the command to change fan speed on a single GPU:

Code:

nvidia-settings -a [gpu:5]/GPUFanControlState=1 -a [fan:5]/GPUTargetFanSpeed=70

This will set fan on GPU5 to 70%. Change as you see fit, however note that if you have Maxximus007_auto_temp control enabled, it will readjust it back on its regular cycle.

That's the response that i recieve :

Code:

sudo nvidia-settings -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=30
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.

Are you executing this in guake terminal while locally logged in or are you loging in trough ssh?
Try this before executing the nvidia-settings command:

Code:

export DISPLAY=:0

or this:

Code:

xhost +

to turn off access control. Once done issue "xhost -" to turn access control back on. By the way, you don't need sudo for nvidia-settings.

Thank you very much.
With this pseudo, it is easy to recognize you as seasoned linuxien.

Are you bearded !? Wink

I am joking with the caricatures of unixians / linuxians ....

The first export command allowed me to run the nvidia-settings. Can you explain to me why I have to do this?

I also rediscover via the man page this command "xhost" that I use for the first time! Clever command that this one.

I'll be able to at least temporarily reduce the noise a bit from time to time.

Would not you be able to make a script sorting the cryptos values given by the Whattomine JSON? When I do a cat of the JSON file, it seems to me that retrieving the text values of this file is not so difficult with sed and awk or other grep. But to produce a sorting function of these values in numbers and in associated text, that I know I could not do.

IAmNotAJeep

newbie

Activity: 44

Merit: 0

Quote from: papampi on September 27, 2017, 03:35:10 PM

Quote from: IAmNotAJeep on September 27, 2017, 02:44:55 PM

Quote from: Reinars on September 27, 2017, 02:40:45 PM

Quote from: IAmNotAJeep on September 27, 2017, 09:24:15 AM

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

I've had this bug too on the same boards, unfortunately you need to power cycle, or get an SRR to listen for a hearbeat and do it for you after it stops. (https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdf)

Maybe others have a different solution, but for a remote location this one works reliably for me.

Thanks, this is amazing stuff tho there is one problem with this.
Whenever my computer restarts, It does not recognize the usb until I re-plug it. It just boots straight into bios without doing anything and there is no boot devices available.

hmm does this behaviour survive the power cycle?
I haven't had to deal with this for a while, but from what I remember if the power to the mobo was turned off and the back on, it would re-see the usb.

isn't it easier to install system on a 100$ ssd?
Each rig cost over 2k if not much more, why go cheap with one of the most important parts of it?
Faster, bigger, and no problems.

True, thought about the pros and cons a few times (booting off of a USB is a pain), in the end I would always come down by far in favour of maximizing revenue generating components and making things as cookie-cutter as I can.

crazydane

full member

Activity: 558

Merit: 194

So I have this little bit of custom code added to my 3bash file on all my rigs:

ZENADDR="$ZEN_ADDRESS.$ZEN_WORKER"

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEN_POOL --user $ZENADDR.$WORKERNAME --pass z --port $ZEN_PORT --api 10.0.1.110:42000;

I have 3 rigs that run nvOC (for now) and others that run windows 10. All are mining with EWBF 0.34b. What happens is that after about 10 hours, the nvOC rigs all drop the api functionality at the same time and my browser windows starts showing disconnected for the miner and server, yet they are still mining away. The windows boxes just keep trucking along. I thought is was something with my setup, but a buddy of mine is seeing the exact same thing on the rigs he switched over the ncOC as well.

Killing the miner and restarting it brings the API back to life. This is happening on both 0019 and 0019.1-2 rigs.

Any ideas?

Alternatively, is there a better "single pane of glass" to give me a view similar to this?

Thanks

lakesidedan

newbie

Activity: 1

Merit: 0

I just wanted to say thanks for an awesome mining solution. We currently have two 12 x 1080ti rigs on the Biostar Pro board that have been up and running mining zcash on v18 for almost two months now with very few issues. I'm looking forward to moving to V19.

Many thanks and kudos to all the generous and knowledgeable contributors to this endeavor.

Temporel

full member

Activity: 224

Merit: 100

Quote from: Reinars on September 27, 2017, 02:40:45 PM

Quote from: IAmNotAJeep on September 27, 2017, 09:24:15 AM

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

I've had this bug too on the same boards, unfortunately you need to power cycle, or get an SRR to listen for a hearbeat and do it for you after it stops. (https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdf)

Maybe others have a different solution, but for a remote location this one works reliably for me.

Thanks, this is amazing stuff tho there is one problem with this.
Whenever my computer restarts, It does not recognize the usb until I re-plug it. It just boots straight into bios without doing anything and there is no boot devices available.

so you have tried with another usb stick ?? Its a very common problem that some USB stick wont boot properly with some motherboard.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: IAmNotAJeep on September 27, 2017, 02:44:55 PM

Quote from: Reinars on September 27, 2017, 02:40:45 PM

Quote from: IAmNotAJeep on September 27, 2017, 09:24:15 AM

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

I've had this bug too on the same boards, unfortunately you need to power cycle, or get an SRR to listen for a hearbeat and do it for you after it stops. (https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdf)

Maybe others have a different solution, but for a remote location this one works reliably for me.

Thanks, this is amazing stuff tho there is one problem with this.
Whenever my computer restarts, It does not recognize the usb until I re-plug it. It just boots straight into bios without doing anything and there is no boot devices available.

hmm does this behaviour survive the power cycle?
I haven't had to deal with this for a while, but from what I remember if the power to the mobo was turned off and the back on, it would re-see the usb.

isn't it easier to install system on a 100$ ssd?
Each rig cost over 2k if not much more, why go cheap with one of the most important parts of it?
Faster, bigger, and no problems.

IAmNotAJeep

newbie

Activity: 44

Merit: 0

Quote from: Reinars on September 27, 2017, 02:40:45 PM

Quote from: IAmNotAJeep on September 27, 2017, 09:24:15 AM

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

I've had this bug too on the same boards, unfortunately you need to power cycle, or get an SRR to listen for a hearbeat and do it for you after it stops. (https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdf)

Maybe others have a different solution, but for a remote location this one works reliably for me.

Thanks, this is amazing stuff tho there is one problem with this.
Whenever my computer restarts, It does not recognize the usb until I re-plug it. It just boots straight into bios without doing anything and there is no boot devices available.

hmm does this behaviour survive the power cycle?
I haven't had to deal with this for a while, but from what I remember if the power to the mobo was turned off and the back on, it would re-see the usb.

Reinars

newbie

Activity: 13

Merit: 0

Quote from: IAmNotAJeep on September 27, 2017, 09:24:15 AM

Quote from: Reinars on September 26, 2017, 05:02:12 PM

Hello there. I must say- Amazing stuff here.
Just had a one question. My Riggs sometimes restarts and when they do, after restart they enter in bios because the USB isn't recognized. I have to manually replug USB and then it boots up again.
I have a AsRock h110 BTC+ board and a 3.0 16gb usb stick

I've had this bug too on the same boards, unfortunately you need to power cycle, or get an SRR to listen for a hearbeat and do it for you after it stops. (https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdf)

Maybe others have a different solution, but for a remote location this one works reliably for me.

Thanks, this is amazing stuff tho there is one problem with this.
Whenever my computer restarts, It does not recognize the usb until I re-plug it. It just boots straight into bios without doing anything and there is no boot devices available.

Topic: [ mining os ] nvoc - page 211. (Read 418546 times)