Jaerin
|
|
December 09, 2017, 07:19:23 PM |
|
You were correct STSMiner.... After changing the switching interval and the profit switching threshold, I am now seeing what I consider normal functionality. _________ New Question: Are any you using zpool and noticing you are not getting paid anywhere close to what Awesome Miner is saying you are earning? I mined all day and night with my test rig, and Awesome Miner was reporting a profit from $6/day to $18/day.... But on the zpool wallet page, it shows I have earned $3 in bitcoin. There has been a long time speculation that there is something causing 20% loss of earnings in the exchange process. I discovered that the AverageIncrement function used to create a rolling average of the prices on the exchanges could return 80% of the input values if either of the inputs were 0. I've submitted a bug fix to the Yiimp git, but it has not been accepted yet. Ahashpool.com has implemented the bug fix long ago and I have found that it pays out much better than Zpool. The one drawback is that it does not have near the same number of algorithms and coins available. Specifically the Equihash implementation in Yiimp is private and not shared publicly. Zpool does still pay out better than what Nicehash used too, but there is an obvious bug that continues to go unfixed. There is a thread where evidence was presented that clearly showed that the exchange rates being given on mined coins was always 15-20% below the expected value at the time of payout. Its a hard discussion to win because everyone seems to doubt the validity and chalks up the evidence as somehow doctored or could be explained away by exchange price fluctuations. Hopefully Crackfoo comes to his senses and implements the bug fix. In fact I think people would be fine paying a 5-10% exchange fee if he were transparent about it. It costs money to run a pool and I don't think anyone expects him to do it for free.
|
|
|
|
aussiegwapo
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 09, 2017, 07:21:17 PM |
|
You were correct STSMiner.... After changing the switching interval and the profit switching threshold, I am now seeing what I consider normal functionality. _________ New Question: Are any you using zpool and noticing you are not getting paid anywhere close to what Awesome Miner is saying you are earning? I mined all day and night with my test rig, and Awesome Miner was reporting a profit from $6/day to $18/day.... But on the zpool wallet page, it shows I have earned $3 in bitcoin. There has been a long time speculation that there is something causing 20% loss of earnings in the exchange process. I discovered that the AverageIncrement function used to create a rolling average of the prices on the exchanges could return 80% of the input values if either of the inputs were 0. I've submitted a bug fix to the Yiimp git, but it has not been accepted yet. Ahashpool.com has implemented the bug fix long ago and I have found that it pays out much better than Zpool. The one drawback is that it does not have near the same number of algorithms and coins available. Specifically the Equihash implementation in Yiimp is private and not shared publicly. Zpool does still pay out better than what Nicehash used too, but there is an obvious bug that continues to go unfixed. There is a thread where evidence was presented that clearly showed that the exchange rates being given on mined coins was always 15-20% below the expected value at the time of payout. Its a hard discussion to win because everyone seems to doubt the validity and chalks up the evidence as somehow doctored or could be explained away by exchange price fluctuations. Hopefully Crackfoo comes to his senses and implements the bug fix. In fact I think people would be fine paying a 5-10% exchange fee if he were transparent about it. It costs money to run a pool and I don't think anyone expects him to do it for free. its on all pools i have noticed also on miningpoolhub the same thing
|
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
December 09, 2017, 07:22:47 PM |
|
Feature request: If you're running multiple mining software for multiagos, example, EWBF and ccminer, and using the same port, allow the external miners to be able to reference APIs from both platforms. Obviously when EWBF is running, CC isn't and when CC is running EWBF is running but the disconnect stuff is getting old, even with adjusting the timeouts. Right now it's bastardized in that I have two external rigs for each piece of mining software where half of them are always disconnected (due to the other miner running) and then there still seems to be issues with the API dropping off on the rigs referencing the mining software currently hashing.
Unless of course there is a better way of managing multiple pieces of mining software per rig. It would be nice to have a consistent earnings estimate instead of being a mere fraction of what I am running due to the rigs showing up as disconnected (however, if you go into properties of each rig and test the connection, it shows as successful).
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3556
Merit: 1126
|
|
December 09, 2017, 07:29:53 PM |
|
Patrike,
Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view. The zpool instructions have always been a bit unclear on this. -o stratum+tcp://<algo>.mine.zpool.ca:<PORT> -u <WALLET_ADDRESS> [-p c=<SYMBOL>,<OPTIONS>] <WALLET_ADDRESS> must be a valid address. Incorrect addresses will result in forfit of earning. You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario. You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar). Further reading on zpool instructions: c=<SYMBOL> doesn't always work This is yet another reason why Awesome Miner isn't trying to set this parameter at all. Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set.
|
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
s3c70r
Member
Offline
Activity: 83
Merit: 10
|
|
December 09, 2017, 07:33:12 PM |
|
Hi Patrike,
I can't run ccMiner2.2.2 from AwesomeMiner because AM doesn't give enough time to ccMiner to initialize and thinks the API port is down.
If I run it from command line manually I have no issue.
Can you please check if increasing the API time out value could fix the issue ?
2017-12-09 2:25:50 PM.554 [010] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:50 PM.554 [011] [I2]Done processing: 1, Time: 1031 ms 2017-12-09 2:25:51 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:52 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:53 PM.586 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=14;TS=1512847553| 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:53 PM.586 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:53 PM.586 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:54 PM.602 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:55 PM.602 [009] [ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] : ProcessMiner 2017-12-09 2:25:55 PM.603 [009] Execute API, Hostname: 192.168.0.25:4028, Command: summary 2017-12-09 2:25:56 PM.608 [009] [E]Failed to process API request (time: 1005 ms): summary No connection could be made because the target machine actively refused it 127.0.0.1:4028 2017-12-09 2:25:56 PM.608 [009] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:56 PM.608 [011] [I2]Done processing: 1, Time: 1005 ms 2017-12-09 2:25:57 PM.609 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:58 PM.610 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=19;TS=1512847558| 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:58 PM.610 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:58 PM.610 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:59 PM.626 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:59 PM.798 [008] [W][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] process not running. Restarting...
|
|
|
|
patrike (OP)
Legendary
Offline
Activity: 3500
Merit: 1095
|
|
December 09, 2017, 08:05:20 PM |
|
Does anyone else have problems with benchmarking? I'm trying to run the benchmarks, but the miner keeps telling me there's no pool added. I can mine just fine if I press Start, but the benchmarks can't find any pool.
I've even followed the guide to add your own algorithm to benchmark, and it still can't find it.
Only tried with CryptoNight so far. Anyone got any ideas?
" No pool specified. Add at least one valid pool using the -xpool parameter "
You must have missed a setting. Profit Switching Profiles also need to be checked as well as the mining software. http://www.awesomeminer.com/help/profitswitching.aspx << See the section -- Profit Switching Profile Properties http://www.awesomeminer.com/help/benchmark.aspxAlso check to see what pools have been enabled. Configuration section >> http://www.awesomeminer.com/help/profitswitching.aspxYeah, I thought so too. I've checked and double checked everything now. I even did a clean install on both systems, and I just can't get it to find the pool when I'm benchmarking. It finds it just fine if I just press Start. It'll happily start mining away. I find it really odd that it would be different when benchmarking like this. Right click the miner and do a diagnostic check and post the results here (remove your wallet address before you post it). I appreciate the help. Thanks. Starting Diagnostics Starting Mining Software Setting up Miner Engine. Instance: 1 Engine Type: SgMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: Added rule for: C:\Users\Worker2\AppData\Roaming\AwesomeMinerService\sgminer-5.6.1-nicehash-51-windows-i386_1\sgminer.exe C:\Users\Worker2\AppData\Roaming\AwesomeMinerService\sgminer-5.6.1-nicehash-51-windows-i386_1\sgminer.exe --config awesome.conf --text-only --algorithm groestlcoin (WindowMode: ConsoleFormat, EngineType: SgMiner, IsProfitMiner: True)
... Thanks for sharing. It looks like this one was hashing perfectly fine. Do you still experience issues? That's the thing, it hashes just fine when I start it. I just can't benchmark the cards, so they will just start mining the coin that seems most profitable according to the (very very wrong) existing hash/s numbers, so the profit switching is useless for me since it'll switch between three coins that are 100% worthless for me to mine ( 2-3 cents per day profit ) and skip the ones such as CryptoNight that would actually make me money. I've solved it for now by force-running each algo by itself and then saving the hash-values per card. It takes abssolutely forever though, so it's kind of a deal killer for me atm. I'm not gonna go through that process on 200+ cards. It seems to me ( might be wrong ) that it's just not sending the command line arguments when starting the miner for a benchmark. I'm not sure if it's something I've configured in a wonky manner or if it's a legit bug though. I made one correction in version 4.2.4 related to benchmarking, so can you try that one as well? Also, I assume you don't have 200 different GPU models? As you probably know, you only need to benchmark (or save hashrate manually) once per GPU model. All of the same model/performance should be using the same Profit profile.
|
Awesome Miner - Complete solution to manage and monitor mining operations of ASIC, GPU and CPU miners Optimized Antminer firmware - Increased hashrate, improved power efficiency and more features. For S9, S9i, S9j, T9+, L3+, S17, S17 Pro, S17+, T17, T17+, S19, S19 Pro, S19j, S19j Pro, T19 Up to 200,000 miners | Notifications | Native overclocking | Profit switching | Customizable rules | API | Windows application | Mobile web
|
|
|
patrike (OP)
Legendary
Offline
Activity: 3500
Merit: 1095
|
|
December 09, 2017, 08:08:27 PM |
|
Hi Patrike,
I can't run ccMiner2.2.2 from AwesomeMiner because AM doesn't give enough time to ccMiner to initialize and thinks the API port is down.
If I run it from command line manually I have no issue.
Can you please check if increasing the API time out value could fix the issue ?
2017-12-09 2:25:50 PM.554 [010] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:50 PM.554 [011] [I2]Done processing: 1, Time: 1031 ms 2017-12-09 2:25:51 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:52 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:53 PM.586 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=14;TS=1512847553| 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:53 PM.586 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:53 PM.586 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:54 PM.602 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:55 PM.602 [009] [ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] : ProcessMiner 2017-12-09 2:25:55 PM.603 [009] Execute API, Hostname: 192.168.0.25:4028, Command: summary 2017-12-09 2:25:56 PM.608 [009] [E]Failed to process API request (time: 1005 ms): summary No connection could be made because the target machine actively refused it 127.0.0.1:4028 2017-12-09 2:25:56 PM.608 [009] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:56 PM.608 [011] [I2]Done processing: 1, Time: 1005 ms 2017-12-09 2:25:57 PM.609 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:58 PM.610 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=19;TS=1512847558| 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:58 PM.610 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:58 PM.610 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:59 PM.626 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:59 PM.798 [008] [W][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] process not running. Restarting...
Your question is about Ccminer, but the output here indicates CpuMiner. Also, the message about "process not running" is not checking the API at all. It only check if the process has crashed (process all of a sudden not running anymore). Could this be a crash?
|
Awesome Miner - Complete solution to manage and monitor mining operations of ASIC, GPU and CPU miners Optimized Antminer firmware - Increased hashrate, improved power efficiency and more features. For S9, S9i, S9j, T9+, L3+, S17, S17 Pro, S17+, T17, T17+, S19, S19 Pro, S19j, S19j Pro, T19 Up to 200,000 miners | Notifications | Native overclocking | Profit switching | Customizable rules | API | Windows application | Mobile web
|
|
|
patrike (OP)
Legendary
Offline
Activity: 3500
Merit: 1095
|
|
December 09, 2017, 08:12:09 PM |
|
Patrike,
Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view. The zpool instructions have always been a bit unclear on this. -o stratum+tcp://<algo>.mine.zpool.ca:<PORT> -u <WALLET_ADDRESS> [-p c=<SYMBOL>,<OPTIONS>] <WALLET_ADDRESS> must be a valid address. Incorrect addresses will result in forfit of earning. You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario. You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar). Further reading on zpool instructions: c=<SYMBOL> doesn't always work This is yet another reason why Awesome Miner isn't trying to set this parameter at all. Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set. Isn't the assumption that if c-parameter isn't set, it's always Bitcoin? Why simply not detect empty and use Bitcoin? That must be the most stable solution that would solve all scenarios no matter if Awesome Miner is used or not, and if Awesome Miner is configured explictly for this, or not? Especially given that it looks like c-parameter isn't always working and "at your own risk" according to the instructions above. Please let me know and we can agree on the best way forward. Many thanks!
|
Awesome Miner - Complete solution to manage and monitor mining operations of ASIC, GPU and CPU miners Optimized Antminer firmware - Increased hashrate, improved power efficiency and more features. For S9, S9i, S9j, T9+, L3+, S17, S17 Pro, S17+, T17, T17+, S19, S19 Pro, S19j, S19j Pro, T19 Up to 200,000 miners | Notifications | Native overclocking | Profit switching | Customizable rules | API | Windows application | Mobile web
|
|
|
patrike (OP)
Legendary
Offline
Activity: 3500
Merit: 1095
|
|
December 09, 2017, 08:16:23 PM |
|
HELP I'be been rolling along for months using AM and now apparently typoed or set a value too low for an auto reboot rule. I have a rig that reboots the second AM opens. I tried uninstalling AM, rebooting, then reinstalled and the profile/rules are all still saved. Do you know where the rules are saved locally? Or better yet, is there a way to launch AM with rules disabled? Open the folder %appdata%\AwesomeMiner in the Windows File Explorer and modify ConfigData.xml. You should find the rules in XML format here and it should be some Enabled flag you can change from true to false.
|
Awesome Miner - Complete solution to manage and monitor mining operations of ASIC, GPU and CPU miners Optimized Antminer firmware - Increased hashrate, improved power efficiency and more features. For S9, S9i, S9j, T9+, L3+, S17, S17 Pro, S17+, T17, T17+, S19, S19 Pro, S19j, S19j Pro, T19 Up to 200,000 miners | Notifications | Native overclocking | Profit switching | Customizable rules | API | Windows application | Mobile web
|
|
|
s3c70r
Member
Offline
Activity: 83
Merit: 10
|
|
December 09, 2017, 08:21:34 PM |
|
Hi Patrike,
I can't run ccMiner2.2.2 from AwesomeMiner because AM doesn't give enough time to ccMiner to initialize and thinks the API port is down.
If I run it from command line manually I have no issue.
Can you please check if increasing the API time out value could fix the issue ?
2017-12-09 2:25:50 PM.554 [010] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:50 PM.554 [011] [I2]Done processing: 1, Time: 1031 ms 2017-12-09 2:25:51 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:52 PM.570 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:53 PM.586 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=14;TS=1512847553| 2017-12-09 2:25:53 PM.586 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:53 PM.586 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:53 PM.586 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:53 PM.586 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:54 PM.602 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:55 PM.602 [009] [ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] : ProcessMiner 2017-12-09 2:25:55 PM.603 [009] Execute API, Hostname: 192.168.0.25:4028, Command: summary 2017-12-09 2:25:56 PM.608 [009] [E]Failed to process API request (time: 1005 ms): summary No connection could be made because the target machine actively refused it 127.0.0.1:4028 2017-12-09 2:25:56 PM.608 [009] [I2][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:56 PM.608 [011] [I2]Done processing: 1, Time: 1005 ms 2017-12-09 2:25:57 PM.609 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:58 PM.610 [015] [ManagedMiner#74 - Rig05 - i3-7100 - 8GB] : ProcessMiner 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: summary 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): NAME=cpuminer-opt;VER=3.7.3;API=1.0;ALGO=scrypt;CPUS=3;KHS=0.00;ACC=0;REJ=0;ACCMN=0.000;DIFF=0.009558;TEMP=0.0;FAN=0;FREQ=0;UPTIME=19;TS=1512847558| 2017-12-09 2:25:58 PM.610 [015] Execute API, Hostname: 192.168.0.25:4029, Command: threads 2017-12-09 2:25:58 PM.610 [015] [I2]API result (time: 0 ms): CPU=0;KHS=0.00|CPU=1;KHS=0.00|CPU=2;KHS=0.00| 2017-12-09 2:25:58 PM.610 [015] [I2][ManagedMiner#74 - Rig05 - i3-7100 - 8GB] TriggerControlStateChanged, ControlState: Executing 2017-12-09 2:25:58 PM.610 [011] [I2]Done processing: 1, Time: 0 ms 2017-12-09 2:25:59 PM.626 [011] [I2]Done processing: 0, Time: 0 ms 2017-12-09 2:25:59 PM.798 [008] [W][ManagedMiner#73 - Rig05 - 18 x Colorful P106-100 6GB] process not running. Restarting...
Your question is about Ccminer, but the output here indicates CpuMiner. Also, the message about "process not running" is not checking the API at all. It only check if the process has crashed (process all of a sudden not running anymore). Could this be a crash? My bad sorry. Yes, since I've posted and investigate a bit more I'm pretty sure it's a crash. Thanks for looking into it !
|
|
|
|
tf2addict
|
|
December 09, 2017, 08:32:49 PM |
|
Is there a way to have AM reboot a rig for a miner restart rather than just restarting the miner program? That would temporarily work around the Cast shutdown issue.
|
|
|
|
s3c70r
Member
Offline
Activity: 83
Merit: 10
|
|
December 09, 2017, 08:44:58 PM |
|
Is there a way to have AM reboot a rig for a miner restart rather than just restarting the miner program? That would temporarily work around the Cast shutdown issue.
Look in the rules. Action section of a rule. Add --> Miner Command --> Reboot Computer.
|
|
|
|
puwaha
|
|
December 10, 2017, 01:27:44 AM |
|
You were correct STSMiner.... After changing the switching interval and the profit switching threshold, I am now seeing what I consider normal functionality. _________ New Question: Are any you using zpool and noticing you are not getting paid anywhere close to what Awesome Miner is saying you are earning? I mined all day and night with my test rig, and Awesome Miner was reporting a profit from $6/day to $18/day.... But on the zpool wallet page, it shows I have earned $3 in bitcoin. There has been a long time speculation that there is something causing 20% loss of earnings in the exchange process. I discovered that the AverageIncrement function used to create a rolling average of the prices on the exchanges could return 80% of the input values if either of the inputs were 0. I've submitted a bug fix to the Yiimp git, but it has not been accepted yet. Ahashpool.com has implemented the bug fix long ago and I have found that it pays out much better than Zpool. The one drawback is that it does not have near the same number of algorithms and coins available. Specifically the Equihash implementation in Yiimp is private and not shared publicly. Zpool does still pay out better than what Nicehash used too, but there is an obvious bug that continues to go unfixed. There is a thread where evidence was presented that clearly showed that the exchange rates being given on mined coins was always 15-20% below the expected value at the time of payout. Its a hard discussion to win because everyone seems to doubt the validity and chalks up the evidence as somehow doctored or could be explained away by exchange price fluctuations. Hopefully Crackfoo comes to his senses and implements the bug fix. In fact I think people would be fine paying a 5-10% exchange fee if he were transparent about it. It costs money to run a pool and I don't think anyone expects him to do it for free. You also have to understand how pools like Zpool work and profit-switching in general. When you mine a coin that is "most profitable" in the moment, many, many rigs get pointed to it through the various profit-switching software and pools that are out there. This raises the difficulty on the coin causing it to slide down the ranks. The coins that you did mine at Zpool (or other services) then get sent to the exchange, where it may not be as profitable as it was when you first mined it. Depending on how fast the coin gets exchanged, it could be worth much less BTC. I have some Nist5 coin that I mined at Zpool that has been at the exchanges for over 2 weeks. This is why you should never set AM or any profit-switching algorithm to "current" statistics, but 24 hour averages or longer. Coins slide up and down from the top spot constantly, and you are chasing the tail of the spike if you are using current statistics. If you are in it for profit, then you are better off mining coins that average in the top 5, as you want consistent profit.
|
|
|
|
loneSilentWolf
Newbie
Offline
Activity: 21
Merit: 0
|
|
December 10, 2017, 02:49:42 AM |
|
can not start zpool and hash refiner profit switching mining. when i start the miner gets in start-stop loop 4-5 times and then just quits diagnostics gives the following output Starting Diagnostics. Awesome Miner version: 4.2.4 Starting Mining Software Setting up Miner Engine. Instance: 1 Engine Type: SgMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: Added rule for: C:\Users\Parivaar\AppData\Local\AwesomeMiner\sgminer-5.6.1-nicehash-51-windows-i386_1\sgminer.exe C:\Users\Parivaar\AppData\Local\AwesomeMiner\sgminer-5.6.1-nicehash-51-windows-i386_1\sgminer.exe --config awesome.conf --text-only --algorithm neoscrypt (WindowMode: ConsoleFormat, EngineType: SgMiner, IsProfitMiner: True) Configuration: { "pools": [ { "name": "Zpool [NeoScrypt]", "nfactor": "10", "algorithm": "neoscrypt", "url": "stratum+tcp://neoscrypt.mine.zpool.ca:4233", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Lyra2REv2]", "nfactor": "10", "algorithm": "lyra2rev2", "url": "stratum+tcp://lyra2v2.mine.zpool.ca:4533", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Decred]", "nfactor": "10", "algorithm": "decred", "url": "stratum+tcp://decred.mine.zpool.ca:5744", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [LBRY]", "nfactor": "10", "algorithm": "lbry", "url": "stratum+tcp://lbry.mine.zpool.ca:3334", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Nist5]", "nfactor": "10", "algorithm": "talkcoin-mod", "url": "stratum+tcp://nist5.mine.zpool.ca:3833", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Quark]", "nfactor": "10", "algorithm": "quarkcoin", "url": "stratum+tcp://quark.mine.zpool.ca:4033", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Qubit]", "nfactor": "10", "algorithm": "qubitcoin", "url": "stratum+tcp://qubit.mine.zpool.ca:4733", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [Scrypt]", "nfactor": "10", "algorithm": "zuikkis", "url": "stratum+tcp://scrypt.mine.zpool.ca:3433", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [SHA-3]", "nfactor": "10", "algorithm": "maxcoin", "url": "stratum+tcp://keccak.mine.zpool.ca:5133", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [X11]", "nfactor": "10", "algorithm": "darkcoin-mod", "url": "stratum+tcp://x11.mine.zpool.ca:3533", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [X11Gost]", "nfactor": "10", "algorithm": "sibcoin-mod", "url": "stratum+tcp://sib.mine.zpool.ca:5033", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [X13]", "nfactor": "10", "algorithm": "marucoin-mod", "url": "stratum+tcp://x13.mine.zpool.ca:3633", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [X14]", "nfactor": "10", "algorithm": "x14", "url": "stratum+tcp://x14.mine.zpool.ca:3933", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" }, { "name": "Zpool [X15]", "nfactor": "10", "algorithm": "bitblock", "url": "stratum+tcp://x15.mine.zpool.ca:3733", "user": "185qFNB2sAhQAwZnXZjJCr32quKEyAjdDH", "pass": "x" } ], "api-port": "4028", "intensity": "16", "worksize": "256", "shaders": "2048", "failover-only": true, "gpu-threads": "2", "api-listen": true, "api-allow": "W:127.0.0.1/32", "expiry": "120", "log": "5", "queue": "1", "scan-time": "60", "temp-hysteresis": "3" } > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 0 N-factor to 10 > [07:58:23] Setting pool 0 name to Zpool [NeoScrypt] > [07:58:23] Setting pool 0 algorithm to neoscrypt > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 1 N-factor to 10 > [07:58:23] Setting pool 1 name to Zpool [Lyra2REv2] > [07:58:23] Setting pool 1 algorithm to lyra2rev2 > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 2 N-factor to 10 > [07:58:23] Setting pool 2 name to Zpool [Decred] > [07:58:23] Setting pool 2 algorithm to decred > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 3 N-factor to 10 > [07:58:23] Setting pool 3 name to Zpool [LBRY] > [07:58:23] Setting pool 3 algorithm to lbry > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 4 N-factor to 10 > [07:58:23] Setting pool 4 name to Zpool [Nist5] > [07:58:23] Setting pool 4 algorithm to talkcoin-mod > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 5 N-factor to 10 > [07:58:23] Setting pool 5 name to Zpool [Quark] > [07:58:23] Setting pool 5 algorithm to quarkcoin > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 6 N-factor to 10 > [07:58:23] Setting pool 6 name to Zpool [Qubit] > [07:58:23] Setting pool 6 algorithm to qubitcoin > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 7 N-factor to 10 > [07:58:23] Setting pool 7 name to Zpool [Scrypt] > [07:58:23] Setting pool 7 algorithm to zuikkis > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 8 N-factor to 10 > [07:58:23] Setting pool 8 name to Zpool [SHA-3] > [07:58:23] Setting pool 8 algorithm to maxcoin > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 9 N-factor to 10 > [07:58:23] Setting pool 9 name to Zpool [X11] > [07:58:23] Setting pool 9 algorithm to darkcoin-mod > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 10 N-factor to 10 > [07:58:23] Setting pool 10 name to Zpool [X11Gost] > [07:58:23] Setting pool 10 algorithm to sibcoin-mod > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 11 N-factor to 10 > [07:58:23] Setting pool 11 name to Zpool [X13] > [07:58:23] Setting pool 11 algorithm to marucoin-mod > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 12 N-factor to 10 > [07:58:23] Setting pool 12 name to Zpool [X14] > [07:58:23] Setting pool 12 algorithm to x14 > [07:58:23] Global quota greatest common denominator set to 1 > [07:58:23] Setting pool 13 N-factor to 10 > [07:58:23] Setting pool 13 name to Zpool [X15] > [07:58:23] Setting pool 13 algorithm to bitblock > [07:58:23] Set default algorithm to neoscrypt > [07:58:23] Started sgminer 5.6.1-nicehash-51 > [07:58:23] * using Jansson 2.7 > [07:58:23] Loaded configuration file awesome.conf > [07:58:23] CL Platform vendor: Intel(R) Corporation > [07:58:23] CL Platform name: Intel(R) OpenCL > [07:58:23] CL Platform version: OpenCL 1.2 > [07:58:23] Error -1: Getting Device IDs (num) > [07:58:23] clDevicesNum returned error, no GPUs usable > [07:58:23] Default Devices = all > [07:58:23] set_devices(all) > [07:58:23] GPU 0 Worksize set to 256. > [07:58:23] Loading settings from default_profile for pool 13 > [07:58:23] Pool 13 Algorithm set to "bitblock" > [07:58:23] Pool 13 devices set to "all" > [07:58:23] Pool 13 lookup gap set to "(null)" > [07:58:23] Pool 13 Intensity set to "16" > [07:58:23] Pool 13 Thread Concurrency set to "(null)" > [07:58:23] Pool 13 GPU Clock set to "(null)" > [07:58:23] Pool 13 GPU Memory clock set to "(null)" > [07:58:23] Pool 13 GPU Threads set to "2" > [07:58:23] Pool 13 GPU Fan set to "(null)" > [07:58:23] Pool 13 GPU Powertune set to "(null)" > [07:58:23] Pool 13 GPU Vddc set to "(null)" > [07:58:23] Pool 13 Shaders set to "2048" > [07:58:23] Pool 13 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 12 > [07:58:23] Pool 12 Algorithm set to "x14" > [07:58:23] Pool 12 devices set to "all" > [07:58:23] Pool 12 lookup gap set to "(null)" > [07:58:23] Pool 12 Intensity set to "16" > [07:58:23] Pool 12 Thread Concurrency set to "(null)" > [07:58:23] Pool 12 GPU Clock set to "(null)" > [07:58:23] Pool 12 GPU Memory clock set to "(null)" > [07:58:23] Pool 12 GPU Threads set to "2" > [07:58:23] Pool 12 GPU Fan set to "(null)" > [07:58:23] Pool 12 GPU Powertune set to "(null)" > [07:58:23] Pool 12 GPU Vddc set to "(null)" > [07:58:23] Pool 12 Shaders set to "2048" > [07:58:23] Pool 12 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 11 > [07:58:23] Pool 11 Algorithm set to "marucoin-mod" > [07:58:23] Pool 11 devices set to "all" > [07:58:23] Pool 11 lookup gap set to "(null)" > [07:58:23] Pool 11 Intensity set to "16" > [07:58:23] Pool 11 Thread Concurrency set to "(null)" > [07:58:23] Pool 11 GPU Clock set to "(null)" > [07:58:23] Pool 11 GPU Memory clock set to "(null)" > [07:58:23] Pool 11 GPU Threads set to "2" > [07:58:23] Pool 11 GPU Fan set to "(null)" > [07:58:23] Pool 11 GPU Powertune set to "(null)" > [07:58:23] Pool 11 GPU Vddc set to "(null)" > [07:58:23] Pool 11 Shaders set to "2048" > [07:58:23] Pool 11 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 10 > [07:58:23] Pool 10 Algorithm set to "sibcoin-mod" > [07:58:23] Pool 10 devices set to "all" > [07:58:23] Pool 10 lookup gap set to "(null)" > [07:58:23] Pool 10 Intensity set to "16" > [07:58:23] Pool 10 Thread Concurrency set to "(null)" > [07:58:23] Pool 10 GPU Clock set to "(null)" > [07:58:23] Pool 10 GPU Memory clock set to "(null)" > [07:58:23] Pool 10 GPU Threads set to "2" > [07:58:23] Pool 10 GPU Fan set to "(null)" > [07:58:23] Pool 10 GPU Powertune set to "(null)" > [07:58:23] Pool 10 GPU Vddc set to "(null)" > [07:58:23] Pool 10 Shaders set to "2048" > [07:58:23] Pool 10 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 9 > [07:58:23] Pool 9 Algorithm set to "darkcoin-mod" > [07:58:23] Pool 9 devices set to "all" > [07:58:23] Pool 9 lookup gap set to "(null)" > [07:58:23] Pool 9 Intensity set to "16" > [07:58:23] Pool 9 Thread Concurrency set to "(null)" > [07:58:23] Pool 9 GPU Clock set to "(null)" > [07:58:23] Pool 9 GPU Memory clock set to "(null)" > [07:58:23] Pool 9 GPU Threads set to "2" > [07:58:23] Pool 9 GPU Fan set to "(null)" > [07:58:23] Pool 9 GPU Powertune set to "(null)" > [07:58:23] Pool 9 GPU Vddc set to "(null)" > [07:58:23] Pool 9 Shaders set to "2048" > [07:58:23] Pool 9 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 8 > [07:58:23] Pool 8 Algorithm set to "maxcoin" > [07:58:23] Pool 8 devices set to "all" > [07:58:23] Pool 8 lookup gap set to "(null)" > [07:58:23] Pool 8 Intensity set to "16" > [07:58:23] Pool 8 Thread Concurrency set to "(null)" > [07:58:23] Pool 8 GPU Clock set to "(null)" > [07:58:23] Pool 8 GPU Memory clock set to "(null)" > [07:58:23] Pool 8 GPU Threads set to "2" > [07:58:23] Pool 8 GPU Fan set to "(null)" > [07:58:23] Pool 8 GPU Powertune set to "(null)" > [07:58:23] Pool 8 GPU Vddc set to "(null)" > [07:58:23] Pool 8 Shaders set to "2048" > [07:58:23] Pool 8 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 7 > [07:58:23] Pool 7 Algorithm set to "zuikkis" > [07:58:23] Pool 7 devices set to "all" > [07:58:23] Pool 7 lookup gap set to "(null)" > [07:58:23] Pool 7 Intensity set to "16" > [07:58:23] Pool 7 Thread Concurrency set to "(null)" > [07:58:23] Pool 7 GPU Clock set to "(null)" > [07:58:23] Pool 7 GPU Memory clock set to "(null)" > [07:58:23] Pool 7 GPU Threads set to "2" > [07:58:23] Pool 7 GPU Fan set to "(null)" > [07:58:23] Pool 7 GPU Powertune set to "(null)" > [07:58:23] Pool 7 GPU Vddc set to "(null)" > [07:58:23] Pool 7 Shaders set to "2048" > [07:58:23] Pool 7 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 6 > [07:58:23] Pool 6 Algorithm set to "qubitcoin" > [07:58:23] Pool 6 devices set to "all" > [07:58:23] Pool 6 lookup gap set to "(null)" > [07:58:23] Pool 6 Intensity set to "16" > [07:58:23] Pool 6 Thread Concurrency set to "(null)" > [07:58:23] Pool 6 GPU Clock set to "(null)" > [07:58:23] Pool 6 GPU Memory clock set to "(null)" > [07:58:23] Pool 6 GPU Threads set to "2" > [07:58:23] Pool 6 GPU Fan set to "(null)" > [07:58:23] Pool 6 GPU Powertune set to "(null)" > [07:58:23] Pool 6 GPU Vddc set to "(null)" > [07:58:23] Pool 6 Shaders set to "2048" > [07:58:23] Pool 6 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 5 > [07:58:23] Pool 5 Algorithm set to "quarkcoin" > [07:58:23] Pool 5 devices set to "all" > [07:58:23] Pool 5 lookup gap set to "(null)" > [07:58:23] Pool 5 Intensity set to "16" > [07:58:23] Pool 5 Thread Concurrency set to "(null)" > [07:58:23] Pool 5 GPU Clock set to "(null)" > [07:58:23] Pool 5 GPU Memory clock set to "(null)" > [07:58:23] Pool 5 GPU Threads set to "2" > [07:58:23] Pool 5 GPU Fan set to "(null)" > [07:58:23] Pool 5 GPU Powertune set to "(null)" > [07:58:23] Pool 5 GPU Vddc set to "(null)" > [07:58:23] Pool 5 Shaders set to "2048" > [07:58:23] Pool 5 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 4 > [07:58:23] Pool 4 Algorithm set to "talkcoin-mod" > [07:58:23] Pool 4 devices set to "all" > [07:58:23] Pool 4 lookup gap set to "(null)" > [07:58:23] Pool 4 Intensity set to "16" > [07:58:23] Pool 4 Thread Concurrency set to "(null)" > [07:58:23] Pool 4 GPU Clock set to "(null)" > [07:58:23] Pool 4 GPU Memory clock set to "(null)" > [07:58:23] Pool 4 GPU Threads set to "2" > [07:58:23] Pool 4 GPU Fan set to "(null)" > [07:58:23] Pool 4 GPU Powertune set to "(null)" > [07:58:23] Pool 4 GPU Vddc set to "(null)" > [07:58:23] Pool 4 Shaders set to "2048" > [07:58:23] Pool 4 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 3 > [07:58:23] Pool 3 Algorithm set to "lbry" > [07:58:23] Pool 3 devices set to "all" > [07:58:23] Pool 3 lookup gap set to "(null)" > [07:58:23] Pool 3 Intensity set to "16" > [07:58:23] Pool 3 Thread Concurrency set to "(null)" > [07:58:23] Pool 3 GPU Clock set to "(null)" > [07:58:23] Pool 3 GPU Memory clock set to "(null)" > [07:58:23] Pool 3 GPU Threads set to "2" > [07:58:23] Pool 3 GPU Fan set to "(null)" > [07:58:23] Pool 3 GPU Powertune set to "(null)" > [07:58:23] Pool 3 GPU Vddc set to "(null)" > [07:58:23] Pool 3 Shaders set to "2048" > [07:58:23] Pool 3 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 2 > [07:58:23] Pool 2 Algorithm set to "decred" > [07:58:23] Pool 2 devices set to "all" > [07:58:23] Pool 2 lookup gap set to "(null)" > [07:58:23] Pool 2 Intensity set to "16" > [07:58:23] Pool 2 Thread Concurrency set to "(null)" > [07:58:23] Pool 2 GPU Clock set to "(null)" > [07:58:23] Pool 2 GPU Memory clock set to "(null)" > [07:58:23] Pool 2 GPU Threads set to "2" > [07:58:23] Pool 2 GPU Fan set to "(null)" > [07:58:23] Pool 2 GPU Powertune set to "(null)" > [07:58:23] Pool 2 GPU Vddc set to "(null)" > [07:58:23] Pool 2 Shaders set to "2048" > [07:58:23] Pool 2 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 1 > [07:58:23] Pool 1 Algorithm set to "lyra2rev2" > [07:58:23] Pool 1 devices set to "all" > [07:58:23] Pool 1 lookup gap set to "(null)" > [07:58:23] Pool 1 Intensity set to "16" > [07:58:23] Pool 1 Thread Concurrency set to "(null)" > [07:58:23] Pool 1 GPU Clock set to "(null)" > [07:58:23] Pool 1 GPU Memory clock set to "(null)" > [07:58:23] Pool 1 GPU Threads set to "2" > [07:58:23] Pool 1 GPU Fan set to "(null)" > [07:58:23] Pool 1 GPU Powertune set to "(null)" > [07:58:23] Pool 1 GPU Vddc set to "(null)" > [07:58:23] Pool 1 Shaders set to "2048" > [07:58:23] Pool 1 Worksize set to "256" > [07:58:23] Loading settings from default_profile for pool 0 > [07:58:23] Pool 0 Algorithm set to "neoscrypt" > [07:58:23] Pool 0 devices set to "all" > [07:58:23] Pool 0 lookup gap set to "(null)" > [07:58:23] Pool 0 Intensity set to "16" > [07:58:23] Pool 0 Thread Concurrency set to "(null)" > [07:58:23] Pool 0 GPU Clock set to "(null)" > [07:58:23] Pool 0 GPU Memory clock set to "(null)" > [07:58:23] Pool 0 GPU Threads set to "2" > [07:58:23] Pool 0 GPU Fan set to "(null)" > [07:58:23] Pool 0 GPU Powertune set to "(null)" > [07:58:23] Pool 0 GPU Vddc set to "(null)" > [07:58:23] Pool 0 Shaders set to "2048" > [07:58:23] Pool 0 Worksize set to "256" > [07:58:23] All devices disabled, cannot mine! > [07:58:23] Started sgminer 5.6.1-nicehash-51 > [07:58:23] * using Jansson 2.7 > [07:58:23] Loaded configuration file awesome.conf > [07:58:23] clDevicesNum returned error, no GPUs usable > [07:58:23] All devices disabled, cannot mine! Failed to start miner process: Process has exited, so the requested information is not available. Failed to start miner in Diagnostics mode Diagnostics completed any solution?
|
|
|
|
|
razorseal
Newbie
Offline
Activity: 60
Merit: 0
|
|
December 10, 2017, 03:33:21 AM Last edit: December 10, 2017, 04:00:31 AM by razorseal |
|
Guys, is there any guide to help me setup AM for miningpoolhub? I tried to look around and cant find anything... I did what I think I got right, and I have no idea what it's doing lol. I added a managed profit miner and then added a 'new pool'... I put the address of the BTG pool address in the URL and then worker name (username.worker) and pass x.... picked the type of coin... I then clicked start and now it's mining "unknown neoscript" which I believe is feathercoin I'm so confused. I really want to get this thing running. I primarily want to run equihash, lyra2rev2 and cryptonight for CPU. that's it... I should be alternating between vertcoin, bitcoin gold, monacoin and monero for CPU... Help me out please! Here is a screenshot. I have no idea where that portnumber came from... It's the one for monacoin alright... I don't see it on the dashboard that I'm making anything though? https://s17.postimg.org/50gyy5yyn/AM_ss.pngalso, is there a way to make my CPU work on monero for MPH as a 2nd worker? edit - it decided to mine groestlcoin which I have no interest in, not to mention, I was just mining monacoin at 80 dollars a day, and now it's doing groestlcoin at 35 dollars a way
|
|
|
|
taserz
Sr. Member
Offline
Activity: 808
Merit: 294
Created AutoTune to saved the planet! ~USA
|
|
December 10, 2017, 04:38:07 AM |
|
With Awesome Miner C# Script API how can I call on the miner to get it's local ip address or remote host. I am trying to build something so I can use a pre built in trigger and the action requires me to know the ip of the miner on my local network.
This will be a script everyone is going to want so I will post it here once it is done. More so the guys with lots of miners.
|
|
|
|
Jaerin
|
|
December 10, 2017, 05:58:03 AM |
|
You were correct STSMiner.... After changing the switching interval and the profit switching threshold, I am now seeing what I consider normal functionality. _________ New Question: Are any you using zpool and noticing you are not getting paid anywhere close to what Awesome Miner is saying you are earning? I mined all day and night with my test rig, and Awesome Miner was reporting a profit from $6/day to $18/day.... But on the zpool wallet page, it shows I have earned $3 in bitcoin. There has been a long time speculation that there is something causing 20% loss of earnings in the exchange process. I discovered that the AverageIncrement function used to create a rolling average of the prices on the exchanges could return 80% of the input values if either of the inputs were 0. I've submitted a bug fix to the Yiimp git, but it has not been accepted yet. Ahashpool.com has implemented the bug fix long ago and I have found that it pays out much better than Zpool. The one drawback is that it does not have near the same number of algorithms and coins available. Specifically the Equihash implementation in Yiimp is private and not shared publicly. Zpool does still pay out better than what Nicehash used too, but there is an obvious bug that continues to go unfixed. There is a thread where evidence was presented that clearly showed that the exchange rates being given on mined coins was always 15-20% below the expected value at the time of payout. Its a hard discussion to win because everyone seems to doubt the validity and chalks up the evidence as somehow doctored or could be explained away by exchange price fluctuations. Hopefully Crackfoo comes to his senses and implements the bug fix. In fact I think people would be fine paying a 5-10% exchange fee if he were transparent about it. It costs money to run a pool and I don't think anyone expects him to do it for free. You also have to understand how pools like Zpool work and profit-switching in general. When you mine a coin that is "most profitable" in the moment, many, many rigs get pointed to it through the various profit-switching software and pools that are out there. This raises the difficulty on the coin causing it to slide down the ranks. The coins that you did mine at Zpool (or other services) then get sent to the exchange, where it may not be as profitable as it was when you first mined it. Depending on how fast the coin gets exchanged, it could be worth much less BTC. I have some Nist5 coin that I mined at Zpool that has been at the exchanges for over 2 weeks. This is why you should never set AM or any profit-switching algorithm to "current" statistics, but 24 hour averages or longer. Coins slide up and down from the top spot constantly, and you are chasing the tail of the spike if you are using current statistics. If you are in it for profit, then you are better off mining coins that average in the top 5, as you want consistent profit. I know perfectly well how the pool works. And you're right that you are chasing the potential quick profits, but what you also have to realize is when those coins "spike" in profits could be because there is a short term drop in difficult of the coin and therefore your hashing power for that period actually will generate you more of those coins of that type then it normally would. When the difficulty spikes back up to move onto a different more profitable coin. There is usually 2-3 algorithms that it will end up cycling throughout the day. The price fluctuations on the exchanges may also be the reason one coin becomes more profitable over another. It all depends on how things play out. In general though I can say that my hashing power using a program like Awesome Miner or Multipoolminer on a pool like Ahashpool.com far outperforms sticking to a single coin. As an example I look at whattomine.com and it says for my 7 - 1080's and 1 - 1080Ti based on 7 day difficulty and profitability I should be mining Monacoin and expecting .00253BTC a day. On ahashpool.com in that last 24h I've made closer to .004 My ahashpool wallet: https://www.ahashpool.com/wallet.php?wallet=1Q3HQdXLuiTpmgZo9Mt24Bomee8HyiWRsvwhattomine.com for the same: https://tinyurl.com/ycggbgr5And actually that isn't a full time with my 1080Ti because I play game with it and don't usually mine with it 24/7.
|
|
|
|
mohicans
Newbie
Offline
Activity: 21
Merit: 0
|
|
December 10, 2017, 08:43:38 AM |
|
Hi guys, I'm getting this issue as well, Cast XMR is listed on the Managed Software section but not selectable within the Profit Profiles Thanks Awesome Miner version 4.2.4
- Cast XMR miner supported as Managed Miner - New settings for wait time before terminating mining software and delay for auto starting miners on bootup - Command line and custom exe-file configurable per Managed Profit Miner - "Remove miner" added to context menu in miner list - South African Rand added as display currency - E-mail configuration includes a button for sending a test message - Disabled Blake2b (sia) on Ccminer - Correction to Wallet balance list - Correction to benchmarking
I love you patrike thanks so much for this update I just have one question, I see cast-xmr in "managed miners" but I can't select it in my profit profiles, how do I make my miners use it for cryptonight? Cast XMR was introduced as a Managed Miner, but not yet listed as an option for Profit switching. I was hoping to get some feedback on the Cast XMR implementation made so far before I make it available for profit switching as well - because then much more people will start using it. I guess we'll have to wait awhile till it is implemented on profit miner
|
|
|
|
bullxrider
Newbie
Offline
Activity: 3
Merit: 0
|
|
December 10, 2017, 11:38:46 AM |
|
Hey guys loving the software and got 2 rigs running perfectly, but my third AMD rig seems to stop between a few hours. I'm not sure why and how would I go about fixing it? Thanks for any help
Not working as in it stops mining and have to restart it with start.
|
|
|
|
|