Not long because some cards don't work and therefore watchdog stops the miner. Add "-wd 0" to your command line to ignore failed cards as I told you already: https://bitcointalk.org/index.php?topic=1433925.msg14837013#msg14837013Then when you confirm that it works, use "-di" option to select working cards and you can use non-working cards to mine something else if you cannot make all cards work. Have you tried it? It seems no, instead you created several threads to discuss your problem. |
|
|
|
Claymore could you pleeeease help me?
Miner cannot create buffer on GPU. I cannot help you with this problem, it seems you cannot use the miner on your hardware. But it worked for 5 of the 6 cards. It created the buffer and worked but then got an error. When it restarts it can create the DAG only on 4 of the 6 cards - and crashes again. But between the crashes it seems like it's working fine for the cards where the dag was created. So if it would not work at all then why does it work on some of the cards for some time? If you want to use miner on some cards that work - specify "-di" option, check readme for details. And/or if you don't want to stop miner if it found GPU error (like buffer allocation error in your screenshot) - specify "-wd 0" option. |
|
|
|
2. Some pools don't require worker, but if I remove WORKER option then some people will have problems if they change the pool name and will not know about WORKER option.
For dwarfpool WORKER is not necessary because if you use it you will not see hashrate on pool. Instead, add workername to the wallet address as dwarfpool recommends WALLET: 0x...../YourWorkerName.
Actually, WORKER option may be in place and does not break hashrate reporting on DwarfPool. But WALLET: 0x..... /YourWorkerName is REQUIRED for that. Probably you are right, I just did not try to specify worker in both WALLET and WORKER, it's senseless for me. |
|
|
|
Claymore could you pleeeease help me?
Miner cannot create buffer on GPU. I cannot help you with this problem, it seems you cannot use the miner on your hardware. |
|
|
|
Claymore, I think, there is a bug in the config reading section.
In file epools.txt
If I don't put the space symbol between WORKER: and worker name, it always sends
14:28:22:803 b88 send: {"id":4,"method":"eth_submitWork"...}
with no worker name inside.
If I add the space symbol, everything's fine:
14:21:34:911 c8c send: {"worker":"rig08","id":4,"method":"eth_submitWork"...}
I would also recommend to change the example config a little. Put in the epools.txt
WORKER: YourWorkerName,
instead of confusing
WORKER: ,
And, specially for dwarf:
# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: YourWorkerName, WORKER: YourWorkerName, ESM: 0, ALLPOOLS: 0
I mean that you have to send the worker name in the PSW field to see it on the stats page of dwarf
1. It is not a bug, space is a required character. 2. Some pools don't require worker, but if I remove WORKER option then some people will have problems if they change the pool name and will not know about WORKER option. For dwarfpool WORKER is not necessary because if you use it you will not see hashrate on pool. Instead, add workername to the wallet address as dwarfpool recommends WALLET: 0x...../YourWorkerName. 3. Default epools.txt has no this line for dwarfpool: POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: YourWorkerName, WORKER: YourWorkerName, ESM: 0, ALLPOOLS: 0 So it's your line, not from default epools.txt. |
|
|
|
Mr. Claymore, when I see this n the log, I have no idea, what is this 13:52:24:431 15d8 ETH: put share nonce 563f731acff2c300
13:52:24:447 15d8 ETH round found 1 shares
13:52:24:463 fac ETH: 05/13/16-13:52:24 - SHARE FOUND - (GPU 0)
13:52:24:463 fac send: {"worker":"rig2 ","id":4,"method":"eth_submitWork",...}
13:52:24:530 fac got 18 bytes
13:52:24:530 fac buf: An error occurred
13:52:24:530 fac buf: Anerroroccurred When the answer from the pool is OK, it shows JSON data. But in this case there is no data at all. What are those 18 bytes? I even can not provide you with the data. Background: Mining on dwarf stratum port 8008. epools.txt via 4.2b2: POOL: private_server.dwarfpool.com:8008, WALLET: 0x8f61c9561..., PSW:rig2, WORKER: rig2 , ESM: 0, ALLPOOLS: 0
Pool returned "An error occurred" string instead of error in JSON format. You can ask pool owner why his pool does such thing. |
|
|
|
ok setting that variable doesnt seem to effect the time for http requests it stays at 200. Also noticed that when i first start the program its showing me as etha 1 for slow cards so i defined it in the command line to etha 0 and it made no diff in speed so i changed it to etha 1 and it slowed me down about 8 % or so across all the cards.. So i think there may be a glitch in hte way CDM 4.2 beta displays the etha algo when its not defined in the command line(auto mode).. Its selecting the correct mode just displaying it incorrectly on the output. Any advice be appreciated. "C:\Users\Doug\Desktop\Claymore's Dual Ethereum+Decred AMD GPU Miner v4.2 Beta\EthDcrMiner64.exe" -etht 500 -epool http://x.x.x.x:8545If miner fails to connect it waits for 20 seconds before next attempt. I can add parameter to wait less, but it is not normal mode anyway, you will lose mining speed if you have such problems with connection. Issue with "-etha" - miner shows it correctly. Check again, the problem must be on your side. If you still think that the problem is in miner, PM me two logs - without "-etha" option and with "-etha" which cause slow down. |
|
|
|
Claymore can you mine to miningpoolhub with only -esm 0 and the 20536 port? That port corresponds to dwarf proxy implementation. I tried to mine to the 20535 port using -esm 2 and it didn't work. That's the coinotron proxy implementation. Curious, as I've seen the miningpoolhub op say that's the best way to connect to his pool.
Also your example in the first post regarding miningpoolhub does not have the -allpools 1 parameter
This works for me: EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal 0x...walletaddress.... -eworker YOURLOGIN.YOURWORKERNAME -epsw x -allpools 1 But you must create same worker on this pool, and perhaps specify same wallet address in account settings on pool (I don't remember). About missed "-allpools 1": you are correct, I updated OP. Yes that port works for me too. I was curious why port 20535 and -esm2 doesn't work. Because pool doesn't understand wallet as username and requires login.worker style. It works for me: EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20535 -ewal YOURLOGIN.YOURWORKERNAME -epsw x -esm 2 -allpools 1 |
|
|
|
He answered this. https://i.snag.gy/bmDdnu.jpgTranslation of bottom message. Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers In fact, I saw that dwarfpool had problems for a couple of days. You can see all miner actions in log files. If it cannot connect, cannot get job, or share accepting time >1sec - it is not a miner problem if everything is working on other pools. Some people just put different dwarfpool severs in the failover list and when entire dwarfpool is down they ask why miner does not work. Excellent logic  If dwarfpool admin think that the problem is in miner we can talk about it in details, I'd like to see some proofs. May be he really knows something that I missed, I'm ready to fix it. But right now I have only proofs about recent problems of dwarfpool. You can check how failover/reconnection works easily - disable network connection in Windows or plug off the network cable. Does this address -epool eth-ru.dwarfpool.com:8008 means that im mining on dwarfpool with proxy? My miner does not require proxy, with these settings you mine on dwarfpool directly by using Stratum. Check "ADDITIONAL INFORMATION" section of first message of this thread for more details. |
|
|
|
He answered this. https://i.snag.gy/bmDdnu.jpgTranslation of bottom message. Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers In fact, I saw that dwarfpool had problems for a couple of days. You can see all miner actions in log files. If it cannot connect, cannot get job, or share accepting time >1sec - it is not a miner problem if everything is working on other pools. Some people just put different dwarfpool severs in the failover list and when entire dwarfpool is down they ask why miner does not work. Excellent logic If dwarfpool admin think that the problem is in miner we can talk about it in details, I'd like to see some proofs. May be he really knows something that I missed, I'm ready to fix it. But right now I have only proofs about recent problems of dwarfpool. You can check how failover/reconnection works easily - disable network connection in Windows or plug off the network cable. |
|
|
|
Is Claymore working with dwarf through stratum?
What settings should it be?
It's a good idea to read first post of this thread, it has a lot of samples for many pools. Also Dwarf Admin said that Claymore are working bad with failover servers.
Can you please send a link to this Atrides's message? I'd like to know a bit more details. |
|
|
|
Claymore can you mine to miningpoolhub with only -esm 0 and the 20536 port? That port corresponds to dwarf proxy implementation. I tried to mine to the 20535 port using -esm 2 and it didn't work. That's the coinotron proxy implementation. Curious, as I've seen the miningpoolhub op say that's the best way to connect to his pool.
Also your example in the first post regarding miningpoolhub does not have the -allpools 1 parameter
This works for me: EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal 0x...walletaddress.... -eworker YOURLOGIN.YOURWORKERNAME -epsw x -allpools 1 But you must create same worker on this pool, and perhaps specify same wallet address in account settings on pool (I don't remember). About missed "-allpools 1": you are correct, I updated OP. |
|
|
|
2. You can get less data traffic and reduce pool load.
If you have 20 rigs in remote site working thru 3G connection it could be vital Ok, you can use eth-proxy for now, v4.2 can work with proxies, though I did not test it much. I still think that using proxy can cause some problems and additional delays, but probably in some cases it can be the only solution. |
|
|
|
Does "-etht" also work for stratum pool mode or just solo?
From readme: ... -etht Time period between Ethereum HTTP requests for new job in solo mode, in milliseconds. Default value is 200ms. ... I think it is clear that it is for solo mode only. |
|
|
|
Claymore, you told some time ago that you planing implement json based remote monitoring feature for you miner, how things are going ?
I PM-ed you a build that sends hashrate in solo mode, does it work for you? I think monitoring will be available in next version, it will be ready in a few days. What about the Stratum-Stratum proxy you said you will have in couple of days? this is the only thing putting us off using Claymore. BTW: I would also appreciate if you have Linux builds. I decided not to do a proxy, at least not right now. Proxy has two advantages: 1. You can easiliy change the pool list, it will be applied for all rigs. Option "send pool list to all rigs" will be available in the monitoring utility that I will release in a few days. 2. You can get less data traffic and reduce pool load. But you will not see rigs on pool, only one proxy will be showed there. Data size is not important for 99% of people, but everyone wants to see detailed stats on pool. Also proxy must support all stratum versions and convert them into some one stratum version that miners will use. Possible but requires time to implement. So I decided to release an utility that can monitor miners and manage their settings, but it will not be a proxy, at least first version. You can argue, I'm ready for feedbacks. |
|
|
|
Claymore, you told some time ago that you planing implement json based remote monitoring feature for you miner, how things are going ?
I PM-ed you a build that sends hashrate in solo mode, does it work for you? I think monitoring will be available in next version, it will be ready in a few days. |
|
|
|
1. You are correct. 2. In my tests I used geth.exe --rpc --rpcaddr "192.168.0.2" --rpcport 8545 |
|
|
|
Claymore, any advise?
I don't understand the problem from your explanations. Do you think failover does not work? PM me the log and I will check it. |
|
|
|
FAILOVER
Use "epools.txt" and "dpools.txt" files to specify additional pools. These files have text format, one pool per line. Every pool has 3 connection attempts.
If the first character of a line is ";" or "#", this line will be ignored.
Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list.
If no pool was specified in the command line then first pool in the pools list is main pool. Hi, Is it possible to change this 30 minutes for Failover? I will add an appropriate option in next update, it will allow you to change this time or cancel main pool at all. |
|
|
|
Why DCR hashing fail, if ETH-Pool is down?
Because it is senseless not to mine Ethereum if you use this miner. This is Ethereum miner and plus Decred optionally, not vice versa. Just use failover to change eth pool. |
|
|
|
|
Show Posts
