Miner doesn't like to share

[painting]

@keaton_hiveon finally got bzminer to save all the logs. All 64 of them

It can’t be a problem with my set up, since it is tuned. Either hive isn’t passing it on, or bz ignores it.

bzminer *N* *A* User Config"clear_log_file": false "log_file_verbosity": 3 "hung_gpu_restart_bzminer": true "oc_lock_memory_clock": [810]

Also all the flightsheets have Disable Gpus0-2,4-8

The previous log showed this:

***************************
**                       **
**   BzMiner v12.0.2b1   **
**                       **
***************************


Loading settings from config.txt
Language: English
Working Directory: /hive/miners/bzminer/12.0.2
Logging to: /var/log/miner/bzminer/miner_1666484754.log
<Debug> Cuda runtime version: 11080
<Debug> arch: 35
<Debug> arch: 37
<Debug> arch: 50
<Debug> arch: 52
<Debug> arch: 53
<Debug> arch: 60
<Debug> arch: 61
<Debug> arch: 62
<Debug> arch: 70
<Debug> arch: 72
<Debug> arch: 75
<Debug> arch: 80
<Debug> arch: 86
<Debug> arch: 87
<Debug> arch: 89
<Debug> arch: 90
<Debug> Cuda runtime compiler version: 11.8
<Debug> Creating a NVIDIA device monitor for GPU: 6:0
<Debug> Could not find display name for device: 248710de:248710de
<Debug> Creating a NVIDIA device monitor for GPU: 7:0
<Debug> Could not find display name for device: 248710de:263019da
<Debug> Creating a NVIDIA device monitor for GPU: 8:0
<Debug> Could not find display name for device: 250410de:250410de
<Debug> Creating a NVIDIA device monitor for GPU: 9:0
<Debug> Could not find display name for device: 248810de:861719da
<Debug> Creating a NVIDIA device monitor for GPU: 11:0
<Debug> Could not find display name for device: 248910de:40771458
<Debug> Creating a NVIDIA device monitor for GPU: 12:0
<Debug> Could not find display name for device: 248910de:39721462
<Debug> Creating a NVIDIA device monitor for GPU: 13:0
<Debug> Could not find display name for device: 248910de:163019da
<Debug> Creating a NVIDIA device monitor for GPU: 16:0
<Debug> Could not find display name for device: 248910de:405b1458
<Debug> Creating an AMD device monitor for GPU: 5:0
<Debug> Could not find display name for device: 73df1002:e4451da2
GPU 8:0: LHR Detected, LHR unlock engaged! Stability set to: 100
Cuda: 11.6
Nvidia Driver: 510.68.02
AMD Driver: 3180.7 (PAL,LC)

 ----------------------------------------------- devices ---------------------------------------------
 | #    | name                      | free    | total   | core    | mem       | fan | pwr  | temp    | 
 | 5:0  | AMD Radeon RX 6700 XT     | 11.97gb | 11.97gb | 1.45ghz | 1.07ghz   | 21% | 21w  | 40C/41C |
 | 6:0  | NVIDIA GeForce RTX 3060   | 11.66gb | 11.77gb | 1.35ghz | 8.30ghz   | 47% | 18w  | 44C     |
 | 7:0  | NVIDIA GeForce RTX 3060   | 11.66gb | 11.77gb | 1.78ghz | 7.50ghz   | 53% | 19w  | 49C     |
 | 8:0  | NVIDIA GeForce RTX 3060   | 11.66gb | 11.77gb | 1.78ghz | 810.00mhz | 30% | 16w  | 43C     |
 | 9:0  | NVIDIA GeForce RTX 3070   | 7.64gb  | 7.80gb  | 1.29ghz | 7.80ghz   | 62% | 15w  | 47C     |
 | 11:0 | NVIDIA GeForce RTX 3060 T | 7.66gb  | 7.79gb  | 1.41ghz | 7.90ghz   | 63% | 18w  | 53C     |
 | 12:0 | NVIDIA GeForce RTX 3060 T | 7.66gb  | 7.79gb  | 1.41ghz | 7.20ghz   | 41% | 22w  | 40C     |
 | 13:0 | NVIDIA GeForce RTX 3060 T | 7.66gb  | 7.79gb  | 1.41ghz | 7.60ghz   | 37% | 20w  | 49C     |
 | 16:0 | NVIDIA GeForce RTX 3060 T | 7.66gb  | 7.79gb  | 1.41ghz | 7.90ghz   | 62% | 20w  | 52C     |
 |      |                           |         |         |         |           |     | 169w |         |
 10-22 19:25:56 ---------------------------------------------------------------------------- v12.0.2b1

<Warn> GPU 11:0: disabled. Set start_mining to true to enable.
<Warn> GPU 12:0: disabled. Set start_mining to true to enable.
<Warn> GPU 13:0: disabled. Set start_mining to true to enable.
<Warn> GPU 16:0: disabled. Set start_mining to true to enable.
<Warn> GPU 5:0: disabled. Set start_mining to true to enable.
<Warn> GPU 6:0: disabled. Set start_mining to true to enable.
<Warn> GPU 7:0: disabled. Set start_mining to true to enable.
<Warn> GPU 9:0: disabled. Set start_mining to true to enable.
Connecting to stratum+tcp://us.acc-pool.pw:16061 as rig with wallet:
kaspa:wallet
HTTP API Listening on 127.0.0.1:4014
<Debug> GPU kaspa 8:0: Work thread starting
GPU 8:0: OC has been set for kaspa
GPU 8:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
<Debug> Received new kaspa job
…
 ----------------------------------------------- devices ---------------------------------------------
 | #    | name                     | free    | total   | core    | mem       | fan | pwr   | temp    | 
 | 5:0  | AMD Radeon RX 6700 XT    | 10.54gb | 11.97gb | 1.45ghz | 1.07ghz   | 28% | 85w   | 45C/49C |
 | 6:0  | NVIDIA GeForce RTX 3060  | 10.32gb | 11.77gb | 1.35ghz | 8.30ghz   | 58% | 122w  | 58C     |
 | 7:0  | NVIDIA GeForce RTX 3060  | 7.81gb  | 11.77gb | 1.62ghz | 7.50ghz   | 56% | 104w  | 60C     |
 | 8:0  | NVIDIA GeForce RTX 3060  | 11.66gb | 11.77gb | 1.93ghz | 810.00mhz | 30% | 99w   | 59C     |
 | 9:0  | NVIDIA GeForce RTX 3070  | 6.36gb  | 7.80gb  | 1.29ghz | 7.80ghz   | 57% | 115w  | 57C     |
 | 11:0 | NVIDIA GeForce RTX 3060  | 6.41gb  | 7.79gb  | 1.41ghz | 7.90ghz   | 72% | 123w  | 59C     |
 | 12:0 | NVIDIA GeForce RTX 3060  | 6.41gb  | 7.79gb  | 1.41ghz | 7.20ghz   | 40% | 144w  | 52C     |
 | 13:0 | NVIDIA GeForce RTX 3060  | 6.41gb  | 7.79gb  | 1.41ghz | 7.60ghz   | 36% | 124w  | 54C     |
 | 16:0 | NVIDIA GeForce RTX 3060  | 6.41gb  | 7.79gb  | 1.41ghz | 7.90ghz   | 68% | 121w  | 60C     |
 |      |                          |         |         |         |           |     | 1037w |         |
 10-22 19:27:42 ---------------------------------------------------------------------------- v12.0.2b1

 --------------------------------- kaspa - us.acc-pool.pw:16061 - rig --------------------------------
 | #    | uptime | a/r/i | cfg   | tbs    | eff      | pool hr  | miner hr | status                  | 
 | 8:0  | 0:0:1  | 4/-/- | i27cu | 17.50s | 3.60mh/w | 810.38mh | 352.78mh | Mining (LHR)            |
 |      |        |       |       |        |          |          |          |                         |
 | smry | 0:0:1  | 4/-/- |       | 17.50s | 3.60mh/w | 810.38mh | 352.78mh | diff:     21.48gh       |
 |      |        |       |       |        |          |          |          | latency:  59ms          |
 |      |        |       |       |        |          |          |          | est. tbs: 1.01m         |
 10-22 19:27:42 ---------------------------------------------------------------------------- v12.0.2b1

<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 34
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 35
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 36
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 37
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 38
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 39
<Debug> Received new kaspa job
<Debug> GPU 8:0: Starting kaspa work on job 3a
<Debug> Received new kaspa job

The next time bz started, it grabbed all the gpus for ming

***************************
**                       **
**   BzMiner v12.0.2b1   **
**                       **
***************************


