Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1324. (Read 6590565 times)
May 11, 2016, 04:27:42 PM
Does "-etht" also work for stratum pool mode or just solo?
May 11, 2016, 04:03:32 PM
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.
Actually thats what I was asking about, so can I get a test version maybe ? Otherwise I need to discuss something with you, can you PM me please?
May 11, 2016, 03:59:28 PM
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.
May 11, 2016, 03:35:20 PM
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.
May 11, 2016, 03:17:38 PM
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.
Thanks a lot. Sorry i forgot about PM's. Yes it works.
May 11, 2016, 03:08:58 PM
Btw, can you see my other inquiry on solo mining?
Refer to https://bitcointalksearch.org/topic/m.14803962
Refer to https://bitcointalksearch.org/topic/m.14803962
1. You are correct.
2. In my tests I used
geth.exe --rpc --rpcaddr "192.168.0.2" --rpcport 8545
thanks - this is major thing in solo mining because we can solo mine without using the need of a proxy solution - if only I can turn back the clock 6 months
You could always solo mine without a proxy....
May 11, 2016, 02:56:35 PM
4.2b2 Working like this (Mining Hub/Sprnova):
EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal
wallet -epsw x -eworker
rig.worker -ethi 9 -dpool http://dcr.suprnova.cc:9111 -dwal
rig.worker -dpsw x -allpools 1
I had to change from -dpool stratum+tcp://dcr.suprnova.cc:2252
Which means stratum with DCR no longer works for that pool... I changed to stratum before because of the number of rejects.... Do you know what happened to the pool? my batch wont work for the 4.1 either so its not the miner.....
EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal
wallet -epsw x -eworker
rig.worker -ethi 9 -dpool http://dcr.suprnova.cc:9111 -dwal
rig.worker -dpsw x -allpools 1
I had to change from -dpool stratum+tcp://dcr.suprnova.cc:2252
Which means stratum with DCR no longer works for that pool... I changed to stratum before because of the number of rejects.... Do you know what happened to the pool? my batch wont work for the 4.1 either so its not the miner.....
Pool problem... SOLVED it is working again.... btw Which are the best pools?
Certainly not suprnova. I've been mining DCR there and I think I was getting around 40% less than I should. Mining calculator says I should get more than 5 DCR per day and I was getting 3 per day, several days. I moved to pool.mn in the morning and now in the evening I already mined 2.5, so the difference is evident.
May 11, 2016, 02:47:13 PM
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.
May 11, 2016, 01:11:32 PM
4.2b2 Working like this (Mining Hub/Sprnova):
EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal
wallet -epsw x -eworker
rig.worker -ethi 9 -dpool http://dcr.suprnova.cc:9111 -dwal
rig.worker -dpsw x -allpools 1
I had to change from -dpool stratum+tcp://dcr.suprnova.cc:2252
Which means stratum with DCR no longer works for that pool... I changed to stratum before because of the number of rejects.... Do you know what happened to the pool? my batch wont work for the 4.1 either so its not the miner.....
EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal
wallet -epsw x -eworker
rig.worker -ethi 9 -dpool http://dcr.suprnova.cc:9111 -dwal
rig.worker -dpsw x -allpools 1
I had to change from -dpool stratum+tcp://dcr.suprnova.cc:2252
Which means stratum with DCR no longer works for that pool... I changed to stratum before because of the number of rejects.... Do you know what happened to the pool? my batch wont work for the 4.1 either so its not the miner.....
Pool problem... SOLVED it is working again.... btw Which are the best pools?
May 11, 2016, 12:36:27 PM
Btw, can you see my other inquiry on solo mining?
Refer to https://bitcointalksearch.org/topic/m.14803962
Refer to https://bitcointalksearch.org/topic/m.14803962
1. You are correct.
2. In my tests I used
geth.exe --rpc --rpcaddr "192.168.0.2" --rpcport 8545
thanks - this is major thing in solo mining because we can solo mine without using the need of a proxy solution - if only I can turn back the clock 6 months
May 11, 2016, 12:23:42 PM
Claymore, you told some time ago that you planing implement json based remote monitoring feature for you miner, how things are going ?
May 11, 2016, 11:23:48 AM
Btw, can you see my other inquiry on solo mining?
Refer to https://bitcointalksearch.org/topic/m.14803962
Refer to https://bitcointalksearch.org/topic/m.14803962
1. You are correct.
2. In my tests I used
geth.exe --rpc --rpcaddr "192.168.0.2" --rpcport 8545
May 11, 2016, 11:09:14 AM
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.
Pool failover works fine.
DCR was giving "job timeout" error messages, but this was clarified with zpool OP upgrading the DCR wallet, so in fact, no issue with v4.2.
So all is good. Thanks for the great work in this miner.
Btw, can you see my other inquiry on solo mining?
Refer to https://bitcointalksearch.org/topic/m.14803962
May 11, 2016, 11:05:42 AM
asia1.ethpool.org was DDOS attacked - as per pool OP's message in Ethereum forum - their us and eu nodes were ok.
May 11, 2016, 10:48:33 AM
dcr.Maxminers.net seems not been working for dual mining mode for the recent 2 days.
Anyone else?
Eth mining works fine, but DCR keeps getting 0 Mhash and this 'DCR: Job timeout, disconnect, retry in 20 sec...'
Anyone else?
Eth mining works fine, but DCR keeps getting 0 Mhash and this 'DCR: Job timeout, disconnect, retry in 20 sec...'
May 11, 2016, 10:37:02 AM
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.
May 11, 2016, 10:36:52 AM
BTW, I just updated zpool.ca DCR wallet to 0.1.3 this morning, so some errors may have been seen during this. Back and running now.
Cheers
Cheers
Ahhh.... this makes sense now, what has happened in my case below.
But all is well, and back to normal now.
May 11, 2016, 10:35:47 AM
Is this the best miner for mining ether only? Im not concerned in mining DCR. I have been using this for the last few days on ethpool but i just wanted to make sure this is the best option for single miner.
CDMv42 a startum compliant ETH miner like qtminer - so it is I think the best there is out there, complete with failover, overclocking etc. Even qtminer doesn't have these features.
The other miner like ethminer is not Stratum compliant and still use a "get work from server" method, which is lame - you will be bound to lose $$$ this way.
In order to fix this, many have put a proxy solution so that many workers can hash into a single proxy server into the ETH pool, keeping hash steady...
For CDMv42, we dont need any proxy because the miner is Stratum compliant and will work well with Stratum based ETH pools.
In v42, even the solo mining feature did not need any proxy solution, as it mines directly into Geth, which is fantastic because it direct and does not create any delays.
Others feel free to comment, the above are strictly my opinion only.
May 11, 2016, 10:33:41 AM
BTW, I just updated zpool.ca DCR wallet to 0.1.3 this morning, so some errors may have been seen during this. Back and running now.
Cheers
Cheers
May 11, 2016, 10:26:01 AM
asia1.ethpool.org is now down, and I see the failover in action.
I set the failovers as follows:
POOL: us1.ethpool.org.......
POOL: asia1.ethpool.org.......
POOL: us2.ethpool.org.......
POOL: asia1.ethpool.org.......
POOL: eu1.ethpool.org.......
POOL: asia1.ethpool.org.......
And... DCR is at zpool and yiimp (failover)
After 20 seconds... it retries main eth pool
After 2 attempts.... failover kicks in and connects to us1.ethpool.org successfully.
At this stage, DCR is connected to zpool still and is authorised but sending "Job timeout, disconnect, retry in 20 secs)
This will go on further with ETH still good at us1 node, DCR mining does not failover though, because it can connect with zpool and get authorization.
Right after authorization, error msg "Job timeout, disconnect, retry in 20 secs".
At this point, ETH mining is business as usual in the failover pool.
Claymore, any advise?
Running zpool DCR stand-alone is OK without issues.
POSTNOTES: After about 30 minutes, DCR mining is now ok. But ETH mining is still going strong at first failover node. It looks like DCR mining at zpool -- self-corrected its job submission timing, perhaps...
I set the failovers as follows:
POOL: us1.ethpool.org.......
POOL: asia1.ethpool.org.......
POOL: us2.ethpool.org.......
POOL: asia1.ethpool.org.......
POOL: eu1.ethpool.org.......
POOL: asia1.ethpool.org.......
And... DCR is at zpool and yiimp (failover)
After 20 seconds... it retries main eth pool
After 2 attempts.... failover kicks in and connects to us1.ethpool.org successfully.
At this stage, DCR is connected to zpool still and is authorised but sending "Job timeout, disconnect, retry in 20 secs)
This will go on further with ETH still good at us1 node, DCR mining does not failover though, because it can connect with zpool and get authorization.
Right after authorization, error msg "Job timeout, disconnect, retry in 20 secs".
At this point, ETH mining is business as usual in the failover pool.
Claymore, any advise?
Running zpool DCR stand-alone is OK without issues.
POSTNOTES: After about 30 minutes, DCR mining is now ok. But ETH mining is still going strong at first failover node. It looks like DCR mining at zpool -- self-corrected its job submission timing, perhaps...
asia1.ethpool.org is now back online.
I rebooted all my rigs for safe measure, although CDMv42, successfully went back to main pool.
Everything is back to normal except for one weird thing which its my first time experiencing it.
When the usual bootup sequence is done in CDM.... nearly a screen full of DCR accepted share appeared on screen!
After that, it seems back to normal per like before asia1.ethpool.org went down about an ahour ago.
Could this be linked with the previous message from zpool "Job timeout, disconnect, retry in 20 secs", perhaps submitted hash was still sent to zpool but it can't resend acknowledgement back because it's at failover mode? Maybe this is a Stratum feature to accept past residual shares by the miner, I am not sure.
Claymore, any advise?
Jump to: