 Show Posts
|
|
Pages: [1] 2 3 »
|
Our company just brought in a huge haul of brand new parts from a miner that never got around to building. Everything is brand new and sealed in retail boxes. It’s like Newegg for miners over here right now. We will make very favorable deals for bulk purchases, but single unit prices: 580 8G - Sapphire Nitro +, MSI Gaming X - $175 Celeron G3930 - $50 MSI Z270-A Pro - $50 Ballistix 4GB DDR4 2666 - $25 ADATA 128GB NVME SSD - $25 Corsair HX1200 - $120 Corsair HX1000 - $100 We are a legit business located in NY that specializes in building mining farms and liquidating/reselling parts: http://www.bitprocrypto.comBTC, Local cash accepted |
|
|
|
lots of "share rejected due to low difficulty"
11 accepted 24 rejected
testing grin on win7 12.1.0
if it is happen when you test on grinmint pool, this problem should have been fixed in Bminer 12.2.0, please try and let me know if it works. https://bminer.me/releases/it works on grinmint, 130 accepted - 8 rejected How do you format the -uri with the email address? |
|
|
|
|
Zergpool has apparently risen from the dead. It would be great if you could re-enable native support for it, it has by far the best selection of coins to mine.
|
|
|
|
I've been having a very frustrating problem the last couple of weeks - every few hours a miner randomly "fails to start", and then I get the modal dialog asking me to run diagnostics. Every single time I run diagnostics absolutely nothing is wrong. So one by one my miners are stopping, and I have to check every few hours, clear 5-10 of these dialogs, start the miners back up, and they work every single time. So there has to be some bug in AM causing this, because there's certainly not a problem with the miners or the rigs if the miner starts right up every time.
Nope, that's definitely not it. Something must have changed in awesome miner, because this only started happening recently.
If you get the dialog that the miner failed to start, it's because the mining software has crashed a number of times over the last few minutes. After a number of attempts of restarting it, Awesome Miner will give up and show this error. You can configure Awesome Miner to continue trying to restart the crashed mining software via the Options dialog, Mining Settings section, where you can set the restart attempts to 99. As the number of attempts are based on the last few minutes, a value of 99 will basically make Awesome Miner trying to restart the mining every time it's crashes and never give up. There are no recent changes in Awesome Miner to this behavior. There can be instances where mining software crashes a number of times for a while, but when starting it with the exact same settings a little later, it will no longer crash. Temperature is a common cause why the problem resolves itself, but I suppose there can be many other reasons why mining software don't give consistent behaviors with the crashes. For the crashes you may have to do general troubleshooting to find out if it's a specific algorithm or mining software or mining rig or clocking settings that causes the problem. I've set it to restart as many as 10 times, and while I'm using the program if the dialog pops up, I can click it *immediately* and it always still works. Furthermore, I tried to set a rule where it would wait 10 seconds before starting the miner again, but the modal dialogs seem to block that rule from executing (and who knows what else). For instance this morning I had 3 of those dialogs on top of each other, I clicked no to all of them, and then a few seconds later, the rule triggered and all three started up just fine. There at least has to be some way to turn this blocking dialog off if it's going to prevent me from setting rules to correct this inexplicable behavior. Thanks for the update, I understand your point. Do you get any entry on the Notifications tab about this issue? Could you please send me the log file for this Remote Agent and also for the Awesome Miner main application - and let me know the time and the name of the miner? I will investigate to find out what the scenario looks like. Thanks! 12/22/2018 6:16:22 PM.152 [009] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Starting...
12/22/2018 6:16:23 PM.167 [009] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Starting Mining Software
12/22/2018 6:16:23 PM.167 [009] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Setting up Miner Engine. Instance: 1
12/22/2018 6:16:23 PM.167 [009] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
12/22/2018 6:16:23 PM.167 [009] EngineSetup: CcCryptoDredgeEngine
12/22/2018 6:16:23 PM.167 [009] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Set clocking start profile: 59, 60%/+100/0/Auto (when stopping, the following will be used: -1, type: Single, Use: False)
12/22/2018 6:16:23 PM.167 [022] ApplySingleProfile Begin
12/22/2018 6:16:23 PM.167 [022] Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
12/22/2018 6:16:23 PM.199 [022] Number of GPU commands: 20
12/22/2018 6:16:23 PM.199 [022] Executing GPU clocking command: /setmacm, powerLimit0=60&coreClockBoost0=100000&memoryClockBoost0=0&fanSpeed0=auto&powerLimit1=60&coreClockBoost1=100000&memoryClockBoost1=0&fanSpeed1=auto&powerLimit2=60&coreClockBoost2=100000&memoryClockBoost2=0&fanSpeed2=auto&powerLimit3=60&coreClockBoost3=100000&memoryClockBoost3=0&fanSpeed3=auto&powerLimit4=60&coreClockBoost4=100000&memoryClockBoost4=0&fanSpeed4=auto
12/22/2018 6:16:23 PM.199 [022] Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
12/22/2018 6:16:24 PM.183 [020] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:24 PM.183 [009] [E]System.NullReferenceException: Object reference not set to an instance of an object.
12/22/2018 6:16:24 PM.183 [009] [E] at AwesomeMiner.Service.Core.Engines.EnginePrepareBase.GetStaticSortedPools()
at AwesomeMiner.Service.Core.Engines.EnginePrepareBase.ProcessVirtualEffectivePool List()
at AwesomeMiner.Service.Core.Engines.CcMiner.CcEnginePrepare.BuildArguments()
at AwesomeMiner.Service.Core.Engines.MinerEngine.Start(Int32 #=znFEPBq4WhQQq, Boolean #=zm8OVyhw=, Boolean #=z3_DDggA=, BenchmarkCommand #=zG2LTkxarwMBnUeaT5w==)
12/22/2018 6:16:24 PM.183 [009] [E][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Failed to start miner process: Object reference not set to an instance of an object.
12/22/2018 6:16:24 PM.183 [009] [E][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X]Failed to start miner
12/22/2018 6:16:25 PM.199 [020] [ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:27 PM.027 [022] ApplySingleProfile End
12/22/2018 6:16:29 PM.246 [038] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:30 PM.262 [038] [ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:34 PM.325 [020] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:35 PM.341 [020] [ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:39 PM.388 [022] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:40 PM.404 [016] [ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:44 PM.435 [007] [ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:45 PM.451 [038] [ManagedMiner#531 - CPU-J7] : ProcessMiner |
|
|
|
I've been having a very frustrating problem the last couple of weeks - every few hours a miner randomly "fails to start", and then I get the modal dialog asking me to run diagnostics. Every single time I run diagnostics absolutely nothing is wrong. So one by one my miners are stopping, and I have to check every few hours, clear 5-10 of these dialogs, start the miners back up, and they work every single time. So there has to be some bug in AM causing this, because there's certainly not a problem with the miners or the rigs if the miner starts right up every time.
Nope, that's definitely not it. Something must have changed in awesome miner, because this only started happening recently.
If you get the dialog that the miner failed to start, it's because the mining software has crashed a number of times over the last few minutes. After a number of attempts of restarting it, Awesome Miner will give up and show this error. You can configure Awesome Miner to continue trying to restart the crashed mining software via the Options dialog, Mining Settings section, where you can set the restart attempts to 99. As the number of attempts are based on the last few minutes, a value of 99 will basically make Awesome Miner trying to restart the mining every time it's crashes and never give up. There are no recent changes in Awesome Miner to this behavior. There can be instances where mining software crashes a number of times for a while, but when starting it with the exact same settings a little later, it will no longer crash. Temperature is a common cause why the problem resolves itself, but I suppose there can be many other reasons why mining software don't give consistent behaviors with the crashes. For the crashes you may have to do general troubleshooting to find out if it's a specific algorithm or mining software or mining rig or clocking settings that causes the problem. I've set it to restart as many as 10 times, and while I'm using the program if the dialog pops up, I can click it *immediately* and it always still works. Furthermore, I tried to set a rule where it would wait 10 seconds before starting the miner again, but the modal dialogs seem to block that rule from executing (and who knows what else). For instance this morning I had 3 of those dialogs on top of each other, I clicked no to all of them, and then a few seconds later, the rule triggered and all three started up just fine. There at least has to be some way to turn this blocking dialog off if it's going to prevent me from setting rules to correct this inexplicable behavior. |
|
|
|
|
Nope, that's definitely not it. Something must have changed in awesome miner, because this only started happening recently.
|
|
|
|
|
I've been having a very frustrating problem the last couple of weeks - every few hours a miner randomly "fails to start", and then I get the modal dialog asking me to run diagnostics. Every single time I run diagnostics absolutely nothing is wrong. So one by one my miners are stopping, and I have to check every few hours, clear 5-10 of these dialogs, start the miners back up, and they work every single time. So there has to be some bug in AM causing this, because there's certainly not a problem with the miners or the rigs if the miner starts right up every time.
|
|
|
|
Looking at the block explorer https://explorer.ritocoin.org/richlistthe owner of minermore pool owns like 80% of the coins. Pool owners and devs working together to scam people. Beware people beware. Minermore has a username system where people don't need a wallet to start mining, so the coins have to go somewhere controlled by minermore. |
|
|
|
|
Any possibility of adding Current Rev/Profit to the graph on the dashboard, or at least to the history collection? The hashrates arent helpful when you have multiple different models hashing at vastly different scales, and it's not really the #1 thing that matters anyway.
|
|
|
|
Awesome Miner version 5.4.5 (Development preview of 5.5) is now available. It's a smaller update to the previous development version that address issues related to:
- Configuration not received correctly for Remote Agent on Linux
- Execution of rules based on failed process trigger corrected, to prevent blocking user interface updates
- T-Rex miner launched again (a second instance) after restarting Remote Agent
When I try to upgrade the linux remote agent, it fails: Sep 04 18:30:50 worker systemd[1]: awesome.service: Service hold-off time over, scheduling restart. Sep 04 18:30:50 worker systemd[1]: Stopped Awesome Miner Remote Agent. Sep 04 18:30:50 worker systemd[1]: Started Awesome Miner Remote Agent. Sep 04 18:30:50 worker systemd[1]: awesome.service: Main process exited, code=exited, status=203/EXEC Sep 04 18:30:50 worker systemd[1]: awesome.service: Unit entered failed state. Sep 04 18:30:50 worker systemd[1]: awesome.service: Failed with result 'exit-code'. Sep 04 18:30:50 worker systemd[1]: awesome.service: Service hold-off time over, scheduling restart. Sep 04 18:30:50 worker systemd[1]: Stopped Awesome Miner Remote Agent. Sep 04 18:30:50 worker systemd[1]: awesome.service: Start request repeated too quickly. Sep 04 18:30:50 worker systemd[1]: Failed to start Awesome Miner Remote Agent. |
|
|
|
|
So my initial test with the linux agent was a semi-fail. I got AM to recognize the agent, but it refuses to mine.
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.077 [001] Starting service
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003] Updating settings
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003] [W]Warning - Settings is null
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003] Current list of Active Miners:
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.089 [003] Saving configuration to: /root/.config/AwesomeMinerSe rvice/ServiceData.xml.tmp
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.099 [003] --> /root/.config/AwesomeMinerService/ServiceData.xml
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.105 [003] Starting Service Manager...
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.112 [003] IntelliServer::Start - Will listen on Port: 9630
Sep 04 01:53:41 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:41 AM.110 [008] Running Discovery Thread
Sep 04 01:55:45 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:45 AM.912 [016] Setting callback channel
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.304 [016] Command request: Start
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.305 [016] [E]Miner not found: 284
|
|
|
|
|
I'm really eager to test out the linux remote agent. I'd like to use as stripped down a distro as possible, basically just the bare minimum needed to mine in linux via command line, preferably off of a USB stick.
Can anyone recommend a pre-packaged distro with the bare minimum required for mining, specifically the drivers? Or a up to date guide that outlines the bare minimum steps to making ubuntu server mining ready?
Also, are there any limitations to the current linux agent aside from the mining software that can be automatically downloaded? Can we still upload custom software? What if any methods are available to control GPU clocks?
|
|
|
|
|
Also, with so many usable miners with a lot of overlap on algos now (t-rex, z-enemy, cryptodredge), I would really like it if there was a way to view the mining software currently being used in a column on the compact view.
|
|
|
|
Just wanted to let you know that I've isolated the UI freezing problem to a scenario where I have a remote client that I am connecting to via port forwarding, and their internet connectivity is spotty. I imagine the freeze is happening when the thread is hanging because it is expecting a timely response from the remote client and not getting it. Is there a setting already in place to deal with such a scenario?
Thanks for the update on this. I will try to reproduce the scenario. I would actually recommend you to check the setting for the connection timeout. Although it might sound attractive to increase the timeout to wait longer, in this case I think we should try to make it fail faster with a short timeout instead. Can you make sure that the setting "Increase connection timeout for Remote Agent" is unchecked, which is actually the default value? It is unchecked, and its still pretty bad. When Awesome Miner is in this state where it's running slow, can you please create a process dump file and send me by mail (the file will be large). Use Windows Task Manager, Details tab, right click on AwesomeMiner and select "Create dump file". With the information in this file, I will be able to see the current Awesome Miner process state and hopefully be able to identify why it's running slow. Thanks! One quick question - are you using the automatic console screen update on the Console tab (bottom of the screen in Awesome Miner), Settings -> Auto Refresh? If that's the case, please try to set it to Disabled. Yes, Ill do this soon. The freezing state seems to come and go, but I definitely still experience it with auto refresh disabled. Ive also tried disabling system monitoring, logging, all my rules, just about everything. I've added many more GB of memory as well - the only thing I'm sure of is that it's actually the UI thread of AM freezing, because if I click a little too much while the mouse cursor is a blue circle, the entire UI greys out and it asks me if I want to wait for AM to start responding again. |
|
|
|
Just wanted to let you know that I've isolated the UI freezing problem to a scenario where I have a remote client that I am connecting to via port forwarding, and their internet connectivity is spotty. I imagine the freeze is happening when the thread is hanging because it is expecting a timely response from the remote client and not getting it. Is there a setting already in place to deal with such a scenario?
Thanks for the update on this. I will try to reproduce the scenario. I would actually recommend you to check the setting for the connection timeout. Although it might sound attractive to increase the timeout to wait longer, in this case I think we should try to make it fail faster with a short timeout instead. Can you make sure that the setting "Increase connection timeout for Remote Agent" is unchecked, which is actually the default value? It is unchecked, and its still pretty bad. |
|
|
|
|
Just wanted to let you know that I've isolated the UI freezing problem to a scenario where I have a remote client that I am connecting to via port forwarding, and their internet connectivity is spotty. I imagine the freeze is happening when the thread is hanging because it is expecting a timely response from the remote client and not getting it. Is there a setting already in place to deal with such a scenario?
|
|
|
|
I'm still getting massive delays in the UI. I noticed that it's fine for the first minute or two after I open the program, and then gets progressively worse, usually to the point where i need to force terminate AM and start from scratch. There's definitely something weird going on, Ive tried performance mode, Ive tried turning off my rules, beyond that I'm not sure what can be causing these UI freezes.
Please get back to me with the log file and configuration file and I will investigate this in more detail. Thanks! I sent you the log file a while ago, nothing in my configuration has changed since then. |
|
|
|
|
I'm still getting massive delays in the UI. I noticed that it's fine for the first minute or two after I open the program, and then gets progressively worse, usually to the point where i need to force terminate AM and start from scratch. There's definitely something weird going on, Ive tried performance mode, Ive tried turning off my rules, beyond that I'm not sure what can be causing these UI freezes.
|
|
|
|
|
I'd like to put in another request for customizable columns in the main view. There's so much more information I'd like to see at a glance.
For example, I've been having a weird problem where specific mining software seems to disable itself and go back to ccminer, which is much less efficient than z-enemy, t-rex or cryptodredge. But I only notice this when I see that its not hashing as fast as it should, and then I click it and see the problem.
I'd prefer it if at least every single data entry under the summary could be displayed as a column, and let each user decide what information is most relevant to them. Some might want to see hosts or whatever.
Personally I'd like to see software, windows uptime and current GPU clocking profile. That way I can see at a glance if anything is not where I want to be in terms of software or stability.
|
|
|
|
|
Do you have any plans to support the upcoming SQRL miner and/or acorns?
Even without acorn support at first, simply supporting SQRL miner because it has the ethlargement pill built in will be a major boost in ease of use. I have had so much trouble dealing with getting the pill launched and exited properly upon profit switching, all too often I'll RDP into a rig thats mining X16 and find the pill still launched even though I have multiple kill commands programmed. I just want to be done with this dependency already, and given that theyre supposedly going to pass along the benefits to GDDR5 cards with SQRL miner, its going to be the best ETH miner by a longshot, so the sooner you can support it, the better.
As far as the acorns go, I'm sure that will add a fair bit of complexity to support thoroughly, but at least from the outset it shouldnt be too difficult to just stand out of its way and let the SQRL miner handle that end.
|
|
|
|
|