Loading settings from config.txt
Language: English
Working Directory: /hive/miners/bzminer/12.0.2
Logging to: /var/log/miner/bzminer/miner_1666484944.log
<Debug> Cuda runtime version: 11080
<Debug> arch: 35
<Debug> arch: 37
<Debug> arch: 50
<Debug> arch: 52
<Debug> arch: 53
<Debug> arch: 60
<Debug> arch: 61
<Debug> arch: 62
<Debug> arch: 70
<Debug> arch: 72
<Debug> arch: 75
<Debug> arch: 80
<Debug> arch: 86
<Debug> arch: 87
<Debug> arch: 89
<Debug> arch: 90
<Debug> Cuda runtime compiler version: 11.8
<Warn> Failed to get X11 display. Nvidia Memory, core, and fan oc's will not be available. Try setting 'x_display' option.
<Debug> Failed to load NvCTRL. Memory, core, and fan oc's will not be available
<Debug> Creating a NVIDIA device monitor for GPU: 6:0
<Debug> Could not find display name for device: 248710de:248710de
<Debug> Creating a NVIDIA device monitor for GPU: 7:0
<Debug> Could not find display name for device: 248710de:263019da
<Debug> Creating a NVIDIA device monitor for GPU: 8:0
<Debug> Could not find display name for device: 250410de:250410de
<Debug> Creating a NVIDIA device monitor for GPU: 9:0
<Debug> Could not find display name for device: 248810de:861719da
<Debug> Creating a NVIDIA device monitor for GPU: 11:0
<Debug> Could not find display name for device: 248910de:40771458
<Debug> Creating a NVIDIA device monitor for GPU: 12:0
<Debug> Could not find display name for device: 248910de:39721462
<Debug> Creating a NVIDIA device monitor for GPU: 13:0
<Debug> Could not find display name for device: 248910de:163019da
<Debug> Creating a NVIDIA device monitor for GPU: 16:0
<Debug> Could not find display name for device: 248910de:405b1458
GPU 6:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 7:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 8:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 9:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 11:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 12:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 13:0: LHR Detected, LHR unlock engaged! Stability set to: 100
GPU 16:0: LHR Detected, LHR unlock engaged! Stability set to: 100
Cuda: 11.6
Nvidia Driver: 510.68.02

 ----------------------------------------------- devices ---------------------------------------------
 | #    | name                           | free    | total   | core    | mem     | fan | pwr  | temp | 
 | 6:0  | NVIDIA GeForce RTX 3060        | 11.57gb | 11.77gb | 1.87ghz | 7.50ghz | 0%  | 36w  | 41C  |
 | 7:0  | NVIDIA GeForce RTX 3060        | 11.57gb | 11.77gb | 1.99ghz | 7.50ghz | 0%  | 47w  | 44C  |
 | 8:0  | NVIDIA GeForce RTX 3060        | 11.57gb | 11.77gb | 1.91ghz | 7.50ghz | 0%  | 35w  | 41C  |
 | 9:0  | NVIDIA GeForce RTX 3070        | 7.50gb  | 7.80gb  | 1.86ghz | 7.00ghz | 0%  | 38w  | 49C  |
 | 11:0 | NVIDIA GeForce RTX 3060 Ti     | 7.54gb  | 7.79gb  | 1.95ghz | 7.00ghz | 52% | 43w  | 53C  |
 | 12:0 | NVIDIA GeForce RTX 3060 Ti     | 7.54gb  | 7.79gb  | 1.95ghz | 7.00ghz | 0%  | 45w  | 34C  |
 | 13:0 | NVIDIA GeForce RTX 3060 Ti     | 7.54gb  | 7.79gb  | 1.95ghz | 7.00ghz | 36% | 42w  | 39C  |
 | 16:0 | NVIDIA GeForce RTX 3060 Ti     | 7.54gb  | 7.79gb  | 2.04ghz | 7.00ghz | 71% | 43w  | 54C  |
 |      |                                |         |         |         |         |     | 329w |      |
 10-22 19:29:16 ---------------------------------------------------------------------------- v12.0.2b1

Connecting to stratum+tcp://us.acc-pool.pw:16061 as rig with wallet:
kaspa:wallet
<Debug> GPU kaspa 12:0: Work thread starting
<Debug> GPU kaspa 11:0: Work thread starting
<Debug> GPU kaspa 16:0: Work thread starting
<Debug> GPU kaspa 7:0: Work thread starting
<Debug> GPU kaspa 13:0: Work thread starting
<Debug> GPU kaspa 9:0: Work thread starting
<Debug> GPU kaspa 6:0: Work thread starting
<Debug> GPU kaspa 8:0: Work thread starting
HTTP API Listening on 127.0.0.1:4014
<Debug> Unable to resolve us.acc-pool.pw - Host not found (non-authoritative), try again later
<Warn> Unable to resolve us.acc-pool.pw
<Debug> Unable to connect to pool.
GPU 11:0: OC has been set for kaspa
GPU 9:0: OC has been set for kaspa
GPU 6:0: OC has been set for kaspa
GPU 12:0: OC has been set for kaspa
GPU 16:0: OC has been set for kaspa
GPU 8:0: OC has been set for kaspa
GPU 7:0: OC has been set for kaspa
GPU 13:0: OC has been set for kaspa
GPU 11:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 9:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 6:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 12:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 16:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 8:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 7:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
GPU 13:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
Reconnecting to stratum+tcp://us.acc-pool.pw:16061 in 3 seconds...

[keaton_hiveon]

why did bzminer restart?

[painting]

would it make a difference, for bz to go haywire?

The last log where bz worked correctly doesn’t state why. Think bz doesn’t show why it terminated. However, it could have been autoswitch changing currency. Did took a bit over a minute between runs. Also there could had been a network issue. The next run seems to had network problems, but that shouldn’t had caused it to grab all the gpus

last lines of the good run

 <Debug> GPU 8:0: Starting kaspa work on job 3a
 <Debug> Received new kaspa job

[keaton_hiveon]

i would try to figure out why its crashing and resolve that. alternatively you can try another miner and see if the issue persists.

[painting]

would love to try another lol, but not an option. I’m already using all the other possible miners Maybe a custom one

Usually I noticed it grabs all the cards when it restarts. I need to shutdown and do a cold boot. I have noticed something strange during the boot process when it will fail. Haven’t had a chance to grab it, maybe next time syslog doesn’t seem rotate

[keaton_hiveon]

miniz is better for flux anyway. try miniz and lolminer

[painting]

thought lolminer hashes better for flux. Did you noticed, I’m doing kaspa?

[keaton_hiveon]

yeah, and lolminer is better for kaspa as well, so win win. miniz for flux and lol for kaspa. lolminer can also lock mem at 810.

[painting]

as I said, I am already using all the other options (gminer, lolminer, trm). Currently lolminer is mining something else, so I can’t use it or any other miner bz seems to be the only option.

So my best choice is get bz to behave nicely

[keaton_hiveon]

youre using bzminer for kaspa and lolminer for flux now right?

and youre not using miniz for anything?

[painting]

This is one of the flight sheets, most of the other 12 look similar. If I’m not using lolminer for the main one, then I use it for flux

[keaton_hiveon]

maybe simplify your flight sheet/miner/pool selection and see if its more stable.

[painting]

lol

if I take kaspa out, it works fine. However then there wouldn’t be a need to fix the problem

Nonetheless, I had used bzminer on other simpler flight sheet, and it also misbehaved. I had been trying to stay away from bz, but have no choice now

[painting]

also noticed something strange. bz seems to be mining to a weird address. Been mining to this using my pool, and it isn’t getting authorized. Could 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v be the wallet for the miner’s fee? Though it isn’t a kaspa address

It only happens with bz and no other miner. So not sure it is malware

<Warn> Kaspa wallet is: 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v.2842067                                                                   
<Warn> Kaspa wallets should start with 'kaspa:'                                                                                      
<Warn> GPU 9:0: disabled. Set start_mining to true to enable.                                                                        
Connecting to stratum+tcp://us.acc-pool.pw:16061 as rig with wallet:                                                                 
34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v.2842067                                                                                           
<Debug> GPU kaspa 8:0: Work thread starting
GPU 8:0: OC has been set for kaspa                                                                                                   
GPU 8:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]                                                                      
<Debug> Error on stratum+tcp://us.acc-pool.pw:16061: Connection reset by peer                                                        
Connected to stratum+tcp://us.acc-pool.pw:16061 using stratum as rig                                                                 
kaspa dev fee: 1.0%                                                                                                                  
Reconnecting to stratum+tcp://us.acc-pool.pw:16061 in 3 seconds...                                                                   
<Debug> Error shutting down pool connection: shutdown: Transport endpoint is not connected [system:107]                              
<Debug> GPU 8:0: stop work requested                                                                                                 
<Debug> GPU 8:0: Work thread closing                                                                                                 
<Debug> Destroying pool connection to stratum+tcp://us.acc-pool.pw:16061                                                             
<Debug> GPU kaspa 8:0: Work thread starting                                                                                          
<Debug> Received HTTP GetHiveStatus                                                                                                  

[keaton_hiveon]

Post your flight sheet

[painting]

Finally grabbed some screenshots of when it crashes. Strangely enough except for an obscure error, everything works! Finds the wireless card, connects flawlessly to the wifi network, and should have worked (and still waits for 2m). However, it is when this happens that bz misbehaves

Maybe you know how to fix an msr error? The linux kernel is disabling userspace writes to MSR in version 5.9

When this happens, bz takes over all the cards, and the rig crashes (wrong oc for the seized cards?). Somehow bz decides to lock all the memory at 810

@keaton_hiveon

Post your flight sheet

Not going to post 12 fs lol Would be great if there was a mass search and replace for fs! It is a pain to edit all fs when need to make a change

Zhash
nicehash
nicehash
Wallet Address my_wallet
Server  URLs zhash.auto.nicehash.com:9200
miniz NA
Url %URL%
Algo 144,5
Pass x
Template %WAL%.%WORKER_NAME%
User Config --pers auto -cd 3 4 5 6 7

RVN
mining-dutch
Configured in miner
Wallet Address my_wallet
teamredminer A
Tuned
User Config --kernel_vm_mode=RR --prog_hash_report -d 0
Url stratum+tcp://americas.kawpow.mining-dutch.nl:9985 stratum+tcp://kawpow.mining-dutch.nl:9985
Algo kawpow
Pass d=188
Template %WAL%.%WORKER_NAME%

RVN
mining-dutch
Configured in miner
Wallet Address my_wallet
gminer NA
Algo kawpow
Pass d=188
Port 9985 9985
Server americas.kawpow.mining-dutch.nl kawpow.mining-dutch.nl
Template %WAL%.%WORKER_NAME%
User Config --devices 1

FLUX
Flux - Zelcore
fluxpools
Wallet Address my_wallet
Server  URLs
us-flux.fluxpools.net:7001
eu-flux.fluxpools.net:7001
lolminer NA
Algo ZEL
Pass  x
Port %URL_PORT%
Server %URL_HOST%
Template %WAL%.%WORKER_NAME%
User Config --devices 2

KAS
kaspa
acc-pool
Wallet Address my_wallet
Server  URLs
us.acc-pool.pw:16061
ca.acc-pool.pw:16061
eu1.acc-pool.pw:16061
eu2.acc-pool.pw:16061
bzminer NA
Tuned
User Config "clear_log_file": false "log_file_verbosity": 3 "hung_gpu_restart_bzminer": true "oc_lock_memory_clock": [810]
Disable Gpus0-2,4-8
Tls 0
Url %URL%
Algo kaspa
Template %WAL%
User Config "oc_lock_memory_clock": [810] < overwritten
Disable Gpus0-2,4-8 < overwritten

EPIC
epic
Configured in miner
Wallet Address my_wallet
srbminer AC
Tuned
Url epic.ca.hashrate.to:4000 epic.hashrate.to:4000
Algo randomepic
Pass  x
Template  my_wallet
User Config --disable-gpu --cpu-threads 3 --keepalive true
Url stratum-na.rplant.xyz:7084 < overwritten 
Algo ghostrider < overwritten
Template %WAL% < overwritten


Autoswitch Zhash

Not shown buy my kaspa address isn’t 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v. Besides mine is properly formatted with a kaspa: prefix

[keaton_hiveon]

you can only run one flight sheet at a time, post that one. a screenshot is fine

[painting]

I posted the text of the fs above, but here is the image

[keaton_hiveon]

Since you censored it, What’s your nicehash wallet address? Is it the address that’s applied to kaspa on bz?

[painting]

@keaton_hiveon why would I do that? miniz is hashing to nicehash using the nicehash address wallet. All the others are mining using the correct wallet for each coin. Should I have mixed them up, it wouldn’t mine!

Even mentioned that the address for bz changed to an incorrect wallet. None of my wallets has 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v as a value. Not sure if this is the miner’s wallet or could be malware

You are missing the point, this is a problem happens only sometimes when the rig boots. Not sure that I have seen this at other times. Something goes wrong and bz tries to mine on all the cards. This causes some cards to double mine using bz and the other miners. After a couple of minutes, the rig crashes.

If this misstep doesn’t happen, then the rig mines correctly and bz uses only the assigned card. It is this that makes me think there might be a problem with hive that leads to this. bz might not be as stable as the other miners, but seems it is when hive launches bz.