Pages:
Author

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

fk1
full member
Activity: 216
Merit: 100
January 06, 2018, 01:07:41 PM
I just found out I accidentially pasted my ZEC/ZCL config twice in 1bash. fixed that, new report stated above:
Code:

Software info:
Report ver    :  v0019-2.0.002
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release
nvOC (3main)  :  nvOC v0019-2.0 - Community Release
1bash ver     :  v0019-2.0.003
3main ver     :  v0019-2.0.006
5watchdog ver :  v0019-2.0.011
6tempcontrol v:  v0019-2.0.003
wtm switch ver:  v0019-2.0.0011
Kernel        :  4.4.0-97-generic
OS            :  Ubuntu 16.04.3 LTS
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver :  387.12

Hardware info:
Motherboard   :  ASUS STRIX Z270F GAMING  Rev 1.xx
BIOS ver.     :  1009 07/23/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3984632 kB
Mem Free      :         3049740 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
└─sda2 55.9G ext4   part    0       0                                       /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c82 (rev a1)

1bash settings:
1bash version .............: v0019-2.0.003
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES

Temp Control ..............: YES
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 50

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS .: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 480
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

P106_100_FULL_HEADLESS_MODE: NO
GPUPowerMizerMode_Adjust...: NO
POWERLIMIT (global) .......: YES
POWERLIMIT_WATTS ..........: 76
CORE_OVERCLOCK (global)....: 150
MEMORY_OVERCLOCK (global) .: 800
MANUAL_FAN ................: NO
ALGO_SPECIFIC_OC ..........: YES

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: CUSTOM
CUSTOM_WORKERNAME .........: 02
plusCPU ...................: NO

ZM_or_EWBF ................: EWBF
EWBF_VERSION ..............: 3_4
EWBF_PERCENT ..............: 0

COIN ......................: ZCL
ZCL_WORKER ................: 02
ZCL_ADDRESS ...............: xxxxx...
ZCL_POOL ..................: europe.zclassic.miningpoolhub.com
ZCL_PORT ..................: 20575

unfortunately still no mining process

I curled 0miner 1bash and 3main from git and got ZCL to work so I guess I had a typo or something somewhere when I tried to handle this problem. tyvm nvtl
member
Activity: 126
Merit: 10
January 06, 2018, 12:43:05 PM
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.

I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.

Cheers


I have some code to share with you but the site is blocking my input.
Trying to contact with an admin about.
Thanks :-) Maybe you can post a link outside this forum

Ok, have a look at this and see if can help:
https://bitcointalksearch.org/topic/m.22615430

I don't use Nvoc's temp control.

Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware):
https://pastebin.com/mcqmt9CF

It is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi.
I just look forward to have a well configured rig and make it work stable instead of using wdog.
I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc).
Hi kk003,

This is awsome!! I will modify the code according the my setup.
As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct?
In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat:

Code:
nc -z -v -w5 $rigIP 22

(w5 is a timeout of 5 seconds)

Thanks again :-)

Since we are on RPi talks ...
How many rigs can be monitored and reboot/reset/hard reboot with one RPi?
What are the hardwares needed for multiple rig control?

I'm not much of a hardware guy but love to make a rig controller with RPi if its not too hard.
Hi Papampi,
A Raspberry Pi 2B or 3B has up to 26 programmable digital pins (the original Raspberry Pi B has only 17).
You could connect each digital output to an optocoupler or a relay and control the power swithch and/or the reset button of the motherboard.
Suppose that you want to want to control both switch and reset of each mobo, that would make that you could monitor up to 13 mobo (26 if you just want to control the reset switch).

You can also connect digital temperature sensors to the pins (programming them in input mode).
You can find pretty inexpensive ready made relay boards with up to 16 relays.

In practice the hardware needed for for controlling 12 mobos would be:
1) 16 relay module. There are many on Amazon, for example https://www.amazon.com/SainSmart-101-70-103-16-Channel-Relay-Module/dp/B0057OC66U
2) 8 relay module.
3) Usb power supply
4) Optional external HDMI screen, unless you are running the RPi headless through SSH
5) Of course, a raspberry Pi
6) Plenty of cables with female Dupont connectors

The standard OS for the Raspberry Pi is Debian (Raspbian), but if you prefer you can have as well Ubuntu or Windows 10 IoT.
The advantage of Raspbian is that it comes with all the utilities for controlling directly the GPIO pins, either from Bash or a high level language like C++ or Python.


Awesome, Thanks a lot for the info
I have 3 RPi 2B that dont use any more because when 3B came out I replaced them for faster kodi
So I'm going to get a relay module and start playing with it, for sure I'm going to ask for more help on programming and connecting the relay to the board and ...

Thanks a lot mate
Keep calm and carry on mining Wink
No problems ;-)
Just a thing, do not buy the board that I put in the link of my previous message. I justs realised that the inputs are for 5V signals while what you need is a board compatible with 3.3V signals. Look for a board that is specifically designed for the RPi.
fk1
full member
Activity: 216
Merit: 100
January 06, 2018, 12:14:30 PM
I just found out I accidentially pasted my ZEC/ZCL config twice in 1bash. fixed that, new report stated above:
Code:

Software info:
Report ver    :  v0019-2.0.002
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release
nvOC (3main)  :  nvOC v0019-2.0 - Community Release
1bash ver     :  v0019-2.0.003
3main ver     :  v0019-2.0.006
5watchdog ver :  v0019-2.0.011
6tempcontrol v:  v0019-2.0.003
wtm switch ver:  v0019-2.0.0011
Kernel        :  4.4.0-97-generic
OS            :  Ubuntu 16.04.3 LTS
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver :  387.12

Hardware info:
Motherboard   :  ASUS STRIX Z270F GAMING  Rev 1.xx
BIOS ver.     :  1009 07/23/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3984632 kB
Mem Free      :         3049740 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
└─sda2 55.9G ext4   part    0       0                                       /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c82 (rev a1)

1bash settings:
1bash version .............: v0019-2.0.003
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES

Temp Control ..............: YES
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 50

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS .: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 480
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

P106_100_FULL_HEADLESS_MODE: NO
GPUPowerMizerMode_Adjust...: NO
POWERLIMIT (global) .......: YES
POWERLIMIT_WATTS ..........: 76
CORE_OVERCLOCK (global)....: 150
MEMORY_OVERCLOCK (global) .: 800
MANUAL_FAN ................: NO
ALGO_SPECIFIC_OC ..........: YES

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: CUSTOM
CUSTOM_WORKERNAME .........: 02
plusCPU ...................: NO

ZM_or_EWBF ................: EWBF
EWBF_VERSION ..............: 3_4
EWBF_PERCENT ..............: 0

COIN ......................: ZCL
ZCL_WORKER ................: 02
ZCL_ADDRESS ...............: xxxxx...
ZCL_POOL ..................: europe.zclassic.miningpoolhub.com
ZCL_PORT ..................: 20575

unfortunately still no mining process
fk1
full member
Activity: 216
Merit: 100
January 06, 2018, 12:03:46 PM
Hi! I jsut installed nvOC 0019 2.0 but unfortunately since then I am not able to mine ZEC or ZCL anymore. I am not sure whats wrong, theres just no screen to resume and cat 5_watchdoglog says:
Code:
WARNING: Sat Jan  6 06:51:57 MST 2018 - Problem found: See diagnostics below:
Percent of GPUs bellow threshold: 100 %
name, pstate, temperature.gpu, fan.speed [%], utilization.gpu [%], power.draw [W], power.limit [W]
GeForce GTX 1050 Ti, P8, 23, 50 %, 0 %, [Unknown Error], 76.00 W
    --noreconnect    Disable automatic reconnection on network errors.

    --temp-target    In C - If set, enables temperature controller.
                     The workload of each GPU will be continuously
                     adjusted such that the temperature stays around
                     this value. It is recommended to set your fan speed
                     to 100% when using this setting.

    --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
                     can be accessed using a web browser(http) or by json-rpc.
                     If no arguments are given the server listens on
                     127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
                     Valid port range [1025-65535]
 Example:
    zm --server servername.com --port 1234 --user username
CRITICAL: Sat Jan  6 06:51:57 MST 2018 - GPU Utilization is too low: restarting 3main...

I want to mine to miningpoolhub and everything worked fine under v0019 1.0. As I am trying to figure out I wonder what is the best method to restart the mining process since I am tired of rebooting the whole machine...


MiningPoolHub twittert some problems with the pool. Please try another one.

To restart the mining process you can restart the console window. There is no need to reboot the machine.

Please post settings for your coins, it seems some settings mismatch to me
Also post output of :

Code:
~/nvOC report

1 bash:
Code:
# ZEC
ZEC_WORKER=$WORKERNAME
# replace_with_your_ZEC_address
ZEC_ADDRESS="xxxxx"
ZEC_POOL="europe.equihash-hub.miningpoolhub.com"
ZEC_PORT="20570"

# ZCL
ZCL_WORKER="02"
ZCL_ADDRESS="xxxxx"
ZCL_POOL="europe.zclassic.miningpoolhub.com"
ZCL_PORT="20575"

0miner:
Code:
if [ $COIN == "ZEC" ]
then

  if [ $EWBF_VERSION == "3_3" ]
  then
    HCD='/home/m1/zec/v3_3/miner'
  fi

  if [ $EWBF_VERSION == "3_4" ]
  then
    HCD='/home/m1/zec/v3_4/miner'
  fi

  ZECADDR="$ZEC_ADDRESS.$ZEC_WORKER"

  if [ $ZM_or_EWBF == "ZM" ]
  then
    HCD='/home/m1/zec/zm/latest/zm_miner'
    screen -dmSL miner $HCD --server $ZEC_POOL --user $ZECADDR --pass $MINER_PWD --port $ZEC_PORT  --time $ZM_OPTS ;
  fi

  if [ $ZM_or_EWBF == "EWBF" ]
  then
    screen -dmSL miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEC_POOL --user $ZECADDR --pass $MINER_PWD --port $ZEC_PORT  $EWBF_OPTS ;
  fi
fi

if [ $COIN == "ZCL" ]
then

  if [ $EWBF_VERSION == "3_3" ]
  then
    HCD='/home/m1/zec/v3_3/miner'
  fi

  if [ $EWBF_VERSION == "3_4" ]
  then
    HCD='/home/m1/zec/v3_4/miner'
  fi

  ZCLADDR="$ZCL_ADDRESS.$ZCL_WORKER"

  if [ $ZM_or_EWBF == "ZM" ]
  then
    HCD='/home/m1/zec/zm/latest/zm_miner'
    screen -dmSL miner $HCD --server $ZCL_POOL --user $ZCLADDR --pass $MINER_PWD --port $ZCL_PORT  --time $ZM_OPTS ;
  fi

  if [ $ZM_or_EWBF == "EWBF" ]
  then
    screen -dmSL miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZCL_POOL --user $ZCLADDR --pass $MINER_PWD --port $ZCL_PORT  $EWBF_OPTS ;
  fi
fi

output ~/nvOC report:


      Report generator v0019-2.0.002 by leenoox


Code:

Software info:
Report ver    :  v0019-2.0.002
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release
nvOC (3main)  :  nvOC v0019-2.0 - Community Release
1bash ver     :  v0019-2.0.003
3main ver     :  v0019-2.0.006
5watchdog ver :  v0019-2.0.011
6tempcontrol v:  v0019-2.0.003
wtm switch ver:  v0019-2.0.0011
Kernel        :  4.4.0-97-generic
OS            :  Ubuntu 16.04.3 LTS
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver :  387.12

Hardware info:
Motherboard   :  ASUS STRIX Z270F GAMING  Rev 1.xx
BIOS ver.     :  1009 07/23/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3984632 kB
Mem Free      :         3041620 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
└─sda2 55.9G ext4   part    0       0                                       /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c82 (rev a1)

1bash settings:
1bash version .............: v0019-2.0.003
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES

Temp Control ..............: YES
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 50

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS .: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 480
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

P106_100_FULL_HEADLESS_MODE: NO
GPUPowerMizerMode_Adjust...: NO
POWERLIMIT (global) .......: YES
POWERLIMIT_WATTS ..........: 76
CORE_OVERCLOCK (global)....: 100
MEMORY_OVERCLOCK (global) .: 100
MANUAL_FAN ................: NO
ALGO_SPECIFIC_OC ..........: YES

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: CUSTOM
CUSTOM_WORKERNAME .........: 02
plusCPU ...................: NO

ZM_or_EWBF ................:

COIN ......................: ZCL
ZCL_WORKER ................: 02
ZCL_ADDRESS ...............: ...
ZCL_POOL ..................:


strange thing is no ZM or EWBF showing up but it is set in 1bash:

Code:
ZM_or_EWBF="EWBF"  # choose ZM or EWBF miner
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
January 06, 2018, 12:01:08 PM
For equihash miners, It's a bit off topic but it can probably shed light on Zclassic's violent and sudden rise this day:

Here is a news that explain the great raise of ZCL this day :
https://medium.com/chain-intelligence/the-resurgence-of-zcl-and-an-upcoming-hardfork-3ba65de3cf21

hardfok is comming on this currencie :

"While the fork wasn’t ready by Christmas eve, development is currently under progress and the date for the snapshot will likely be near mid January or the end of January.

At the high level, the plan is the following:

    Circulating BTC = 17 million, Circulating ZCL = 2 million.
    The ZClassic coin will be migrated to become a Bitcoin hard-fork “Bitcoin Private” or “BTCP” by dropping coinbase inputs into the blockchain as a hard-fork.
    This way, holders of BTC (or BCH) will receive BTCP in a 1:1 ratio and holders of ZCL will receive BTCP in a 1:1 ratio as well.
    The community is still in the process of deciding the details of the fork, choosing between non-SegWit BTC addresses and BCH addresses.
    BTCP will regardless be a fork of Bitcoin, and the first purely privacy focused Bitcoin fork driven by the community itself. Its circulation will be roughly 19 million at the time of the drop."


I took my benefits now, this night. I hope i will profit of segweet2x BTC hardforkthis night too



Here is the continuation of this story of the end of Zclassic and the birth of BTCP aka Bitcoin Private

Their web site is online, and from what I read on the web, the new Wallet will be available from January 8
https://bitcoinpvt.org/?lang=fr_FR

I think I will mine ZCL this weekend and return to wtm switch right after.

When I think I sold 1.98 ZCL at 241 kSAT the unit and it is worth 0.01 BTC this day! Once again the information is really the key for the economy of cryptocurrency as for the traditional financial market.

Remember, they will pay for both ZCL and also for BTC because it is a HF BTC they announce.
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
January 06, 2018, 11:31:46 AM
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.

I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.

Cheers


I have some code to share with you but the site is blocking my input.
Trying to contact with an admin about.
Thanks :-) Maybe you can post a link outside this forum

Ok, have a look at this and see if can help:
https://bitcointalksearch.org/topic/m.22615430

I don't use Nvoc's temp control.

Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware):
https://pastebin.com/mcqmt9CF

It is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi.
I just look forward to have a well configured rig and make it work stable instead of using wdog.
I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc).
Hi kk003,

This is awsome!! I will modify the code according the my setup.
As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct?
In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat:

Code:
nc -z -v -w5 $rigIP 22

(w5 is a timeout of 5 seconds)

Thanks again :-)

Since we are on RPi talks ...
How many rigs can be monitored and reboot/reset/hard reboot with one RPi?
What are the hardwares needed for multiple rig control?

I'm not much of a hardware guy but love to make a rig controller with RPi if its not too hard.
Hi Papampi,
A Raspberry Pi 2B or 3B has up to 26 programmable digital pins (the original Raspberry Pi B has only 17).
You could connect each digital output to an optocoupler or a relay and control the power swithch and/or the reset button of the motherboard.
Suppose that you want to want to control both switch and reset of each mobo, that would make that you could monitor up to 13 mobo (26 if you just want to control the reset switch).

You can also connect digital temperature sensors to the pins (programming them in input mode).
You can find pretty inexpensive ready made relay boards with up to 16 relays.

In practice the hardware needed for for controlling 12 mobos would be:
1) 16 relay module. There are many on Amazon, for example https://www.amazon.com/SainSmart-101-70-103-16-Channel-Relay-Module/dp/B0057OC66U
2) 8 relay module.
3) Usb power supply
4) Optional external HDMI screen, unless you are running the RPi headless through SSH
5) Of course, a raspberry Pi
6) Plenty of cables with female Dupont connectors

The standard OS for the Raspberry Pi is Debian (Raspbian), but if you prefer you can have as well Ubuntu or Windows 10 IoT.
The advantage of Raspbian is that it comes with all the utilities for controlling directly the GPIO pins, either from Bash or a high level language like C++ or Python.


Awesome, Thanks a lot for the info
I have 3 RPi 2B that dont use any more because when 3B came out I replaced them for faster kodi
So I'm going to get a relay module and start playing with it, for sure I'm going to ask for more help on programming and connecting the relay to the board and ...

Thanks a lot mate
Keep calm and carry on mining Wink
member
Activity: 126
Merit: 10
January 06, 2018, 11:25:01 AM
  For those people who are considering to use a RPi as a controller, just remember it does use a micro sd and I did burn up two 64 gig
playing around with them. They work wonderful and you can do a lot with them but when the max write limit is hit, bye bye. Both my
Pie's are on the shelf with me wondering what to do with them.

thay
Hi Thaelin,
The original RPi used a microSD, while the newer RPi 2 and 3 require a nanoSD card.
As always, it all depends on the quality of the card you are using. I have for example an RPi that has been working continuously for the last 3 years as a temperature sensor without any problems.
The same kind or reasoning with running nvOC from a USB key is applicable, meaning that if you are continuously updating log files, or worse, using the card as virtual memory, you are going to kill the SD card rather quickly.
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
January 06, 2018, 11:21:07 AM
Running into some weird issue with 19_1.4 New install, just keeps throwing an error and rebooting due to not being able to resolve host. Host/hostname is fine. If i connect a keyboard while startup, and cancel the reboot it works and mines tho its weird. Where is the lookup for resolving on the boot script so i can modify?


Unknown Host is a known issue in 19-1.4
as soon as your rig boots and loaded the gnome-terminal close it then:

Either edit hosts and  hostname in /etc/ and make them same

Or better to update to 19-2.0 with update script :

Code:
cd /home/m1/Downloads
wget https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update
bash /home/m1/Downloads/nvOC-19-2-update
member
Activity: 126
Merit: 10
January 06, 2018, 11:17:50 AM
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.

I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.

Cheers


I have some code to share with you but the site is blocking my input.
Trying to contact with an admin about.
Thanks :-) Maybe you can post a link outside this forum

Ok, have a look at this and see if can help:
https://bitcointalksearch.org/topic/m.22615430

I don't use Nvoc's temp control.

Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware):
https://pastebin.com/mcqmt9CF

It is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi.
I just look forward to have a well configured rig and make it work stable instead of using wdog.
I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc).
Hi kk003,

This is awsome!! I will modify the code according the my setup.
As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct?
In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat:

Code:
nc -z -v -w5 $rigIP 22

(w5 is a timeout of 5 seconds)

Thanks again :-)

Since we are on RPi talks ...
How many rigs can be monitored and reboot/reset/hard reboot with one RPi?
What are the hardwares needed for multiple rig control?

I'm not much of a hardware guy but love to make a rig controller with RPi if its not too hard.
Hi Papampi,
A Raspberry Pi 2B or 3B has up to 26 programmable digital pins (the original Raspberry Pi B has only 17).
You could connect each digital output to an optocoupler or a relay and control the power swithch and/or the reset button of the motherboard.
Suppose that you want to want to control both switch and reset of each mobo, that would make that you could monitor up to 13 mobo (26 if you just want to control the reset switch).

You can also connect digital temperature sensors to the pins (programming them in input mode).
You can find pretty inexpensive ready made relay boards with up to 16 relays.

In practice the hardware needed for for controlling 12 mobos would be:
1) 16 relay module. There are many on Amazon, for example https://www.amazon.com/SainSmart-101-70-103-16-Channel-Relay-Module/dp/B0057OC66U
2) 8 relay module.
3) Usb power supply
4) Optional external HDMI screen, unless you are running the RPi headless through SSH
5) Of course, a raspberry Pi
6) Plenty of cables with female Dupont connectors

The standard OS for the Raspberry Pi is Debian (Raspbian), but if you prefer you can have as well Ubuntu or Windows 10 IoT.
The advantage of Raspbian is that it comes with all the utilities for controlling directly the GPIO pins, either from Bash or a high level language like C++ or Python.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
January 06, 2018, 11:10:51 AM
I was having some issues this week with some pools and decide to rewrite the code for pool check in watchdog, it was supposed to be in v19-2.0 but we let it slide for that time.

It works almost same as network check but instead of checking for network it checks for pool and wait if its unreachable to prevent miner restart and eventually rig restarts.
Then After I wrote it I thought why wait and waste time when we can switch to an alternate pool
So I rewrite it again to add an alternate pool in 1bash whether its supported by the miner or not.
What left to do is to check the first pool and switch back as soon as it becomes available.


So here is my question:
How important it is for you guys to have an alternate pool?
And how important it is to switch back to main pool?


I'm asking this because I wrote the code for myself and to make it work with rest of miners and coins it needs more changes so I don't want to work on something not so useful Wink

It's clear that luckpool has had a lot of hits this week. They probably have lower fee than elsewhere but their servers seem unstable, so I decided to go elsewhere, even if it costs me a little more fee.
When I look at MPH and the number of pools they have and I have never had a single break with them, all I can switch home, I rock it.

I also had troubles with Nicehash who all of a sudden Wednesday night began to refuse my connections to their servers ... So I created a ticket home and removed nicehash from my list of WTM switch ...

Your proposal to send to another alternative pool is a good idea, but I have another one: Why not try the second corner directly in the WTM list.

Obviously this only works for those who use WTM_Switch, but it must be possible to combine both a second pool and a second coin with or without the SWITCH WTM.
newbie
Activity: 35
Merit: 0
January 06, 2018, 11:00:35 AM
Running into some weird issue with 19_1.4 New install, just keeps throwing an error and rebooting due to not being able to resolve host. Host/hostname is fine. If i connect a keyboard while startup, and cancel the reboot it works and mines tho its weird. Where is the lookup for resolving on the boot script so i can modify?
member
Activity: 104
Merit: 10
January 06, 2018, 10:32:40 AM
Hi guys any 1050ti neoscrypt miner here? can u share ur Hashrate / CCminer version / OC i think i cant maxmize mine just doing 300-350 Khs per card

TIA
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
January 06, 2018, 09:48:25 AM
Hi! I jsut installed nvOC 0019 2.0 but unfortunately since then I am not able to mine ZEC or ZCL anymore. I am not sure whats wrong, theres just no screen to resume and cat 5_watchdoglog says:
Code:
WARNING: Sat Jan  6 06:51:57 MST 2018 - Problem found: See diagnostics below:
Percent of GPUs bellow threshold: 100 %
name, pstate, temperature.gpu, fan.speed [%], utilization.gpu [%], power.draw [W], power.limit [W]
GeForce GTX 1050 Ti, P8, 23, 50 %, 0 %, [Unknown Error], 76.00 W
    --noreconnect    Disable automatic reconnection on network errors.

    --temp-target    In C - If set, enables temperature controller.
                     The workload of each GPU will be continuously
                     adjusted such that the temperature stays around
                     this value. It is recommended to set your fan speed
                     to 100% when using this setting.

    --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
                     can be accessed using a web browser(http) or by json-rpc.
                     If no arguments are given the server listens on
                     127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
                     Valid port range [1025-65535]
 Example:
    zm --server servername.com --port 1234 --user username
CRITICAL: Sat Jan  6 06:51:57 MST 2018 - GPU Utilization is too low: restarting 3main...

I want to mine to miningpoolhub and everything worked fine under v0019 1.0. As I am trying to figure out I wonder what is the best method to restart the mining process since I am tired of rebooting the whole machine...


MiningPoolHub twittert some problems with the pool. Please try another one.

To restart the mining process you can restart the console window. There is no need to reboot the machine.

Please post settings for your coins, it seems some settings mismatch to me
Also post output of :

Code:
~/nvOC report
newbie
Activity: 41
Merit: 0
January 06, 2018, 09:42:19 AM
Hi! I jsut installed nvOC 0019 2.0 but unfortunately since then I am not able to mine ZEC or ZCL anymore. I am not sure whats wrong, theres just no screen to resume and cat 5_watchdoglog says:
Code:
WARNING: Sat Jan  6 06:51:57 MST 2018 - Problem found: See diagnostics below:
Percent of GPUs bellow threshold: 100 %
name, pstate, temperature.gpu, fan.speed [%], utilization.gpu [%], power.draw [W], power.limit [W]
GeForce GTX 1050 Ti, P8, 23, 50 %, 0 %, [Unknown Error], 76.00 W
    --noreconnect    Disable automatic reconnection on network errors.

    --temp-target    In C - If set, enables temperature controller.
                     The workload of each GPU will be continuously
                     adjusted such that the temperature stays around
                     this value. It is recommended to set your fan speed
                     to 100% when using this setting.

    --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
                     can be accessed using a web browser(http) or by json-rpc.
                     If no arguments are given the server listens on
                     127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
                     Valid port range [1025-65535]
 Example:
    zm --server servername.com --port 1234 --user username
CRITICAL: Sat Jan  6 06:51:57 MST 2018 - GPU Utilization is too low: restarting 3main...

I want to mine to miningpoolhub and everything worked fine under v0019 1.0. As I am trying to figure out I wonder what is the best method to restart the mining process since I am tired of rebooting the whole machine...


MiningPoolHub twittert some problems with the pool. Please try another one.

To restart the mining process you can restart the console window. There is no need to reboot the machine.
newbie
Activity: 41
Merit: 0
January 06, 2018, 09:40:45 AM
I was having some issues this week with some pools and decide to rewrite the code for pool check in watchdog, it was supposed to be in v19-2.0 but we let it slide for that time.

It works almost same as network check but instead of checking for network it checks for pool and wait if its unreachable to prevent miner restart and eventually rig restarts.
Then After I wrote it I thought why wait and waste time when we can switch to an alternate pool
So I rewrite it again to add an alternate pool in 1bash whether its supported by the miner or not.
What left to do is to check the first pool and switch back as soon as it becomes available.


So here is my question:
How important it is for you guys to have an alternate pool?
And how important it is to switch back to main pool?


I'm asking this because I wrote the code for myself and to make it work with rest of miners and coins it needs more changes so I don't want to work on something not so useful Wink





I would totally f... love that ;-)

regards
fk1
full member
Activity: 216
Merit: 100
January 06, 2018, 09:40:42 AM
Hi! I jsut installed nvOC 0019 2.0 but unfortunately since then I am not able to mine ZEC or ZCL anymore. I am not sure whats wrong, theres just no screen to resume and cat 5_watchdoglog says:
Code:
WARNING: Sat Jan  6 06:51:57 MST 2018 - Problem found: See diagnostics below:
Percent of GPUs bellow threshold: 100 %
name, pstate, temperature.gpu, fan.speed [%], utilization.gpu [%], power.draw [W], power.limit [W]
GeForce GTX 1050 Ti, P8, 23, 50 %, 0 %, [Unknown Error], 76.00 W
    --noreconnect    Disable automatic reconnection on network errors.

    --temp-target    In C - If set, enables temperature controller.
                     The workload of each GPU will be continuously
                     adjusted such that the temperature stays around
                     this value. It is recommended to set your fan speed
                     to 100% when using this setting.

    --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
                     can be accessed using a web browser(http) or by json-rpc.
                     If no arguments are given the server listens on
                     127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
                     Valid port range [1025-65535]
 Example:
    zm --server servername.com --port 1234 --user username
CRITICAL: Sat Jan  6 06:51:57 MST 2018 - GPU Utilization is too low: restarting 3main...

I want to mine to miningpoolhub and everything worked fine under v0019 1.0. As I am trying to figure out I wonder what is the best method to restart the mining process since I am tired of rebooting the whole machine...
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
January 06, 2018, 07:14:36 AM
I was having some issues this week with some pools and decide to rewrite the code for pool check in watchdog, it was supposed to be in v19-2.0 but we let it slide for that time.

It works almost same as network check but instead of checking for network it checks for pool and wait if its unreachable to prevent miner restart and eventually rig restarts.
Then After I wrote it I thought why wait and waste time when we can switch to an alternate pool
So I rewrite it again to add an alternate pool in 1bash whether its supported by the miner or not.
What left to do is to check the first pool and switch back as soon as it becomes available.


So here is my question:
How important it is for you guys to have an alternate pool?
And how important it is to switch back to main pool?


I'm asking this because I wrote the code for myself and to make it work with rest of miners and coins it needs more changes so I don't want to work on something not so useful Wink



newbie
Activity: 64
Merit: 0
January 06, 2018, 05:44:36 AM
   For those people who are considering to use a RPi as a controller, just remember it does use a micro sd and I did burn up two 64 gig
playing around with them. They work wonderful and you can do a lot with them but when the max write limit is hit, bye bye. Both my
Pie's are on the shelf with me wondering what to do with them.

thay
member
Activity: 117
Merit: 10
January 06, 2018, 05:13:46 AM
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.

I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.

Cheers


I have some code to share with you but the site is blocking my input.
Trying to contact with an admin about.
Thanks :-) Maybe you can post a link outside this forum

Ok, have a look at this and see if can help:
https://bitcointalksearch.org/topic/m.22615430

I don't use Nvoc's temp control.

Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware):
https://pastebin.com/mcqmt9CF

It is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi.
I just look forward to have a well configured rig and make it work stable instead of using wdog.
I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc).
Hi kk003,

This is awsome!! I will modify the code according the my setup.
As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct?
In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat:

Code:
nc -z -v -w5 $rigIP 22

(w5 is a timeout of 5 seconds)

Thanks again :-)

The script checks that temp room is too high, if so turnoff the rig, then wait 120 seconds and ping the rig again (it should be power off by now).
I agreed with you some times the ping is not enough to make sure that the rig is on/off. I should add the bit with netcat as a double check.
Thx. 
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
January 06, 2018, 04:54:58 AM
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.

I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.

Cheers


I have some code to share with you but the site is blocking my input.
Trying to contact with an admin about.
Thanks :-) Maybe you can post a link outside this forum

Ok, have a look at this and see if can help:
https://bitcointalksearch.org/topic/m.22615430

I don't use Nvoc's temp control.

Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware):
https://pastebin.com/mcqmt9CF

It is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi.
I just look forward to have a well configured rig and make it work stable instead of using wdog.
I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc).
Hi kk003,

This is awsome!! I will modify the code according the my setup.
As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct?
In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat:

Code:
nc -z -v -w5 $rigIP 22

(w5 is a timeout of 5 seconds)

Thanks again :-)

Since we are on RPi talks ...
How many rigs can be monitored and reboot/reset/hard reboot with one RPi?
What are the hardwares needed for multiple rig control?

I'm not much of a hardware guy but love to make a rig controller with RPi if its not too hard.
Pages:
Jump to: