I mentioned web server, it is for that.
I'm just worried that its gonna be a local web server within the LAN of the mining farm. I can't be bothered to setup dynamic IP hosting and configuring my firewall etc for accessing the stats page on the web server when i'm outside. If you could create something that can push the data from the rigs to your server and then to the app on my iPhone, that would be awesome. Realtime stats on all rigs. Click on a rig name to get detailed stats on that particular machine. Group/individual config for pools. etc etc. Yes it will be local server. Accessing it from outside is a completely separate task. |
|
|
|
Claymore, with your monitoring app, you should also create an android/iOS app which can give us full control of the rigs, including restarting, push-notification alerts, etc. Maybe even rig config too (clock speed, pool settings, etc). I'd be willing to pay for your app if you could do something like that.
I mentioned web server, it is for that. |
|
|
|
Hi! Claymore.
Are there any news on solomining option and + getting the jobs out of geth running aside?
thank you
peace
I'm working on a 3-in-1 utility: 1. pool proxy for my miner (allows to change settings/pools easily for large farms). 2. proxy for solo mode. 3. Monitoring/management + web server for monitoring. Solo will be available with this utility - you point all your rigs to this utility and point this utility to geth. Hope to release first version in a few days. Next update will be available within 24 hours and will include CRC check for DAGs (no more corrupted DAGs) and Failover. |
|
|
|
Hello. It's true. I have the same problem. My effictive average Hashrate is on both miners I use way off (about 5-10 MH/s).
Miner1:
Reported 142,1 MH/s; Effective Average Hashrate 136.5 MH/s (which is on the higher side, it can go down to almost 130 MH/s)
Miner2:
Reported 134,3 MH/s; Effective Average Hashrate 125.8 MH/s
Pool: Ethermine;
Miner: Claymore's miner in eth only mode.
Windows 7 with mixed GPUs.
I'am aware of the dev fee, but it shouldn't be more than 1,5 MH/s.
With this miner I have almost no invalid shares, and it restarts if anything happens - which is great. But also more watt consumption and apparently no real average (24h) MH/s gain. (reported hashrate is about 5% higher with this miner).
Anyone else with this problem?
What is the maximum value -ethi? 100 or 36 or 16 If you put -ethi 100 heshrate high, if put -ethi -16,384 heshrate low, but SHARES are located quickly. There is no stability in finding SHARES What is the problem? Max "-ethi" value is 32 but it is not a good idea to set it above 16, next update will use 8 by default. At 32 one GPU round can take up to 1sec (depends on GPU) and when miner gets new job it cannot cancel current GPU round so it will lose up to 500ms in average, for 15sec block time it is up to 3-4% of lost time. |
|
|
|
@ Mr. Claymoretimeout /t 10
EthDcrMiner64.exe -epool coinotron.com:3344 -epsw pass -ewal serj2.006 -esm 2 -allpools 1 -dir C:\Users\user\Documents\ClaymoreED\dag0 -mode 0 -dpool stratum+tcp://dcr.coinmine.pl:2222 -dwal salex.006 -dpsw password -dcri 25 -dbg 1 -r 1 -ethi 4
pause reboot.bat shutdown -r Log https://yadi.sk/i/8Laaj337rE5eKscreen https://yadi.sk/i/K_n2QwH4rE5pfI guess log is ok, this is not miner issue. But it there any way to handle this error and run some reboot.bat? edit: or you can add checking hashrate. eg. last message in log 11:46:24:457 1360 DCR: GPU0 385.285 Mh/s, GPU1 385.572 Mh/s, GPU2 217.012 Mh/s, GPU3 129166.883 Mh/s, GPU4 385.693 Mh/s, GPU5 237.894 Mh/s immpossible 129 Gh/s hashrate:) Your card ignores OpenCL work somehow and returns immediately without any error, so you get such crazy hashrate. I will fix it in next update, it will show zero hashrate and therefore watchdog will work. |
|
|
|
Again, it is minor bug and you can mine. Start miner and wait. |
|
|
|
I tried these settings with the setting for coinotron but I get this
15:14:16:804 1570 Need to check DAG file (epoch #46), starting...
15:14:16:945 914 got 101 bytes
15:14:16:945 914 buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}
15:14:16:945 914 parse packet: 36
15:14:16:945 914 ETH: Authorized
15:14:16:945 914 remove first packet 54
15:14:16:945 914 new buf size: 54
15:14:16:945 914 parse packet: 54
15:14:16:945 914 send: {"error": null, "jsonrpc": "id": 9876, "result": "eth 1.0"}
15:14:16:945 914 new buf size: 0
15:14:17:148 914 got 66 bytes
15:14:17:148 914 buf: {"id": , "result": null, "error": [51, "JSON parse error", null]}
15:14:17:148 914 parse packet: 57
15:14:17:148 914 Cannot parse JSON!
15:14:17:148 914 new buf size: 0
15:14:19:165 660 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
15:14:22:170 660 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
It's a minor bug, will be fixed in next update: miner sends incorrect version answer, then pool sends incorrect report about the error, therefore you see this warning. You still can mine, here is my command line that you can use as start point, very similar to sample from OP: EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -allpools 1 |
|
|
|
|
Yes it is a good idea to set some timeout in .bat file before starting miner at system startup (30sec or even a minute), and try "-ethi 4" to check if it is more stable. It can help if miner is not stable on some system. Note "-ethi 4" can reduce mining speed a bit.
Added to OP.
|
|
|
|
So this one's got me stumped. DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 9112
ETH: Stratum - Connected
DCR: Stratum - Connected
ETH: Authorized
ETH: Job timeout, disconnect, retry in 20 sec...
DCR: Job timeout, disconnect, retry in 20 sec...
ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3334
ETH: Stratum - Connected
ETH: Authorized
DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 9112
DCR: Stratum - Connected
ETH: Job timeout, disconnect, retry in 20 sec...
DCR: Job timeout, disconnect, retry in 20 sec...
ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3334
ETH: Stratum - Connected
ETH: Authorized
DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 9112
DCR: Stratum - Connected
ETH: Job timeout, disconnect, retry in 20 sec...
DCR: Job timeout, disconnect, retry in 20 sec...
ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3334
ETH: Stratum - Connected
ETH: Authorized
ETH: Job timeout, disconnect, retry in 20 sec...
DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 9112
DCR: Stratum - Connected Wrong ports and/or protocols. It's a good idea to show your command line if you want to know more details. |
|
|
|
anyone can help me understand this "--farm-recheck" ?
Check for new task every x.xxx seconds thanks so, faster GPUs can use --farm-recheck 200 or 100 ? It is better to use 100, that is to check every 100ms. Claymore, does the --farm-recheck really change the way the miner mines? Because on ethminer-genoil with stratum, it only modifiy the rate at which hashing speed is calculated. On your miner though, the display of the hashing speed is not affected by this it seems. --farm-recheck is not supported by my miner. Moreover, it is for HTTP to work with Stratum proxy, my miner uses Stratum directly. |
|
|
|
|
Problems on DCR pools forced me to check my code again and again to be sure that these problems are not related to the miner and I rewrote some routines to improve Stratum support for Decred.
v3.2:
- reduced number of rejected shares for Decred-Stratum.
- miner sends its current hashrate to pool, some pools have "reported hashrate" column and you can see miner hashrate there.
- miner shows how long it takes pool to accept share.
- option "-r 1" closes miner and calls "reboot.bat" if some GPU failed, so you can create "reboot.bat" to perform any actions.
- Bug fixes, a few minor improvements.
I'm still working on failover and other new features.
|
|
|
|
I tried to use -wd 1, but can't make it to close the miner tried -r -1 tried -r 0 When I mistype pool name (simulating dns /connectivity problem) it just keeps retrying to connect every 20sec, won't close the miner  My miner does not close. It will hang the system. So I use -wd 0 to disable the watchdog, and -r -1 not to restart. . +1 , after ver. 3.0 i found my rig 2 times freezed after a crash, i will test with -wd 0 and -r -1 now +1 same here windows totally freezes and crash sometime i have no unplug it to restart  When GPU fails, often Windows cannot work properly anymore and often it cannot even reboot normally. In your old miner, 1.0 to 2.0, when the one GPU hang, the mining can still continue in other GPUs. Disable watchdog: "-wd 0" if you want to continue mining if some GPU failed. |
|
|
|
hey claymore, could you make one of these for decred and expanse? it would be cool and it should work, right? This miner works like a charm. I dont mind the fees at all since it increased my hashrate by more than 3% without counting decred!  You can mine expanse and decred, check OP or readme file: ... Ethereum forks mining: EthDcrMiner64.exe -epool exp-us.dwarfpool.com:8018 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -allcoins -1 ... Just set your address add decred parameters to this sample command line. |
|
|
|
A bit strange approach, is not it? Just send worker name as second param and it would work like a charm.
Eth's mining methods are more then a bit strange (and inconsistent between every implementation), indeed. 2 requests (fairly trivial I think): - show eth/dcr when printing Authorized - show response time in ms for work submition and response e.g. Share Accepted (80ms) Well, I will send worker name as third param then. Ok, your requests will be added in next update. |
|
|
|
I tried to use -wd 1, but can't make it to close the miner tried -r -1 tried -r 0 When I mistype pool name (simulating dns /connectivity problem) it just keeps retrying to connect every 20sec, won't close the miner My miner does not close. It will hang the system. So I use -wd 0 to disable the watchdog, and -r -1 not to restart. . +1 , after ver. 3.0 i found my rig 2 times freezed after a crash, i will test with -wd 0 and -r -1 now +1 same here windows totally freezes and crash sometime i have no unplug it to restart When GPU fails, often Windows cannot work properly anymore and often it cannot even reboot normally. |
|
|
|
@Claymore, i'm using your latest beta release. Will the -wd 1 -r -1 switches work?
And I have a loop in my startup batch file. So I have to just have a blank reboot.bat file in order for it to jump back to my original batch file loop
?
"-wd 1 -r -1" will work. |
|
|
|
Yes I found "eth_submitHashrate" but I'd like to check some miner that sends this command to see how it works. There is no any documentation about it but it seems it has two params: first is the hashrate, second is filled by random and it's strange, it must be worker name so pool can know who reports the hashrate. I confirmed with dr_pra that the 2nd param is ignored (at least by ethpool/ethermine). If more then one worker connects via a stratum proxy, submitted hashrate doesn't work. If a single worker is used on a connection, the hashrate is assosiated with that worker. A bit strange approach, is not it? Just send worker name as second param and it would work like a charm. |
|
|
|
@Claymore I have a request. I've noticed that you have an auto restart option now when one of the GPUs stops talking to the miner. However, when the program restarts, it hangs at the POOL connection part (i'm mining in ETH only mode). What I usually have to do when I encounter this, is close the program, and then restart it manually, then it works. I have automated batch files to start your miner. Can you please add a command line switch which just quits the program rather than restarting it automatically when a GPU fails? Would be a huge help to me (and probably many others). I love your miner, and praise it on the eth forums. Much thanks  Already done via "-r 1" option, but it's not included in public release yet, it will be included in next update. This option closes miner and calls "reboot.bat" to reboot system, you can change reboot.bat so miner will just be closed (as if you use "-r -1") or do some other actions instead of reboot. I have just tested restarting by watchdog, it connects to a pool correctly after restarting, so I cannot reproduce the issue you describe. Actually miner just starts itself with the same command line, so I don't see any reasons why it can fail to connect to a pool after restarting. |
|
|
|
|
Today some Decred pools have problems, at least suprnova on dashboard page showed me a message about problems in their backend.
|
|
|
|
I tried to use -wd 1, but can't make it to close the miner tried -r -1 tried -r 0 When I mistype pool name (simulating dns /connectivity problem) it just keeps retrying to connect every 20sec, won't close the miner Watchdog closes/restarts miner only if GPU failed. I'm working on failover, will be added in a day. |
|
|
|
|
Show Posts
