Author

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

full member
Activity: 1092
Merit: 227
Something wrong, on two mashines, miner crash (not freezz, but process crash):

Confirmed, probably this issue is related to Linux version only. I just saw this on my test linux rig. Since it works for several hours before crashing, it will take some time to fix it.

Yup, one little rig i have on windows. Working stable.
Trouble on linux ver.

I try to add -tt 0 (for disable T and Fans watch - but this option does not work oO)
donator
Activity: 1610
Merit: 1325
Miners developer
complete log-file

Finally I got it. Issue confirmed and fixed, re-download v4.3, log must show "b142" now (means build 142).

-erate:

Check OP or readme for sample how to specify worker name for dwarf. Hint:  -ewal YourWallet/YourWorkerName.
Don't use -erate option because it is already "1" by default.
donator
Activity: 1610
Merit: 1325
Miners developer
So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["", "", ";;", "", ";;", "", ";", ""]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?

It's usual tcp/ip connection - create socket, connect, send the string "{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}" and read response, disconnect, that is all.
newbie
Activity: 7
Merit: 0
So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["", "", ";;", "", ";;", "", ";", ""]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?
donator
Activity: 1610
Merit: 1325
Miners developer

@claymore: Do you plan any output from the miner itself maybe in json format ? This would be killer feature for miner with more then just a few rigs to build central monitoring

Miner sends stats in json format, use wireshark or similar tool to see format. So you can write own monitoring utility if you want.
donator
Activity: 1610
Merit: 1325
Miners developer
Something wrong, on two mashines, miner crash (not freezz, but process crash):

Confirmed, probably this issue is related to Linux version only. I just saw this on my test linux rig. Since it works for several hours before crashing, it will take some time to fix it.
legendary
Activity: 2026
Merit: 1005
Who else has had an issue with "-erate" (dwarf) and "-etha" (windows)?
member
Activity: 82
Merit: 11
someone who gets monitoring/management feature up and running ?  On my linux ubuntu i'm not able to load site.

Quote
Remote management is enabled on port 3333

But surfing on ip:3333 ends in endless loading without any information.

Like up member say:
3333 - port for desktop app.
8000 - port for web (only if desktop app started, i think)

i'm running linux, so seems like managament and monitor isn't available for linux ?
port 8000 also doesn't return anything. Seems like Miner manager does the web part not the miner itself.

@claymore: Do you plan any output from the miner itself maybe in json format ? This would be killer feature for miner with more then just a few rigs to build central monitoring
newbie
Activity: 49
Merit: 0
someone who gets monitoring/management feature up and running ?  On my linux ubuntu i'm not able to load site.

Quote
Remote management is enabled on port 3333

But surfing on ip:3333 ends in endless loading without any information.
To manage the necessary utility "Remote manager" which is located in the folder for windows   Sad
legendary
Activity: 2026
Merit: 1005
This is the part of log-file  Smiley
Nothing has changed in 4.3, the bug is present.

I don't need part of log. I need full log. It is because I have a rig with several 290X and I cannot reproduce the issue that you mention. So the complete log file is the only thing that can help me.
win7 x64/16gb page-file size/8gb ram/catalyst 16.1 (nothing has changed with 15.12/15.11/16.3)

Sorry, I will ignore your issue until you PM me complete log file.
Latest version v4.3:

- added "-erate" option.

It doesnt work on dwarf pool - Sent Hashrate(MHs) is empty as for previous v. 4.2

complete log-file
Code:
23:09:08:551	bb0	commandline: c:\ether\clay\EthDcrMiner64.exe  -epool eth-eu.dwarfpool.com:8008 -ewal 0x6343ac3f15c925acd28bbf799a138781XXXXXXXX -epsw x -eworker XXXX -erate 1 -estale 1 -esm 0 -etha 0,0,0,0,0 -ethi 16 -eres 2 -etht 200 -mode 1 -tstop 93 -dbg 1 -mport 0
23:09:08:551 bb0
23:09:08:551 bb0 ЙHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH»
23:09:08:551 bb0 є   Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.3 Beta   є
23:09:08:551 bb0 ИHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHj
23:09:08:551 bb0
23:09:08:751 bb0 ETH: 1 pool is specified
23:09:09:421 bb0 OpenCL platform: AMD Accelerated Parallel Processing
23:09:09:421 bb0
Cards available: 5
23:09:09:421 bb0 GPU #0: name: Hawaii, 4096 MB available, 44 compute units
23:09:09:421 bb0 GPU #1: name: Hawaii, 4096 MB available, 44 compute units
23:09:09:421 bb0 GPU #2: name: Hawaii, 4096 MB available, 44 compute units
23:09:09:421 bb0 GPU #3: name: Hawaii, 4096 MB available, 44 compute units
23:09:09:421 bb0 GPU #4: name: Hawaii, 4096 MB available, 40 compute units
23:09:09:421 bb0 Total cards: 5
23:09:09:431 bb0 Initializing...

23:09:09:431 bb0 GPU #0 recognized as Radeon 290X
23:09:09:431 bb0 GPU #1 recognized as Radeon 290X
23:09:09:431 bb0 GPU #2 recognized as Radeon 290X
23:09:09:431 bb0 GPU #3 recognized as Radeon 290X
23:09:09:431 bb0 GPU #4 recognized as Radeon 290
23:09:09:431 bb0 POOL/SOLO version
23:09:09:431 bb0 b141
23:09:09:431 bb0 start building OpenCL program...
23:09:11:031 bb0 done
23:09:11:031 bb0 GPU #0: set -etha as 1 (ETH algo for slow cards)
23:09:11:031 bb0 GPU #1: set -etha as 1 (ETH algo for slow cards)
23:09:11:031 bb0 GPU #2: set -etha as 1 (ETH algo for slow cards)
23:09:11:031 bb0 GPU #3: set -etha as 1 (ETH algo for slow cards)
23:09:11:031 bb0 GPU #4: set -etha as 1 (ETH algo for slow cards)
23:09:11:171 b34 ETH: Stratum - connecting to 'eth-eu.dwarfpool.com' <87.98.182.61> port 8008
23:09:11:261 bb0 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

23:09:11:261 bb0 miner-proxy stratum mode
23:09:11:261 bb0 Watchdog enabled
23:09:11:261 bb0

23:09:12:221 b34 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x6343ac3f15c925acd28bbf799a138781XXXXXXXX", "x"], "id": 2, "method": "eth_submitLogin"}

23:09:12:221 b34 ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
23:09:12:271 b34 got 39 bytes
23:09:12:271 b34 buf: {"id":2,"jsonrpc":"2.0","result":true}

23:09:12:271 b34 parse packet: 39
23:09:12:271 b34 ETH: Authorized
23:09:12:271 b34 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

23:09:12:271 b34 new buf size: 0
23:09:12:331 b34 got 244 bytes
23:09:12:331 b34 buf: {"result":["0x9e30025a2c38c52deb61fa5a2d66c559b5fa0bdcce6cb8c138bfc30471ac781a","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


23:09:12:331 b34 parse packet: 243
23:09:12:331 b34 eth: job changed
23:09:12:331 b34 remove first packet 1
23:09:12:331 b34 new buf size: 1
23:09:12:331 b34 buf:

23:09:12:381 8d4 Setting DAG epoch #51...
23:09:14:051 8d4 Setting DAG epoch #51 for GPU #4
23:09:14:051 ea8 Setting DAG epoch #51 for GPU #3
23:09:14:061 f64 Setting DAG epoch #51 for GPU #2
23:09:14:071 cd0 Setting DAG epoch #51 for GPU #0
23:09:14:071 910 Setting DAG epoch #51 for GPU #1
23:09:14:081 8d4 Create GPU buffer for GPU #4
23:09:14:091 ea8 Create GPU buffer for GPU #3
23:09:14:091 f64 Create GPU buffer for GPU #2
23:09:14:101 cd0 Create GPU buffer for GPU #0
23:09:14:111 910 Create GPU buffer for GPU #1
23:09:20:451 8d4 GPU 4 DAG creation time 6253 ms
23:09:20:451 8d4 Setting DAG epoch #51 for GPU #4 done
23:09:20:581 f64 GPU 2 DAG creation time 6432 ms
23:09:20:591 910 GPU 1 DAG creation time 6438 ms
23:09:20:601 f64 Setting DAG epoch #51 for GPU #2 done
23:09:20:601 ea8 GPU 3 DAG creation time 6425 ms
23:09:20:611 ea8 Setting DAG epoch #51 for GPU #3 done
23:09:20:621 910 Setting DAG epoch #51 for GPU #1 done
23:09:20:681 cd0 GPU 0 DAG creation time 6430 ms
23:09:20:691 cd0 Setting DAG epoch #51 for GPU #0 done
23:09:21:721 b34 got 244 bytes
23:09:21:721 b34 buf: {"result":["0x80e055d940c2062284ce7e0be91c71ba605d32797cf3601816d5aacdeae27264","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


23:09:21:721 b34 parse packet: 243
23:09:21:721 b34 eth: job changed
23:09:21:721 b34 remove first packet 1
23:09:21:721 b34 new buf size: 1
23:09:21:721 b34 buf:

23:09:21:721 b34 ETH: 05/18/16-23:09:21 - New job (target 0x0000000225c17d04) from eth-eu.dwarfpool.com:8008
23:09:21:731 b34 ETH - Total Speed: 128.870 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
23:09:21:741 b34 ETH: GPU0 25.712 Mh/s, GPU1 25.726 Mh/s, GPU2 25.720 Mh/s, GPU3 25.702 Mh/s, GPU4 26.010 Mh/s
23:09:22:351 b34 ETH: checking pool connection...
23:09:22:351 b34 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

23:09:22:401 b34 got 244 bytes
23:09:22:401 b34 buf: {"result":["0x80e055d940c2062284ce7e0be91c71ba605d32797cf3601816d5aacdeae27264","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


23:09:22:401 b34 parse packet: 243
23:09:22:401 b34 eth: job is the same
23:09:22:401 b34 remove first packet 1
23:09:22:401 b34 new buf size: 1
23:09:22:401 b34 buf:

23:09:28:121 f64 ETH: put share nonce 8d895d9c047b66c1
23:09:28:121 f64 ETH round found 1 shares
23:09:28:131 b34 ETH: 05/18/16-23:09:28 - SHARE FOUND - (GPU 2)
23:09:28:131 b34 send: {"worker":"{XXXX","id":4,"method":"eth_submitWork","params":["0x8d895d9c047b66c1","0x80e055d940c2062284ce7e0be91c71ba605d32797cf3601816d5aacdeae27264","0x6758718f568b3cc07de6046a135aa941bd778c5dfdfc44147bed130171f82341"]}

23:09:28:191 b34 got 40 bytes
23:09:28:191 b34 buf: {"id":4,"jsonrpc":"2.0","result":true}


23:09:28:191 b34 parse packet: 39
23:09:28:191 b34 ETH: Share accepted (47 ms)!

23:09:28:191 b34 remove first packet 1
23:09:28:191 b34 new buf size: 1
23:09:28:191 b34 buf:

23:09:30:371 b34 got 244 bytes
23:09:30:371 b34 buf: {"result":["0xd5e2cd7704885ec7df01a58dd12f1e5d298d4f66dc35d249ef23178814c2e695","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


23:09:30:371 b34 parse packet: 243
23:09:30:371 b34 eth: job changed
23:09:30:371 b34 remove first packet 1
23:09:30:371 b34 new buf size: 1
23:09:30:371 b34 buf:

23:09:30:371 b34 ETH: 05/18/16-23:09:30 - New job (target 0x0000000225c17d04) from eth-eu.dwarfpool.com:8008
23:09:30:381 b34 ETH - Total Speed: 129.350 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
23:09:30:391 b34 ETH: GPU0 25.768 Mh/s, GPU1 25.752 Mh/s, GPU2 25.757 Mh/s, GPU3 25.734 Mh/s, GPU4 26.339 Mh/s
23:09:30:611 b34 got 244 bytes
23:09:30:611 b34 buf: {"result":["0x8aa35565076519f625855a15f6101fc1170a5684c9e01c0d10623ade482b97a2","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


23:09:30:611 b34 parse packet: 243
23:09:30:611 b34 eth: job changed
23:09:30:611 b34 remove first packet 1
23:09:30:611 b34 new buf size: 1
23:09:30:611 b34 buf:

23:09:30:611 b34 ETH: 05/18/16-23:09:30 - New job (target 0x0000000225c17d04) from eth-eu.dwarfpool.com:8008
23:09:30:621 b34 ETH - Total Speed: 129.353 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
23:09:30:631 b34 ETH: GPU0 25.768 Mh/s, GPU1 25.752 Mh/s, GPU2 25.760 Mh/s, GPU3 25.750 Mh/s, GPU4 25.046 Mh/s
23:09:32:341 b34 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x7b64145", "0x000000000000000000000000000000000000000000000000000000009ff1e5fb"]}

23:09:32:361 b34 ETH: checking pool connection...
23:09:32:361 b34 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

23:09:32:391 b34 got 40 bytes
23:09:32:391 b34 buf: {"id":6,"jsonrpc":"2.0","result":true}


23:09:32:391 b34 parse packet: 39
23:09:32:391 b34 remove first packet 1
23:09:32:391 b34 new buf size: 1
23:09:32:391 b34 buf:

23:09:32:441 b34 got 244 bytes
23:09:32:441 b34 buf: {"result":["0x8aa35565076519f625855a15f6101fc1170a5684c9e01c0d10623ade482b97a2","0xe71828fc57e8425d0dd0b77ace7b2030cfa18afd2f5d5513a3eef30729508fae","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


23:09:32:441 b34 parse packet: 243
23:09:32:441 b34 eth: job is the same
23:09:32:441 b34 remove first packet 1
23:09:32:441 b34 new buf size: 1
23:09:32:441 b34 buf:

sr. member
Activity: 661
Merit: 250
full member
Activity: 1092
Merit: 227
someone who gets monitoring/management feature up and running ?  On my linux ubuntu i'm not able to load site.

Quote
Remote management is enabled on port 3333

But surfing on ip:3333 ends in endless loading without any information.

Like up member say:
3333 - port for desktop app.
8000 - port for web (only if desktop app started, i think)
member
Activity: 82
Merit: 11
someone who gets monitoring/management feature up and running ?  On my linux ubuntu i'm not able to load site.

Quote
Remote management is enabled on port 3333

But surfing on ip:3333 ends in endless loading without any information.
member
Activity: 82
Merit: 10
How does the remote monitor work? I work during the day and would really like to see these rigs with temps from work.
U need dedicated IP for this, unfirewalled/forwarded port 3333 to ur computer (rig).
And copy RM to work pc, enter home ip and u can see how it work.

The remote monitor also serves up a simple web page at port 8000 by default, which you can check on a phone.
full member
Activity: 1092
Merit: 227
How does the remote monitor work? I work during the day and would really like to see these rigs with temps from work.
U need dedicated IP for this, unfirewalled/forwarded port 3333 to ur computer (rig).
And copy RM to work pc, enter home ip and u can see how it work.
sr. member
Activity: 283
Merit: 250
How does the remote monitor work? I work during the day and would really like to see these rigs with temps from work.
donator
Activity: 1610
Merit: 1325
Miners developer
This is the part of log-file  Smiley
Nothing has changed in 4.3, the bug is present.

I don't need part of log. I need full log. It is because I have a rig with several 290X and I cannot reproduce the issue that you mention. So the complete log file is the only thing that can help me.
win7 x64/16gb page-file size/8gb ram/catalyst 16.1 (nothing has changed with 15.12/15.11/16.3)

Sorry, I will ignore your issue until you PM me complete log file.
sr. member
Activity: 661
Merit: 250
Thank you for your job !
Remote monitoring ! Waouh !
newbie
Activity: 14
Merit: 0
pool.mn and coinmine.pl are easily the best decred pools.

The guy who runs zpool either doesn't know what he's doing or is a fraud. I mined on the pool for 10 days and the payouts are consistently lower than they should be by 15-20%. I wouldn't mine there.
legendary
Activity: 2026
Merit: 1005
This is the part of log-file  Smiley
Nothing has changed in 4.3, the bug is present.

I don't need part of log. I need full log. It is because I have a rig with several 290X and I cannot reproduce the issue that you mention. So the complete log file is the only thing that can help me.
win7 x64/16gb page-file size/8gb ram/catalyst 16.1 (nothing has changed with 15.12/15.11/16.3)
Jump to: