Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..
did you update the AM?
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 428. (Read 703113 times)
February 01, 2018, 10:30:34 PM
February 01, 2018, 09:23:56 PM
for 24 hour profitability settings, why would you not set it to 1 minute or 5 minutes? It doesn't switch very often anyway. The problem I have with that at least on my system is it will basically just mine bitcore forever.
From my experience you need to be careful when selecting pools for this. AHashpool is most reliable in terms of not experiencing / showing crazy spikes, while zpool and MHP are the worst.
In my experience, ahashpool stats are totally misleding. I deactivated it from my profit switch.
I find all the values shown by AM misleading, they simply have absolutely no relation with the reality. I tried with 3 separate test rigs and with the same settings and same GPUs one shows $100/day and the the other shows that is it making $5/day.
It seems that statistics and profit that is shown are just random numbers.
PATRIKE, can you read it and explain why all profit values from AM are RANDOM NUMBERS ? It changes from one miner to another based on random numbers, nothing that has to do with reality or at least with the values from whattomine.com !!!
When I said the ahashpool numbers are misleading, I didnt say it was AM fault. It looks like ahashpool reports incorrect numbers.
February 01, 2018, 09:12:46 PM
Another vote for Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.
1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...
I have similar results with Excavator. We really need the latest version to be supported in AM.
I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.
some one have contact with excavator developers
?it's a good point to check
Well the right way is for AM to adapt to the changes. I doubt Excavator guys will start supporting an obsolete API.
February 01, 2018, 06:16:14 PM
Another vote for Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.
1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...
I have similar results with Excavator. We really need the latest version to be supported in AM.
I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.
some one have contact with excavator developers
?it's a good point to check
February 01, 2018, 05:48:06 PM
Another vote for Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.
1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...
I have similar results with Excavator. We really need the latest version to be supported in AM.
I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.
February 01, 2018, 03:40:10 PM
Another vote for Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.
1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
2. The best miner for my Radeon Vega cards (XMR-STAK) has only external mining support.
3. The statistics implementation needs help. For something like Nicehash, "current" stats work fine, as I am getting paid on a per-hash basis. However, on everything else I get jacked around far too often. That leaves a 24 hours as my only other option, which, given volatility of the alt-coin market is really far too long. MPM has a "stability" calculation that is better, and it essentially builds a real-time ongoing database of prices. My preference would be to implement an ability for us to do continuous sampling and apply our own math via the scripting function. I'd implement a EWMA and then play with the lambda until I was happy that I was able to usually mine coins that are either stable or increasing in value to match the TTF numbers so they get auto-exchanged for somewhere close to the value I supposedly mined them at.
Don't get me wrong, the program is better than others out there, but I can't say I am happy with it, and I don't think there would be too much trouble to implement a few of these. I'd be more than happy to help test solutions (or even contribute to coding) if it would speed things up a little.
February 01, 2018, 03:06:45 PM
Hi all from Awesome Miner,
I use the new version of Awesome miner but see some strange figures.
Is this a bug in the program?
See the green,red and blue lines
https://www.dropbox.com/sh/orvmmv8xzsf5a3j/AACfIN_uPFYz-D9g4V8SK6Tka?dl=0
I use the new version of Awesome miner but see some strange figures.
Is this a bug in the program?
See the green,red and blue lines
https://www.dropbox.com/sh/orvmmv8xzsf5a3j/AACfIN_uPFYz-D9g4V8SK6Tka?dl=0
February 01, 2018, 10:54:04 AM
Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..
did you update the AM? February 01, 2018, 10:50:01 AM
Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..
February 01, 2018, 10:48:45 AM
Hi, I am running a Awesome Miner 4.4 with claymore 10.6
I have a 6x1050Ti rig. I have overclocked it with +150/+500 with 75% TDP.
Whenever I start the Claymore Miner with overclocked settings, it fails to start.
Here is the log:
If I reset the overclock settings, and then start the miner, it starts mining, and then i can apply overclocking, and so it will continue mining with the improved hashrate.
But I cannot do this everytime the miner restarts.
Can anyone help with this? Thanks
I have a 6x1050Ti rig. I have overclocked it with +150/+500 with 75% TDP.
Whenever I start the Claymore Miner with overclocked settings, it fails to start.
Here is the log:
Code:
20:25:33:052 209c Check and remove old log files...
20:25:33:053 209c args: -platform 2 -mode 1 -wd 1 -r -1 -mport 4028 -allcoins 1
20:25:33:054 209c
20:25:33:055 209c ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:33:056 209c º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.6 º
20:25:33:057 209c ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:25:33:058 209c
20:25:33:058 209c b471
20:25:33:259 209c You enabled full remote management, but did not specify -mpsw option to protect it by password, please do it, otherwise you can be attacked if you share remote management port to internet! Or use negative -mport value to enable read-only remote management mode, see Readme for details.
20:25:38:264 209c ETH: 1 pool is specified
20:25:38:265 209c Main Ethereum pool is asia.ethash-hub.miningpoolhub.com:20536
20:25:38:716 209c CUDA initializing...
20:25:38:717 209c NVIDIA Cards available: 6
20:25:38:718 209c CUDA Driver Version/Runtime Version: 9.1/8.0
20:25:38:736 209c GPU #0: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 1:0:0)
20:25:38:738 209c GPU #1: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 2:0:0)
20:25:38:740 209c GPU #2: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 3:0:0)
20:25:38:741 209c GPU #3: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 5:0:0)
20:25:38:743 209c GPU #4: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 6:0:0)
20:25:38:745 209c GPU #5: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 7:0:0)
20:25:38:746 209c Total cards: 6
20:25:42:753 209c No AMD cards in the list, ADL library will not be used.
20:25:42:758 209c NVML version: 9.390.65
20:25:43:453 fe4 ETH: Stratum - connecting to 'asia.ethash-hub.miningpoolhub.com' <172.104.94.4> port 20536
20:25:43:532 209c ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
20:25:43:534 209c ETH: eth-proxy stratum mode
20:25:43:535 209c "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
20:25:43:536 209c Watchdog enabled
20:25:43:538 209c Remote management is enabled on port 4028
20:25:43:539 209c
20:25:43:593 fe4 send: {"worker": "Kishorthakkar.am", "jsonrpc": "2.0", "params": ["", "x"], "id": 2, "method": "eth_submitLogin"}
20:25:43:593 fe4 ETH: Stratum - Connected (asia.ethash-hub.miningpoolhub.com:20536)
20:25:43:733 fe4 got 39 bytes
20:25:43:733 fe4 buf: {"id":2,"jsonrpc":"2.0","result":true}
20:25:43:734 fe4 parse packet: 38
20:25:43:735 fe4 ETH: Authorized
20:25:43:737 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:25:43:737 fe4 new buf size: 0
20:25:43:874 fe4 got 243 bytes
20:25:43:875 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:25:43:875 fe4 parse packet: 242
20:25:43:876 fe4 ETH: job changed
20:25:43:877 fe4 new buf size: 0
20:25:43:943 1440 Setting DAG epoch #167...
20:25:46:091 21bc Setting DAG epoch #167 for GPU5
20:25:46:092 690 Setting DAG epoch #167 for GPU3
20:25:46:094 404 Setting DAG epoch #167 for GPU1
20:25:46:095 21bc Create GPU buffer for GPU5
20:25:46:090 1440 Setting DAG epoch #167 for GPU0
20:25:46:095 2378 Setting DAG epoch #167 for GPU4
20:25:46:098 690 Create GPU buffer for GPU3
20:25:46:101 1440 Create GPU buffer for GPU0
20:25:46:103 a24 Setting DAG epoch #167 for GPU2
20:25:46:104 404 Create GPU buffer for GPU1
20:25:46:110 2378 Create GPU buffer for GPU4
20:25:46:114 a24 Create GPU buffer for GPU2
20:25:49:008 2054 srv_thr cnt: 1, IP: 127.0.0.1
20:25:49:014 2054 recv: 51
20:25:49:016 2054 srv pck: 50
20:25:49:019 2054 srv bs: 0
20:25:49:020 2054 sent: 208
20:25:53:898 fe4 ETH: checking pool connection...
20:25:53:909 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:25:54:036 2144 srv_thr cnt: 1, IP: 127.0.0.1
20:25:54:037 2144 recv: 51
20:25:54:037 2144 srv pck: 50
20:25:54:040 2144 srv bs: 0
20:25:54:041 fe4 got 243 bytes
20:25:54:042 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:25:54:043 fe4 parse packet: 242
20:25:54:043 fe4 ETH: job is the same
20:25:54:044 fe4 new buf size: 0
20:25:54:046 2144 sent: 208
20:25:55:268 690 GPU 3, GpuMiner cu_kd failed 4 (11), unspecified launch failure
20:25:55:270 690 GPU 3, Calc DAG failed!
20:25:55:327 21bc GPU 5, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:450 1440 GPU 0, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:452 1440 GPU 0, Calc DAG failed!
20:25:55:544 2378 GPU 4, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:545 404 GPU 1, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:684 a24 GPU 2, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:694 a24 GPU 2, Calc DAG failed!
20:25:55:696 2378 GPU 4, Calc DAG failed!
20:25:55:699 404 GPU 1, Calc DAG failed!
20:25:55:713 21bc GPU 5, Calc DAG failed!
20:25:58:869 690 Set global fail flag, failed GPU3
20:25:58:872 690 GPU 3 failed
20:25:58:870 3ac Setting DAG epoch #167 for GPU3
20:25:58:874 3ac GPU 3, CUDA error 4 - cannot write buffer for DAG
20:25:59:045 1440 Set global fail flag, failed GPU0
20:25:59:045 9d0 Setting DAG epoch #167 for GPU0
20:25:59:051 9d0 GPU 0, CUDA error 4 - cannot write buffer for DAG
20:25:59:062 1440 GPU 0 failed
20:25:59:067 ddc srv_thr cnt: 1, IP: 127.0.0.1
20:25:59:076 ddc recv: 51
20:25:59:076 ddc srv pck: 50
20:25:59:079 ddc srv bs: 0
20:25:59:080 ddc sent: 208
20:25:59:197 a24 Set global fail flag, failed GPU2
20:25:59:198 19cc Setting DAG epoch #167 for GPU2
20:25:59:201 19cc GPU 2, CUDA error 4 - cannot write buffer for DAG
20:25:59:204 a24 GPU 2 failed
20:25:59:213 2378 Set global fail flag, failed GPU4
20:25:59:214 1a28 Setting DAG epoch #167 for GPU4
20:25:59:216 1a28 GPU 4, CUDA error 4 - cannot write buffer for DAG
20:25:59:218 2378 GPU 4 failed
20:25:59:214 404 Set global fail flag, failed GPU1
20:25:59:223 404 GPU 1 failed
20:25:59:225 15b8 Setting DAG epoch #167 for GPU1
20:25:59:226 15b8 GPU 1, CUDA error 4 - cannot write buffer for DAG
20:25:59:218 21bc Set global fail flag, failed GPU5
20:25:59:229 21bc GPU 5 failed
20:25:59:230 1d40 Setting DAG epoch #167 for GPU5
20:25:59:231 1d40 GPU 5, CUDA error 4 - cannot write buffer for DAG
20:26:01:875 3ac Set global fail flag, failed GPU3
20:26:01:876 3ac GPU 3 failed
20:26:02:063 9d0 Set global fail flag, failed GPU0
20:26:02:064 9d0 GPU 0 failed
20:26:02:204 19cc Set global fail flag, failed GPU2
20:26:02:205 19cc GPU 2 failed
20:26:02:219 1a28 Set global fail flag, failed GPU4
20:26:02:222 1a28 GPU 4 failed
20:26:02:228 15b8 Set global fail flag, failed GPU1
20:26:02:229 15b8 GPU 1 failed
20:26:02:235 1d40 Set global fail flag, failed GPU5
20:26:02:236 1d40 GPU 5 failed
20:26:03:884 fe4 send: {"id":6,"worker":"Kishorthakkar.am","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x0000000000000000000000000000000000000000000000000000000074222981"]}
20:26:03:916 fe4 ETH: checking pool connection...
20:26:03:917 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:26:04:019 fe4 got 39 bytes
20:26:04:019 fe4 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:26:04:019 fe4 parse packet: 38
20:26:04:020 fe4 new buf size: 0
20:26:04:096 788 srv_thr cnt: 1, IP: 127.0.0.1
20:26:04:096 788 recv: 51
20:26:04:097 788 srv pck: 50
20:26:04:099 788 srv bs: 0
20:26:04:101 788 sent: 208
20:26:04:149 fe4 got 243 bytes
20:26:04:150 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:26:04:151 fe4 parse packet: 242
20:26:04:153 fe4 ETH: job is the same
20:26:04:155 fe4 new buf size: 0
20:26:05:847 fe4 got 243 bytes
20:26:05:847 fe4 buf: {"id":0,"jsonrpc":"2.0","result":["0xcca0c35bf4cd033a1b1f8effd66769d52b01e504343fbed30f25abcfeed04d83","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:26:05:848 fe4 parse packet: 242
20:26:05:849 fe4 ETH: job changed
20:26:05:850 fe4 new buf size: 0
20:26:05:852 fe4 ETH: 02/01/18-20:26:05 - New job from asia.ethash-hub.miningpoolhub.com:20536
20:26:05:853 fe4 target: 0x00000000ffb34c02 (diff: 4300MH), epoch 167(2.30GB)
20:26:05:855 fe4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
20:26:05:856 fe4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
20:26:08:319 20d4 GPU0 t=38C fan=48%%, GPU1 t=42C fan=49%%, GPU2 t=38C fan=48%%, GPU3 t=43C fan=49%%, GPU4 t=43C fan=49%%, GPU5 t=40C fan=49%%
20:26:08:417 20bc em hbt: 0, fm hbt: 32,
20:26:08:418 20bc watchdog - thread 0 (gpu0), hb time 9188
20:26:08:418 20bc watchdog - thread 1 (gpu0), hb time 9188
20:26:08:419 20bc watchdog - thread 2 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 3 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 4 (gpu2), hb time 9188
20:26:08:421 20bc watchdog - thread 5 (gpu2), hb time 9188
20:26:08:422 20bc watchdog - thread 6 (gpu3), hb time 9188
20:26:08:422 20bc watchdog - thread 7 (gpu3), hb time 9188
20:26:08:423 20bc watchdog - thread 8 (gpu4), hb time 9188
20:26:08:423 20bc watchdog - thread 9 (gpu4), hb time 9188
20:26:08:424 20bc watchdog - thread 10 (gpu5), hb time 9188
20:26:08:425 20bc watchdog - thread 11 (gpu5), hb time 9188
20:26:08:426 20bc WATCHDOG: GPU error, you need to restart miner :(
20:25:33:053 209c args: -platform 2 -mode 1 -wd 1 -r -1 -mport 4028 -allcoins 1
20:25:33:054 209c
20:25:33:055 209c ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:33:056 209c º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.6 º
20:25:33:057 209c ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:25:33:058 209c
20:25:33:058 209c b471
20:25:33:259 209c You enabled full remote management, but did not specify -mpsw option to protect it by password, please do it, otherwise you can be attacked if you share remote management port to internet! Or use negative -mport value to enable read-only remote management mode, see Readme for details.
20:25:38:264 209c ETH: 1 pool is specified
20:25:38:265 209c Main Ethereum pool is asia.ethash-hub.miningpoolhub.com:20536
20:25:38:716 209c CUDA initializing...
20:25:38:717 209c NVIDIA Cards available: 6
20:25:38:718 209c CUDA Driver Version/Runtime Version: 9.1/8.0
20:25:38:736 209c GPU #0: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 1:0:0)
20:25:38:738 209c GPU #1: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 2:0:0)
20:25:38:740 209c GPU #2: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 3:0:0)
20:25:38:741 209c GPU #3: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 5:0:0)
20:25:38:743 209c GPU #4: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 6:0:0)
20:25:38:745 209c GPU #5: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 7:0:0)
20:25:38:746 209c Total cards: 6
20:25:42:753 209c No AMD cards in the list, ADL library will not be used.
20:25:42:758 209c NVML version: 9.390.65
20:25:43:453 fe4 ETH: Stratum - connecting to 'asia.ethash-hub.miningpoolhub.com' <172.104.94.4> port 20536
20:25:43:532 209c ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
20:25:43:534 209c ETH: eth-proxy stratum mode
20:25:43:535 209c "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
20:25:43:536 209c Watchdog enabled
20:25:43:538 209c Remote management is enabled on port 4028
20:25:43:539 209c
20:25:43:593 fe4 send: {"worker": "Kishorthakkar.am", "jsonrpc": "2.0", "params": ["", "x"], "id": 2, "method": "eth_submitLogin"}
20:25:43:593 fe4 ETH: Stratum - Connected (asia.ethash-hub.miningpoolhub.com:20536)
20:25:43:733 fe4 got 39 bytes
20:25:43:733 fe4 buf: {"id":2,"jsonrpc":"2.0","result":true}
20:25:43:734 fe4 parse packet: 38
20:25:43:735 fe4 ETH: Authorized
20:25:43:737 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:25:43:737 fe4 new buf size: 0
20:25:43:874 fe4 got 243 bytes
20:25:43:875 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:25:43:875 fe4 parse packet: 242
20:25:43:876 fe4 ETH: job changed
20:25:43:877 fe4 new buf size: 0
20:25:43:943 1440 Setting DAG epoch #167...
20:25:46:091 21bc Setting DAG epoch #167 for GPU5
20:25:46:092 690 Setting DAG epoch #167 for GPU3
20:25:46:094 404 Setting DAG epoch #167 for GPU1
20:25:46:095 21bc Create GPU buffer for GPU5
20:25:46:090 1440 Setting DAG epoch #167 for GPU0
20:25:46:095 2378 Setting DAG epoch #167 for GPU4
20:25:46:098 690 Create GPU buffer for GPU3
20:25:46:101 1440 Create GPU buffer for GPU0
20:25:46:103 a24 Setting DAG epoch #167 for GPU2
20:25:46:104 404 Create GPU buffer for GPU1
20:25:46:110 2378 Create GPU buffer for GPU4
20:25:46:114 a24 Create GPU buffer for GPU2
20:25:49:008 2054 srv_thr cnt: 1, IP: 127.0.0.1
20:25:49:014 2054 recv: 51
20:25:49:016 2054 srv pck: 50
20:25:49:019 2054 srv bs: 0
20:25:49:020 2054 sent: 208
20:25:53:898 fe4 ETH: checking pool connection...
20:25:53:909 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:25:54:036 2144 srv_thr cnt: 1, IP: 127.0.0.1
20:25:54:037 2144 recv: 51
20:25:54:037 2144 srv pck: 50
20:25:54:040 2144 srv bs: 0
20:25:54:041 fe4 got 243 bytes
20:25:54:042 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:25:54:043 fe4 parse packet: 242
20:25:54:043 fe4 ETH: job is the same
20:25:54:044 fe4 new buf size: 0
20:25:54:046 2144 sent: 208
20:25:55:268 690 GPU 3, GpuMiner cu_kd failed 4 (11), unspecified launch failure
20:25:55:270 690 GPU 3, Calc DAG failed!
20:25:55:327 21bc GPU 5, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:450 1440 GPU 0, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:452 1440 GPU 0, Calc DAG failed!
20:25:55:544 2378 GPU 4, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:545 404 GPU 1, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:684 a24 GPU 2, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:694 a24 GPU 2, Calc DAG failed!
20:25:55:696 2378 GPU 4, Calc DAG failed!
20:25:55:699 404 GPU 1, Calc DAG failed!
20:25:55:713 21bc GPU 5, Calc DAG failed!
20:25:58:869 690 Set global fail flag, failed GPU3
20:25:58:872 690 GPU 3 failed
20:25:58:870 3ac Setting DAG epoch #167 for GPU3
20:25:58:874 3ac GPU 3, CUDA error 4 - cannot write buffer for DAG
20:25:59:045 1440 Set global fail flag, failed GPU0
20:25:59:045 9d0 Setting DAG epoch #167 for GPU0
20:25:59:051 9d0 GPU 0, CUDA error 4 - cannot write buffer for DAG
20:25:59:062 1440 GPU 0 failed
20:25:59:067 ddc srv_thr cnt: 1, IP: 127.0.0.1
20:25:59:076 ddc recv: 51
20:25:59:076 ddc srv pck: 50
20:25:59:079 ddc srv bs: 0
20:25:59:080 ddc sent: 208
20:25:59:197 a24 Set global fail flag, failed GPU2
20:25:59:198 19cc Setting DAG epoch #167 for GPU2
20:25:59:201 19cc GPU 2, CUDA error 4 - cannot write buffer for DAG
20:25:59:204 a24 GPU 2 failed
20:25:59:213 2378 Set global fail flag, failed GPU4
20:25:59:214 1a28 Setting DAG epoch #167 for GPU4
20:25:59:216 1a28 GPU 4, CUDA error 4 - cannot write buffer for DAG
20:25:59:218 2378 GPU 4 failed
20:25:59:214 404 Set global fail flag, failed GPU1
20:25:59:223 404 GPU 1 failed
20:25:59:225 15b8 Setting DAG epoch #167 for GPU1
20:25:59:226 15b8 GPU 1, CUDA error 4 - cannot write buffer for DAG
20:25:59:218 21bc Set global fail flag, failed GPU5
20:25:59:229 21bc GPU 5 failed
20:25:59:230 1d40 Setting DAG epoch #167 for GPU5
20:25:59:231 1d40 GPU 5, CUDA error 4 - cannot write buffer for DAG
20:26:01:875 3ac Set global fail flag, failed GPU3
20:26:01:876 3ac GPU 3 failed
20:26:02:063 9d0 Set global fail flag, failed GPU0
20:26:02:064 9d0 GPU 0 failed
20:26:02:204 19cc Set global fail flag, failed GPU2
20:26:02:205 19cc GPU 2 failed
20:26:02:219 1a28 Set global fail flag, failed GPU4
20:26:02:222 1a28 GPU 4 failed
20:26:02:228 15b8 Set global fail flag, failed GPU1
20:26:02:229 15b8 GPU 1 failed
20:26:02:235 1d40 Set global fail flag, failed GPU5
20:26:02:236 1d40 GPU 5 failed
20:26:03:884 fe4 send: {"id":6,"worker":"Kishorthakkar.am","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x0000000000000000000000000000000000000000000000000000000074222981"]}
20:26:03:916 fe4 ETH: checking pool connection...
20:26:03:917 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:26:04:019 fe4 got 39 bytes
20:26:04:019 fe4 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:26:04:019 fe4 parse packet: 38
20:26:04:020 fe4 new buf size: 0
20:26:04:096 788 srv_thr cnt: 1, IP: 127.0.0.1
20:26:04:096 788 recv: 51
20:26:04:097 788 srv pck: 50
20:26:04:099 788 srv bs: 0
20:26:04:101 788 sent: 208
20:26:04:149 fe4 got 243 bytes
20:26:04:150 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:26:04:151 fe4 parse packet: 242
20:26:04:153 fe4 ETH: job is the same
20:26:04:155 fe4 new buf size: 0
20:26:05:847 fe4 got 243 bytes
20:26:05:847 fe4 buf: {"id":0,"jsonrpc":"2.0","result":["0xcca0c35bf4cd033a1b1f8effd66769d52b01e504343fbed30f25abcfeed04d83","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}
20:26:05:848 fe4 parse packet: 242
20:26:05:849 fe4 ETH: job changed
20:26:05:850 fe4 new buf size: 0
20:26:05:852 fe4 ETH: 02/01/18-20:26:05 - New job from asia.ethash-hub.miningpoolhub.com:20536
20:26:05:853 fe4 target: 0x00000000ffb34c02 (diff: 4300MH), epoch 167(2.30GB)
20:26:05:855 fe4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
20:26:05:856 fe4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
20:26:08:319 20d4 GPU0 t=38C fan=48%%, GPU1 t=42C fan=49%%, GPU2 t=38C fan=48%%, GPU3 t=43C fan=49%%, GPU4 t=43C fan=49%%, GPU5 t=40C fan=49%%
20:26:08:417 20bc em hbt: 0, fm hbt: 32,
20:26:08:418 20bc watchdog - thread 0 (gpu0), hb time 9188
20:26:08:418 20bc watchdog - thread 1 (gpu0), hb time 9188
20:26:08:419 20bc watchdog - thread 2 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 3 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 4 (gpu2), hb time 9188
20:26:08:421 20bc watchdog - thread 5 (gpu2), hb time 9188
20:26:08:422 20bc watchdog - thread 6 (gpu3), hb time 9188
20:26:08:422 20bc watchdog - thread 7 (gpu3), hb time 9188
20:26:08:423 20bc watchdog - thread 8 (gpu4), hb time 9188
20:26:08:423 20bc watchdog - thread 9 (gpu4), hb time 9188
20:26:08:424 20bc watchdog - thread 10 (gpu5), hb time 9188
20:26:08:425 20bc watchdog - thread 11 (gpu5), hb time 9188
20:26:08:426 20bc WATCHDOG: GPU error, you need to restart miner :(
If I reset the overclock settings, and then start the miner, it starts mining, and then i can apply overclocking, and so it will continue mining with the improved hashrate.
But I cannot do this everytime the miner restarts.
Can anyone help with this? Thanks
February 01, 2018, 09:29:49 AM
There is a run profit switch action in rules. Does the HTTP API also support this?
February 01, 2018, 08:58:30 AM
Another vote for Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.
February 01, 2018, 08:26:50 AM
I'm interested in Excavator new versions as well 
Could be possible to update it, please?
Could be possible to update it, please?
February 01, 2018, 07:15:52 AM
Hi guys.
Does this program support EWBF miner?
Does this program support EWBF miner?
Yes, it's built in.
Quote
If so, is there any guide how to set it up ?
You don't need to set it up. AM will set the command line correctly. You just need to define a pool, a miner, and then tell the miner to use EWBF on that pool. AM does all the work from there.
Quote
Is this program heavy on resources ? CPU/memory/GPU
Thanks!!!
Thanks!!!
Not especially, no. I run it on a simple virtual machine on one of my low-end vmware nodes. The node has a low-end Athlon 5350 CPU. I gave the VM two cores and 4GB of RAM. It runs fine... runs an average of 15% CPU on that piddly VM with the resources given to it.
Ok perfect. And please tell me, is there any decrease of Sols when using AM ? I want to stay at max Sols obviously. Thanks!
February 01, 2018, 07:00:43 AM
Hi guys.
Does this program support EWBF miner?
Does this program support EWBF miner?
Yes, it's built in.
Quote
If so, is there any guide how to set it up ?
You don't need to set it up. AM will set the command line correctly. You just need to define a pool, a miner, and then tell the miner to use EWBF on that pool. AM does all the work from there.
Quote
Is this program heavy on resources ? CPU/memory/GPU
Thanks!!!
Thanks!!!
Not especially, no. I run it on a simple virtual machine on one of my low-end vmware nodes. The node has a low-end Athlon 5350 CPU. I gave the VM two cores and 4GB of RAM. It runs fine... runs an average of 15% CPU on that piddly VM with the resources given to it.
Ok perfect. And please tell me, is there any decrease of Sols when using AM ? I want to stay at max Sols obviously. Thanks!
February 01, 2018, 05:49:31 AM
I've never encouraged this error before:
I relocated S9 farm, changed the LAN subnet and added all miners again to the awesomeminer, I connected to all of them (old batches) except of two (new batches), I did try everything I could find in config and properties but with 0 luck, I know I'm missing the simple config or something like that,
any help would be much appreciated
Code:
Connection aborted by the remote computer.
I relocated S9 farm, changed the LAN subnet and added all miners again to the awesomeminer, I connected to all of them (old batches) except of two (new batches), I did try everything I could find in config and properties but with 0 luck, I know I'm missing the simple config or something like that,
any help would be much appreciated
Are all the S9s on the same subnet as the computer that runs AM? Are there any conflicting IPs?
February 01, 2018, 05:39:24 AM
Hi Folks.
My setup is up and running and i have 2 more questions:
Question 1:
Is it possible to extend the web interface of Awesome Miner to include windowsUptime in the overview? I have seen that it is mininal js, but i am not an expert in that. But as I can see that information ithe "summary-section" of any miner, the information is available and it shouldnt be to much hussle to modify the web page in the miner overview to show that information as well.
Question 2:
My Rigs did went offline because the miner software tried to restart several time without success, however, I have not seen a rule that is causing that entry. So where is it configured that we are trying to restart the service and stop trying after X attemps? My solution is a manual rule to restart the entire rig in case we exceed the miner software restart option threshold. But I would like to extend the current rule (if it is a rule), which is logging that we exceeded the threshold with an restart rather than creating a manual job. So, where can i find that rule?
chaosphysik
@moppidoo : Thanks for your reply.
My setup is up and running and i have 2 more questions:
Question 1:
Is it possible to extend the web interface of Awesome Miner to include windowsUptime in the overview? I have seen that it is mininal js, but i am not an expert in that. But as I can see that information ithe "summary-section" of any miner, the information is available and it shouldnt be to much hussle to modify the web page in the miner overview to show that information as well.
Question 2:
My Rigs did went offline because the miner software tried to restart several time without success, however, I have not seen a rule that is causing that entry. So where is it configured that we are trying to restart the service and stop trying after X attemps? My solution is a manual rule to restart the entire rig in case we exceed the miner software restart option threshold. But I would like to extend the current rule (if it is a rule), which is logging that we exceeded the threshold with an restart rather than creating a manual job. So, where can i find that rule?
chaosphysik
@moppidoo : Thanks for your reply.
February 01, 2018, 03:02:49 AM
A bug when miner gets disconnected from the pool.
Sometimes when pools have too many connections they disable new connections for a period of time to a specific algo. In this case AM remains stucked with the last value AM received from the mining instance of ccminer and does nothing to fix that.
I believe it would be better to show income statistics based on submitted (and also accepted shares) , instead AM not remains without any refresh to the last hash rate that was submitted by ccminer even hours ago.
If AM waits for hours for an updated hashrate from ccminer and does not take time into consideration it is not the correct behavior. It should have a timer that checks every x seconds the received hashrate from the miner, with one minute delay when miner is started to allow all GPUs to be started and send hash rates. Like this if one pool / algo server is offline, it will change to the next most profitable algo from the list.
Did anyone tried to find a solution to this problem ?
Sometimes when pools have too many connections they disable new connections for a period of time to a specific algo. In this case AM remains stucked with the last value AM received from the mining instance of ccminer and does nothing to fix that.
I believe it would be better to show income statistics based on submitted (and also accepted shares) , instead AM not remains without any refresh to the last hash rate that was submitted by ccminer even hours ago.
If AM waits for hours for an updated hashrate from ccminer and does not take time into consideration it is not the correct behavior. It should have a timer that checks every x seconds the received hashrate from the miner, with one minute delay when miner is started to allow all GPUs to be started and send hash rates. Like this if one pool / algo server is offline, it will change to the next most profitable algo from the list.
Did anyone tried to find a solution to this problem ?
January 31, 2018, 11:10:51 PM
When one tweaks the profit option for Time and Percentages does Time stand for the minimum amount of time AM will allow the rig to stay on its last job (whatever pool/algo it was on) What happens after the time lapses? it will redirect ONLY if there is something offering a profit greater than the %percentage that is set?
Yes, you got it mostly. The time is just the amount of time that will pass before AM re-calculates "best coin or algo" profit values from the statistics it gets from either Whattomine (if you are mining individual pools or pool groups)... or it rechecks the enabled Online Services that you have enabled on profit miners. If you are mining individual pools or pool groups, there is also another time setting to pay attention to on the Statistics tab in the Options. That time setting is how often AM will check Whattomine or Coinwarz for updated statistics.
Quote
I dont fully follow when some of the posts talk about setting the values so that your rig doesnt jump around too often but yet doesnt miss out on the peaks?
If I understood how it worked a little more I could possibly run some tests with that idea in mind to see whats best.
The more I read the more I retain (although its in small bits)
Thanks for your help so far gents
If I understood how it worked a little more I could possibly run some tests with that idea in mind to see whats best.
The more I read the more I retain (although its in small bits)
Thanks for your help so far gents
I'll just requote what I wrote a few weeks (and a few pages) back:
Quote from: puwaha
Let's say you switch to mine a coin that has a 2 minute block time on say Zpool. You mine your share, and you get a percentage of the reward for that block. But now, you have to wait for say 10 confirmations to mature before it's sent to the exchange. That's now 20 minutes you are waiting for the coin to mature before it gets sent to the exchange. Now, let's say it's a mildly popular coin, and it's gets sent to the exchange... minimum 2 minutes of that coin's block time if Zpool has enough of that coin built up to make it worth their while to send to the exchange. We are up to 22 minutes. That transaction is going to take another 10 confirmations before the exchange makes it available to trade. We are now up to 42 minutes.
What are the chances that your coin is worth the same amount when you started mining it until it reaches the point where it can be traded on the exchange 42 minutes later? Not very likely. There are thousands and thousands of miners that use auto-switching algorithms and were mining the same coin you thought was hot in that moment. That shoots up the difficulty, and the massive dump on the exchange(s) sends the value of the coin down.
A 24 hour profitability evens out those nuances, and I would even argue that a longer period is necessary. You want to be mining a coin that is consistently in the top spot... not in the moment.
But, this is my opinion... there are other perspectives.
January 31, 2018, 10:59:08 PM
I've never encouraged this error before:
I relocated S9 farm, changed the LAN subnet and added all miners again to the awesomeminer, I connected to all of them (old batches) except of two (new batches), I did try everything I could find in config and properties but with 0 luck, I know I'm missing the simple config or something like that,
any help would be much appreciated
Code:
Connection aborted by the remote computer.
I relocated S9 farm, changed the LAN subnet and added all miners again to the awesomeminer, I connected to all of them (old batches) except of two (new batches), I did try everything I could find in config and properties but with 0 luck, I know I'm missing the simple config or something like that,
any help would be much appreciated
Are all the S9s on the same subnet as the computer that runs AM? Are there any conflicting IPs?
Jump to: