Quote from: Nipar on October 16, 2019, 02:39:22 PM

@jsheets1970 from mining the previous method I have multiple copies of my wallet running. some on linux, some on Windows 10.

For those getting errors when running the external miner please be aware that all the wrinkles are not yet ironed out.

This is a normal message if you forgot to unlock your wallet for mining OR your abnweight (minimum 125,000 abnweight) is too low
and the miner is waiting for it to reach the minimum limit of 125k abnweight again:

Code:

json_rpc_call failed, retry after 30 seconds
BBP Core Mining Error: Wallet Locked/ABN Required

you will also get this one and a few others that "fix" themselves:

Code:

[2019-10-15 21:06:09] HTTP request failed: Send failure: Broken pipe

while this one is a mystery to me, I am sure that it will be looked into and resolved soon:
(This is what I found while leaving the external miner running overnight with no abnweight. However it did seem to recover at one point only to error out again later.)

Code:

KJV Loaded
Using bbpminer version 1004

Erroring out

Erroring out

Erroring out

Erroring out

Erroring out

It also seems the external miner could use a "standby" type of connection/message as when the abnweight is too low it keeps thinking the connection to the wallet died and makes new connections every few seconds.

So I did find one with Linux miner and Linux wallet so I am sure that is working well.

Sunk made a great point about AVX/AVX2.. We definitely do not want to rule out the people that might have older machines that do not support AVX2.. I believe other miners have handled this issue as I believe, and I might be mistaken, some AMD chips do not support AVX2