Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1323. (Read 6590565 times)

member
Activity: 98
Merit: 10
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.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1




you mind telling me what servers you were on.. the us server sucks .. i was getting 10 second lags on the share submitting.. I finally went to eu server.. but even it was doing funny things last couple days,, Id say its not claymores miner.. it was def dwarf.. i have yet to be satisfied of what it reports i get in hash and what i got paid from their.. always about 10 % less than i calced..

Best Regards
d57heinz

edit ill dig thru my logs just to confirm.. One thing i really like about his miner.. It keeps a txt log off all output. Smiley

after when  ru server was offline it reconnected to eu server

POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us2.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-asia.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0



legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
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.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1




you mind telling me what servers you were on.. the us server sucks .. i was getting 10 second lags on the share submitting.. I finally went to eu server.. but even it was doing funny things last couple days,, Id say its not claymores miner.. it was def dwarf.. i have yet to be satisfied of what it reports i get in hash and what i got paid from there.. always about 10 % less than i calculated..

Best Regards
d57heinz

edit ill dig thru my logs just to confirm.. One thing i really like about his miner.. It keeps a txt log off all output. Smiley

this is when it started acting up.. I was getting shares found but dwarf wasnt reporting back to me that it was accepted.. Thats when i checked the site and noticed too that my numbers dropped way down on accepted shares.. Ill post in a few i have found many entries that show that it took well over 3 seconds for some shares to be accepted.. With a fast block coin thats unacceptable.


Code:
buf:

15:07:47:921 1858 ETH: put share nonce 283f0388114bb420
15:07:47:921 1858 ETH round found 1 shares
15:07:47:937 1860 ETH: 05/08/16-15:07:47 - SHARE FOUND - (GPU 3)
15:07:47:937 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x283f0388114bb420","0x3c4ca5983611feca62ee3a996a02026e765b5e6c25b50926ff704da67386eff6","0x02e67da788ad0bb1ef6c83f7a5f515df0cc7d68396b0111f99ae51dd660b1c95"]}


15:07:49:781 1420 em hbt: 0, fm hbt: 47,
15:07:49:781 1420 watchdog - thread 0, hb time 250
15:07:49:781 1420 watchdog - thread 1, hb time 47
15:07:49:781 1420 watchdog - thread 2, hb time 469
15:07:49:781 1420 watchdog - thread 3, hb time 219
15:07:49:781 1420 watchdog - thread 4, hb time 312
15:07:49:796 1420 watchdog - thread 5, hb time 109
15:07:49:796 1420 watchdog - thread 6, hb time 281
15:07:49:796 1420 watchdog - thread 7, hb time 94
15:07:50:374 1860 got 244 bytes
15:07:50:374 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:07:50:374 1860 parse packet: 243
15:07:50:374 1860 eth: job changed
15:07:50:374 1860 remove first packet 1
15:07:50:374 1860 new buf size: 1
15:07:50:390 1860 buf:

15:07:50:390 1860 ETH: 05/08/16-15:07:50 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:07:50:390 1860 ETH - Total Speed: 103.722 Mh/s, Total Shares: 3444, Rejected: 1, Time: 19:16
15:07:50:390 1860 ETH: GPU0 26.681 Mh/s, GPU1 17.502 Mh/s, GPU2 29.870 Mh/s, GPU3 29.668 Mh/s
15:07:50:453 1854 Job changed, drop current round
15:07:50:453 1850 Job changed, drop current round
15:07:50:484 185c Job changed, drop current round
15:07:50:484 1858 Job changed, drop current round
15:07:50:531 184c Job changed, drop current round
15:07:50:531 1844 Job changed, drop current round
15:07:50:531 1848 Job changed, drop current round
15:07:50:531 1840 Job changed, drop current round
15:07:57:000 1860 ETH: checking pool connection...
15:07:57:000 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:07:57:000 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x635ed8f", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:07:57:062 1860 got 244 bytes
15:07:57:062 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:07:57:062 1860 parse packet: 243
15:07:57:062 1860 eth: job is the same
15:07:57:062 1860 remove first packet 1
15:07:57:062 1860 new buf size: 1
15:07:57:078 1860 buf:

15:08:03:594 1850 ETH: put share nonce 21f4d9ec0b5985f0
15:08:03:594 1850 ETH round found 1 shares
15:08:03:609 1860 ETH: 05/08/16-15:08:03 - SHARE FOUND - (GPU 2)
15:08:03:609 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x21f4d9ec0b5985f0","0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0xfa43e0345bd961b323da81c592a087a669da347c992dbf0ca82e181f43c0e669"]}


15:08:04:641 1850 ETH: put share nonce 21f4d9ec0c768129
15:08:04:641 1850 ETH round found 1 shares
15:08:04:656 1860 ETH: 05/08/16-15:08:04 - SHARE FOUND - (GPU 2)
15:08:04:656 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x21f4d9ec0c768129","0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x4591c5dc863620673c369ad892924348e91a93ae2505a7e19eafd3de87ebb65b"]}


15:08:07:016 1860 ETH: checking pool connection...
15:08:07:016 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:07:016 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x636dca3", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:07:094 1860 got 244 bytes
15:08:07:094 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:07:094 1860 parse packet: 243
15:08:07:094 1860 eth: job is the same
15:08:07:094 1860 remove first packet 1
15:08:07:094 1860 new buf size: 1
15:08:07:094 1860 buf:

15:08:17:032 1860 ETH: checking pool connection...
15:08:17:032 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:17:032 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6376720", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:17:094 1860 got 244 bytes
15:08:17:094 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:17:094 1860 parse packet: 243
15:08:17:094 1860 eth: job is the same
15:08:17:094 1860 remove first packet 1
15:08:17:094 1860 new buf size: 1
15:08:17:094 1860 buf:

15:08:19:829 1420 em hbt: 16, fm hbt: 16,
15:08:19:829 1420 watchdog - thread 0, hb time 266
15:08:19:829 1420 watchdog - thread 1, hb time 63
15:08:19:829 1420 watchdog - thread 2, hb time 313
15:08:19:829 1420 watchdog - thread 3, hb time 78
15:08:19:829 1420 watchdog - thread 4, hb time 328
15:08:19:829 1420 watchdog - thread 5, hb time 125
15:08:19:844 1420 watchdog - thread 6, hb time 156
15:08:19:844 1420 watchdog - thread 7, hb time 359
15:08:27:048 1860 ETH: checking pool connection...
15:08:27:048 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:27:048 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6370d00", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:27:142 1860 got 244 bytes
15:08:27:142 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:27:142 1860 parse packet: 243
15:08:27:142 1860 eth: job is the same
15:08:27:142 1860 remove first packet 1
15:08:27:142 1860 new buf size: 1
15:08:27:142 1860 buf:

15:08:27:204 1860 got 244 bytes
15:08:27:204 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:08:27:204 1860 parse packet: 243
15:08:27:204 1860 eth: job changed
15:08:27:204 1860 remove first packet 1
15:08:27:204 1860 new buf size: 1
15:08:27:204 1860 buf:

15:08:27:220 1860 ETH: 05/08/16-15:08:27 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:08:27:220 1860 ETH - Total Speed: 104.267 Mh/s, Total Shares: 3446, Rejected: 1, Time: 19:17
15:08:27:220 1860 ETH: GPU0 26.785 Mh/s, GPU1 17.638 Mh/s, GPU2 29.920 Mh/s, GPU3 29.924 Mh/s
15:08:27:235 1848 Job changed, drop current round
15:08:27:235 184c Job changed, drop current round
15:08:27:313 1844 Job changed, drop current round
15:08:27:329 1840 Job changed, drop current round
15:08:27:329 185c Job changed, drop current round
15:08:27:345 1858 Job changed, drop current round
15:08:27:360 1850 Job changed, drop current round
15:08:27:376 1854 Job changed, drop current round
15:08:27:688 1844 ETH: put share nonce d5acf358003d2e24
15:08:27:704 1844 ETH round found 1 shares
15:08:27:720 1860 ETH: 05/08/16-15:08:27 - SHARE FOUND - (GPU 0)
15:08:27:720 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xd5acf358003d2e24","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x369365e98f91879277d6cdda47a0b576bb6970fd9d377a288a8010f5e553adff"]}


15:08:28:454 185c ETH: put share nonce b15b444000e31c90
15:08:28:454 185c ETH round found 1 shares
15:08:28:470 1860 ETH: 05/08/16-15:08:28 - SHARE FOUND - (GPU 3)
15:08:28:470 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xb15b444000e31c90","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x12586d487964b0225f4c97577098b1d6360f7f0392a79e9dd34a0ea82aacd85c"]}


15:08:33:157 184c ETH: put share nonce 9554f330031ed640
15:08:33:157 184c ETH round found 1 shares
15:08:33:173 1860 ETH: 05/08/16-15:08:33 - SHARE FOUND - (GPU 1)
15:08:33:173 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x9554f330031ed640","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x8194182ca30ee4b65903999a4ed783c2a9c101f6bc4e207e8e50ab8f0e1bd3ed"]}


15:08:37:064 1860 ETH: checking pool connection...
15:08:37:064 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:37:064 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x636f4fe", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:37:126 1860 got 244 bytes
15:08:37:126 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:37:126 1860 parse packet: 243
15:08:37:126 1860 eth: job is the same
15:08:37:126 1860 remove first packet 1
15:08:37:126 1860 new buf size: 1
15:08:37:126 1860 buf:

15:08:38:408 184c ETH: put share nonce 9554f33005ee3875
15:08:38:408 184c ETH round found 1 shares
15:08:38:423 1860 ETH: 05/08/16-15:08:38 - SHARE FOUND - (GPU 1)
15:08:38:423 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x9554f33005ee3875","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0xfd3f8ad8ca0e4af02fb29882f0d85477a16702054e056f31df2a105d3e637534"]}


15:08:38:689 1858 ETH: put share nonce 3b2edb040a15daa0
15:08:38:705 1858 ETH round found 1 shares
15:08:38:720 1860 ETH: 05/08/16-15:08:38 - SHARE FOUND - (GPU 3)
15:08:38:720 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x3b2edb040a15daa0","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x6644de2cbf115a09cdb310e20479ca258cc026bf5a25dfb1de96b5b2d89cb762"]}


15:08:47:080 1860 ETH: checking pool connection...
15:08:47:080 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:47:080 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x637c9db", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:47:142 1860 got 244 bytes
15:08:47:142 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:47:142 1860 parse packet: 243
15:08:47:142 1860 eth: job is the same
15:08:47:142 1860 remove first packet 1
15:08:47:142 1860 new buf size: 1
15:08:47:142 1860 buf:

15:08:49:877 1420 em hbt: 16, fm hbt: 94,
15:08:49:877 1420 watchdog - thread 0, hb time 78
15:08:49:877 1420 watchdog - thread 1, hb time 281
15:08:49:877 1420 watchdog - thread 2, hb time 141
15:08:49:877 1420 watchdog - thread 3, hb time 375
15:08:49:877 1420 watchdog - thread 4, hb time 188
15:08:49:877 1420 watchdog - thread 5, hb time 375
15:08:49:893 1420 watchdog - thread 6, hb time 235
15:08:49:893 1420 watchdog - thread 7, hb time 31
15:08:53:736 1860 got 244 bytes
15:08:53:736 1860 buf: {"result":["0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:08:53:736 1860 parse packet: 243
15:08:53:736 1860 eth: job changed
15:08:53:736 1860 remove first packet 1
15:08:53:736 1860 new buf size: 1
15:08:53:736 1860 buf:

15:08:53:752 1860 ETH: 05/08/16-15:08:53 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:08:53:752 1860 ETH - Total Speed: 104.231 Mh/s, Total Shares: 3451, Rejected: 1, Time: 19:17
15:08:53:752 1860 ETH: GPU0 26.788 Mh/s, GPU1 17.631 Mh/s, GPU2 29.909 Mh/s, GPU3 29.903 Mh/s
15:08:53:752 185c Job changed, drop current round
15:08:53:768 1858 Job changed, drop current round
15:08:53:768 1840 Job changed, drop current round
15:08:53:768 1844 Job changed, drop current round
15:08:53:799 1854 Job changed, drop current round
15:08:53:815 1850 Job changed, drop current round
15:08:53:846 184c Job changed, drop current round
15:08:53:846 1848 Job changed, drop current round
15:08:57:096 1860 ETH: checking pool connection...
15:08:57:096 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:57:096 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6369085", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:57:158 1860 got 244 bytes
15:08:57:158 1860 buf: {"result":["0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:57:158 1860 parse packet: 243
15:08:57:158 1860 eth: job is the same
15:08:57:158 1860 remove first packet 1
15:08:57:158 1860 new buf size: 1
15:08:57:158 1860 buf:

15:08:57:283 1840 ETH: put share nonce b9aa581802ac1490
15:08:57:283 1840 ETH round found 1 shares
15:08:57:299 1860 ETH: 05/08/16-15:08:57 - SHARE FOUND - (GPU 0)
15:08:57:299 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xb9aa581802ac1490","0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x088b6f71a6dc557b6a61074b655e8ec0c50c66a6891a8339661e449c8b81a014"]}


15:08:58:502 1858 ETH: put share nonce 13c274b404274b5d
15:08:58:502 1858 ETH round found 1 shares
15:08:58:518 1860 ETH: 05/08/16-15:08:58 - SHARE FOUND - (GPU 3)
15:08:58:518 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x13c274b404274b5d","0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x4a0357031ddc6e9f5e0d2aaf965548a0c99a7d224873f36039e33259dd9fc6ee"]}


15:09:06:003 1860 got 244 bytes
15:09:06:003 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:09:06:003 1860 parse packet: 243
15:09:06:003 1860 eth: job changed
15:09:06:003 1860 remove first packet 1
15:09:06:003 1860 new buf size: 1
15:09:06:003 1860 buf:

15:09:06:003 1860 ETH: 05/08/16-15:09:06 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:09:06:018 1860 ETH - Total Speed: 104.314 Mh/s, Total Shares: 3453, Rejected: 1, Time: 19:17
15:09:06:018 1860 ETH: GPU0 26.795 Mh/s, GPU1 17.637 Mh/s, GPU2 29.953 Mh/s, GPU3 29.930 Mh/s
15:09:06:018 1840 Job changed, drop current round
15:09:06:018 1844 Job changed, drop current round
15:09:06:128 185c Job changed, drop current round
15:09:06:128 1858 Job changed, drop current round
15:09:06:174 1848 Job changed, drop current round
15:09:06:174 184c Job changed, drop current round
15:09:06:190 1850 Job changed, drop current round
15:09:06:190 1854 Job changed, drop current round
15:09:07:112 1860 ETH: checking pool connection...
15:09:07:112 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:09:07:112 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6364821", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:09:07:175 1860 got 244 bytes
15:09:07:175 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:09:07:175 1860 parse packet: 243
15:09:07:175 1860 eth: job is the same
15:09:07:175 1860 remove first packet 1
15:09:07:175 1860 new buf size: 1
15:09:07:190 1860 buf:

15:09:17:128 1860 ETH: checking pool connection...
15:09:17:128 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:09:17:128 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6377ed2", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:09:17:191 1860 got 244 bytes
15:09:17:191 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:09:17:191 1860 parse packet: 243
15:09:17:191 1860 eth: job is the same
15:09:17:191 1860 remove first packet 1
15:09:17:191 1860 new buf size: 1
15:09:17:191 1860 buf:

15:09:19:909 1420 em hbt: 0, fm hbt: 47,

heres just one example.. i have hundreds more it appears ;/  didnt realize it was that bad for so long.. ehh thats what happens when you (set and forget).

Code:
ETH: 05/08/16-15:22:09 - SHARE FOUND - (GPU 1)
15:22:09:317 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xc7b17160003e7631","0x37c0f742aa0dc33aec20a568f45a032b6adc7164292d403e9606f36699247873","0x5869dbb8c7964481ee65b5239cd36e0fa715480b945afcef5d6f4e2e9bebb736"]}


15:22:11:255 1860 ETH: checking pool connection...
15:22:11:255 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:22:11:255 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6361ca7", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:22:11:333 1860 got 244 bytes
15:22:11:333 1860 buf: {"result":["0x37c0f742aa0dc33aec20a568f45a032b6adc7164292d403e9606f36699247873","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:22:11:333 1860 parse packet: 243
15:22:11:333 1860 eth: job is the same
15:22:11:333 1860 remove first packet 1
15:22:11:333 1860 new buf size: 1
15:22:11:333 1860 buf:

15:22:17:036 1860 got 40 bytes
15:22:17:036 1860 buf: {"id":4,"jsonrpc":"2.0","result":true}


15:22:17:036 1860 parse packet: 39
15:22:17:036 1860 ETH: Share accepted (7719 ms)!

15:22:17:036 1860 remove first packet 1
15:22:17:036 1860 new buf size: 1
15:22:17:036 1860 buf:

15:22:17:833 1860 got 40 bytes
15:22:17:833 1860 buf: {"id":6,"jsonrpc":"2.0","result":true}


15:22:17:833 1860 parse packet: 39
15:22:17:833 1860 remove first packet 1
15:22:17:833 1860 new buf size: 1
15:22:17:833 1860 buf:

15:22:20:083 1860 got 244 bytes
15:22:20:083 1860 buf: {"result":["0xa3c450677cda25ec700bb01897b40deaa973d96cdf179debbd1ab9fb0814d533","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:22:20:083 1860 parse packet: 243
15:22:20:083 1860 eth: job changed
15:22:20:083 1860 remove first packet 1
15:22:20:083 1860 new buf size: 1
15:22:20:083 1860 buf:

15:22:20:099 1860 ETH: 05/08/16-15:22:20 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:22:20:099 1860 ETH - Total Speed: 104.312 Mh/s, Total Shares: 3496, Rejected: 4, Time: 19:31
15:22:20:099 1860 ETH: GPU0 26.797 Mh/s, GPU1 17.634 Mh/s, GPU2 29.930 Mh/s, GPU3 29.951 Mh/s

This is the typical return time i get.. Around 80 ms for us server. and when i swapped to eu it was 120 ms round trip..

Code:
ETH: 05/07/16-19:51:30 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
19:51:30:235 1860 ETH - Total Speed: 104.103 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:51:30:237 1860 ETH: GPU0 26.653 Mh/s, GPU1 17.627 Mh/s, GPU2 29.919 Mh/s, GPU3 29.904 Mh/s
19:51:30:259 184c Job changed, drop current round
19:51:30:260 1850 Job changed, drop current round
19:51:30:262 1848 Job changed, drop current round
19:51:30:266 1854 Job changed, drop current round
19:51:30:298 1858 Job changed, drop current round
19:51:30:299 185c Job changed, drop current round
19:51:30:407 1844 Job changed, drop current round
19:51:30:410 1840 Job changed, drop current round
19:51:30:995 1840 ETH: put share nonce a89791000974346
19:51:30:997 1840 ETH round found 1 shares
19:51:30:999 1860 ETH: 05/07/16-19:51:30 - SHARE FOUND - (GPU 0)
19:51:30:999 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x0a89791000974346","0x6d17ae3e751193b988570fc5181d3fcb5c88904686429c5ceb694db81b19e53b","0xfc9a9de4a9ddc7e2ae58dc092873c96f4322bd017b8150a8efde3b76767b39cf"]}


19:51:31:078 1860 got 40 bytes
19:51:31:080 1860 buf: {"id":4,"jsonrpc":"2.0","result":true}


19:51:31:080 1860 parse packet: 39
19:51:31:086 1860 ETH: Share accepted (79 ms)!

19:51:31:090 1860 remove first packet 1
19:51:31:091 1860 new buf size: 1
19:51:31:091 1860 buf:

19:51:33:249 1860 got 244 bytes
19:51:33:252 1860 buf: {"result":["0x21b5a4d06f2fa097655d5c008e2421e580b2fb9c1989910940901de1e3272061","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


19:51:33:254 1860 parse packet: 243
19:51:33:254 1860 eth: job changed
19:51:33:259 1860 remove first packet 1
19:51:33:262 1860 new buf size: 1
19:51:33:264 1860 buf:

19:51:33:264 1860 ETH: 05/07/16-19:51:33 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
19:51:33:270 1860 ETH - Total Speed: 104.224 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
19:51:33:274 1860 ETH: GPU0 26.781 Mh/s, GPU1 17.6
member
Activity: 98
Merit: 10
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.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1


donator
Activity: 1610
Merit: 1325
Miners developer
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.
sr. member
Activity: 328
Merit: 250
After restart I am getting EthDcrminer64.exe Initialization error 5 on 2 rigs. Genoil works. These rigs worked for months before restart. What is wrong? Is there some time limit or so?
member
Activity: 98
Merit: 10
Is Claymore working with dwarf through stratum?

What settings should it be?



Also Dwarf Admin said that Claymore are working bad with failover servers.



He suggest usung local proxy with 1+3 failover servers.

How to set up this?
full member
Activity: 196
Merit: 100
today when i woke up i saw that the CDM window was closed no error message
dont know if it tried to restart or not

EthDcrMiner64.exe -mode 1 -epool eth-eu.dwarfpool.com:8008 -ewal 0x0/gpu1 -epsw x -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal tolazy.dcr -dpsw x -dcri 65

dont use dcr rather have the gpu OC for eth.

anyone else have seen this error?
CDM 4.2 windows
390x @ 1160Mhz only 80MHz OC
powerlimit +50

core volt +25 default +19

getting 33.1Mhs
donator
Activity: 1610
Merit: 1325
Miners developer
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.
full member
Activity: 165
Merit: 100
my miner allways say avaible card 0
no card in the list

i use v4.2
windows 10
16gb virtual memory
all variable is set correcly...
all hardware in device manager is detected...
anyone have a idea of my problem?

my gpu is 4X r9 290 with driver 15.2
firewall is off.. tryed everything.. i dont understand

11:58:56:821   418   
Cards available: 0
11:58:56:826   418   No cards in the list!

can someone help me please?


you checked them with device manager already? Are you using on board graphics to boot your com?
newbie
Activity: 1
Merit: 0
my miner allways say avaible card 0
no card in the list

i use v4.2
windows 10
16gb virtual memory
all variable is set correcly...
all hardware in device manager is detected...
anyone have a idea of my problem?

my gpu is 4X r9 290 with driver 15.2
firewall is off.. tryed everything.. i dont understand

11:58:56:821   418   
Cards available: 0
11:58:56:826   418   No cards in the list!

can someone help me please?
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Btw, can you see my other inquiry on solo mining?
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  Grin

You could always solo mine without a proxy....

If local mode solo mining (ie. 1 PC solo mining Geth instance in same PC) then no need proxy.

What I meant was MANY rigs pointing to Geth directly without the need of a proxy. CDM can do this - and that IMO gives reduces variances and delays, technically faster solo mining.

Until the existence of Claymore's v4.2, the only "many workers/rigs" solo mining solution was using a proxy solution (ie. Dwarfpool, Sammy007 etc) to aggregate many workers/rigs hash streams into one steady stream using a proxy server, because the standard ethminer, vanilla or genoil's version are not designed to work with Stratum based Eth pools. Qtminer however works with Stratum based Eth pools - but that's about it - CDM has more features. This is my understanding. Appreciate if any experts out there can verify. thanks

You could do the "many workers/rigs" solo mining with the other miners as well since the beginning.  Using Claymore's example, just point your rigs at 192.168.0.2:8545 and you're solo mining.  Sammy's proxy gave a nice interface to monitor the solo mining however.  You don't need stratum to solo mine, the latency between your rigs and the geth instance is going to be so small it doesn't matter (if you're on the same lan).  Stratum is great for mining at pools because instead of your miner asking if there's a new block every X ms, the pool tells your miner there is a new block.  Much more efficient.

ok good info - appreciate it melloyellow
full member
Activity: 176
Merit: 100
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
full member
Activity: 176
Merit: 100
Btw, can you see my other inquiry on solo mining?
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  Grin

You could always solo mine without a proxy....

If local mode solo mining (ie. 1 PC solo mining Geth instance in same PC) then no need proxy.

What I meant was MANY rigs pointing to Geth directly without the need of a proxy. CDM can do this - and that IMO gives reduces variances and delays, technically faster solo mining.

Until the existence of Claymore's v4.2, the only "many workers/rigs" solo mining solution was using a proxy solution (ie. Dwarfpool, Sammy007 etc) to aggregate many workers/rigs hash streams into one steady stream using a proxy server, because the standard ethminer, vanilla or genoil's version are not designed to work with Stratum based Eth pools. Qtminer however works with Stratum based Eth pools - but that's about it - CDM has more features. This is my understanding. Appreciate if any experts out there can verify. thanks

You could do the "many workers/rigs" solo mining with the other miners as well since the beginning.  Using Claymore's example, just point your rigs at 192.168.0.2:8545 and you're solo mining.  Sammy's proxy gave a nice interface to monitor the solo mining however.  You don't need stratum to solo mine, the latency between your rigs and the geth instance is going to be so small it doesn't matter (if you're on the same lan).  Stratum is great for mining at pools because instead of your miner asking if there's a new block every X ms, the pool tells your miner there is a new block.  Much more efficient.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Btw, can you see my other inquiry on solo mining?
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  Grin

You could always solo mine without a proxy....

If local mode solo mining (ie. 1 PC solo mining Geth instance in same PC) then no need proxy.

What I meant was MANY rigs pointing to Geth directly without the need of a proxy. CDM can do this - and that IMO gives reduces variances and delays, technically faster solo mining.

Until the existence of Claymore's v4.2, the only "many workers/rigs" solo mining solution was using a proxy solution (ie. Dwarfpool, Sammy007 etc) to aggregate many workers/rigs hash streams into one steady stream using a proxy server, because the standard ethminer, vanilla or genoil's version are not designed to work with Stratum based Eth pools. Qtminer however works with Stratum based Eth pools - but that's about it - CDM has more features. This is my understanding. Appreciate if any experts out there can verify. thanks
member
Activity: 72
Merit: 10
Installed and running in minutes without a hitch!

...nice job on the console readouts btw
hero member
Activity: 742
Merit: 505
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

If you have 20 rigs at a remote location ... you could probably also afford a usable connection Cheesy


(but i do agree.. optimalization at all stages)
member
Activity: 96
Merit: 10
Is it possible to solo mine without the hole blockchain in local machine but just an address in exchange? As i see it, only the current info is needed for calculations, not all 10+GB?
donator
Activity: 1610
Merit: 1325
Miners developer
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.
full member
Activity: 124
Merit: 100
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
donator
Activity: 1610
Merit: 1325
Miners developer
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.
Jump to: