|
That does seem like a problem. Considering I have a 4 day holiday coming up I may give it a go at breaking out an enable/disable option for each exchange..
|
|
|
|
Damn so much for a stable BTC. We went right up against that downtrend and dumped hard. I know many think charts/TA is voodoo but we're still right on track..  |
|
|
|
Exactly my point - having to deploy a new version of the mining software every 10 day basis would be a NIGHTMARE.
What? It takes me a few minutes with AwesomeMiner and even less now that Linux is supported.. deploying a new miner would take as little as 60 seconds for 100 rigs. |
|
|
|
So ZCash might be going ProgPow? That's amazing news! |
|
|
|
Z9 mini is fairly quiet - and will probably become a space heater in about a year.
L3+ are like that. Good heaters. The L3 I hosted for a friend was stupid loud.. |
|
|
|
This is pretty incredible. You can buy an L3+ right now for about the same price of a space heater. That says a lot.
Is there a way I can downclock some of the newer ASIC's and just run them as space heaters? If I can get them quiet enough.. makes sense to do. |
|
|
|
With November here temps are starting to drop... now is when my little heat machines doubly pay for themselves  Haven mining still seems to be best amazingly, not sure how that works with CNv8 making monero diff drop.. a little worrying tbh. |
|
|
|
|
Very glad to see that from Zcash. That's a well thought out and eloquent statement. Really hope more coins keep going this way.
|
|
|
|
I would do that, but I'm with smOS...
Not a very good time for AMD rigs over smOS right now...
I mean I tried to edit the config.txt on Xmr-Stak with higher intensity with no luck.. I think that is the issue with my low hashrate compared with claymore-xmr hashrate.
SMOS sucks. Take control of the OS and install the AwesomeMiner Linux client and start mining that way. I've converted all of my SMOS installs into 100% AwesomeMiner controlled/managed now. All you have to do is rename the bash scripts in /root/start.sh and /root/xminer.sh to stop it from ever messing with your stuff. |
|
|
|
So did SQRL completely fail or what?
No 1) paid most or all refunds ask for 2) some fpga's have been shipped 3) acorns and acorn nest should ship before fri 2nd But all in all still somewhat of a mess. Bringing a new product to market like this is exceptionally difficult, so I'm not really surprised. |
|
|
|
|
So did SQRL completely fail or what?
|
|
|
|
I think 5.7.2 broke the ability to communicate to the Linux client. wget http://www.awesomeminer.com/download/setup/awesomeminer-remoteagent.tar.xz
tar xvJf awesomeminer-remoteagent.tar.xz
cd awesomeminer-remoteagent
./AwesomeMiner.RemoteAgent.Linux
10/18/18 6:02:49 PM.717 [001] [S]Loading configuration from: /root/.config/AwesomeMinerService/ServiceData.xml
10/18/18 6:02:50 PM.033 [001] [S]Configuration file created: 10/18/18 3:59:33 PM
10/18/18 6:02:50 PM.049 [001] [S]Starting Awesome Miner Service 5.7.2
10/18/18 6:02:50 PM.049 [001] [S]Branding: False,
10/18/18 6:02:50 PM.049 [001] [S]MSI-Installer filename: AwesomeMinerRemoteService.msi
10/18/18 6:02:50 PM.051 [001] [S]Loading service config from: /root/awesomeminer-remoteagent
Initialize log: /root/.local/share/AwesomeMinerService/AwesomeMinerService.log
10/18/18 6:02:50 PM.070 [001] [S]Log Initiated
10/18/18 6:02:50 PM.072 [001] [S]Process: 6077, Computer name: simpleminer, 64-bit OS: True, OS version: Unix 4.11.0.1, Is Admin: False
10/18/18 6:02:50 PM.072 [001] [S]Service Port: 9630
10/18/18 6:02:50 PM.104 [001] [S]Starting service
10/18/18 6:02:50 PM.113 [003] [S]Data Path: /root/.config/AwesomeMinerService
10/18/18 6:02:50 PM.113 [003] [S]Log Path: /root/.local/share/AwesomeMinerService
10/18/18 6:02:50 PM.124 [003] [S]Updating settings
10/18/18 6:02:50 PM.124 [003] [W]Warning - Settings is null
10/18/18 6:02:50 PM.125 [003] [S]Current list of Active Miners:
10/18/18 6:02:50 PM.126 [003] [S]Saving configuration to: /root/.config/AwesomeMinerService/ServiceData.xml.tmp
10/18/18 6:02:50 PM.142 [003] [S]--> /root/.config/AwesomeMinerService/ServiceData.xml
10/18/18 6:02:50 PM.145 [003] [S]Starting Service Manager...
10/18/18 6:02:50 PM.156 [003] [S]IntelliServer::Start - Will listen on Port: 9630
10/18/18 6:02:50 PM.180 [003] [E]ChannelHandler::ReadAsync - Channel: 1 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:50 PM.192 [003] [S]Setting callback channel
10/18/18 6:02:51 PM.664 [011] [E]ChannelHandler::ReadAsync - Channel: 2 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:51 PM.665 [011] [S]Setting callback channel
10/18/18 6:02:51 PM.667 [011] [E]ChannelHandler::ReadAsync - Channel: 3 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:51 PM.667 [011] [S]Setting callback channel
10/18/18 6:02:53 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 5 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:53 PM.658 [011] [S]Setting callback channel
10/18/18 6:02:53 PM.669 [011] [E]ChannelHandler::ReadAsync - Channel: 6 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:53 PM.669 [011] [S]Setting callback channel
10/18/18 6:02:55 PM.655 [011] [E]ChannelHandler::ReadAsync - Channel: 7 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:55 PM.655 [011] [S]Setting callback channel
10/18/18 6:02:55 PM.661 [011] [E]ChannelHandler::ReadAsync - Channel: 8 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:55 PM.663 [011] [S]Setting callback channel
10/18/18 6:02:57 PM.656 [011] [E]ChannelHandler::ReadAsync - Channel: 9 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:57 PM.656 [011] [S]Setting callback channel
10/18/18 6:02:57 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 10 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:57 PM.658 [011] [S]Setting callback channel
10/18/18 6:02:59 PM.655 [011] [E]ChannelHandler::ReadAsync - Channel: 11 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:59 PM.655 [011] [S]Setting callback channel
10/18/18 6:02:59 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 12 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:59 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:01 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 13 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:01 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:01 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 14 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:01 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:03 PM.657 [011] [E]ChannelHandler::ReadAsync - Channel: 15 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:03 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:03 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 16 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:03 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:05 PM.656 [011] [E]ChannelHandler::ReadAsync - Channel: 17 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:05 PM.656 [011] [S]Setting callback channel
10/18/18 6:03:05 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 18 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:05 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:07 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 19 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:07 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:07 PM.663 [011] [E]ChannelHandler::ReadAsync - Channel: 20 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:07 PM.663 [011] [S]Setting callback channel
^C10/18/18 6:03:08 PM.283 [013] [S]Cancel key pressed
10/18/18 6:03:08 PM.283 [013] [S]ServiceContext.Shutdown
10/18/18 6:03:08 PM.284 [013] [S]Stopping service...
10/18/18 6:03:08 PM.285 [013] [S]Stopping client connections...
10/18/18 6:03:08 PM.293 [013] [S]Closing log
I'm not able to reproduce this - but let's investigate. The error "IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length" indicates a communication error and will typically happen if you connect a Managed Host (Options dialog, Managed Hosts) to Remote Agent on Linux, without checking the "Linux" box on the host. Right now the communication protocol is different if you connect Awesome Miner to a Remote Agent on Linux compared to Windows. Please also verify that you don't have any other host configured to connect to this Remote Agent on Linux. And that would be it. Added to many miners to quickly. I swear I'm not normally this dumb. |
|
|
|
I think 5.7.2 broke the ability to communicate to the Linux client. wget http://www.awesomeminer.com/download/setup/awesomeminer-remoteagent.tar.xz
tar xvJf awesomeminer-remoteagent.tar.xz
cd awesomeminer-remoteagent
./AwesomeMiner.RemoteAgent.Linux
10/18/18 6:02:49 PM.717 [001] [S]Loading configuration from: /root/.config/AwesomeMinerService/ServiceData.xml
10/18/18 6:02:50 PM.033 [001] [S]Configuration file created: 10/18/18 3:59:33 PM
10/18/18 6:02:50 PM.049 [001] [S]Starting Awesome Miner Service 5.7.2
10/18/18 6:02:50 PM.049 [001] [S]Branding: False,
10/18/18 6:02:50 PM.049 [001] [S]MSI-Installer filename: AwesomeMinerRemoteService.msi
10/18/18 6:02:50 PM.051 [001] [S]Loading service config from: /root/awesomeminer-remoteagent
Initialize log: /root/.local/share/AwesomeMinerService/AwesomeMinerService.log
10/18/18 6:02:50 PM.070 [001] [S]Log Initiated
10/18/18 6:02:50 PM.072 [001] [S]Process: 6077, Computer name: simpleminer, 64-bit OS: True, OS version: Unix 4.11.0.1, Is Admin: False
10/18/18 6:02:50 PM.072 [001] [S]Service Port: 9630
10/18/18 6:02:50 PM.104 [001] [S]Starting service
10/18/18 6:02:50 PM.113 [003] [S]Data Path: /root/.config/AwesomeMinerService
10/18/18 6:02:50 PM.113 [003] [S]Log Path: /root/.local/share/AwesomeMinerService
10/18/18 6:02:50 PM.124 [003] [S]Updating settings
10/18/18 6:02:50 PM.124 [003] [W]Warning - Settings is null
10/18/18 6:02:50 PM.125 [003] [S]Current list of Active Miners:
10/18/18 6:02:50 PM.126 [003] [S]Saving configuration to: /root/.config/AwesomeMinerService/ServiceData.xml.tmp
10/18/18 6:02:50 PM.142 [003] [S]--> /root/.config/AwesomeMinerService/ServiceData.xml
10/18/18 6:02:50 PM.145 [003] [S]Starting Service Manager...
10/18/18 6:02:50 PM.156 [003] [S]IntelliServer::Start - Will listen on Port: 9630
10/18/18 6:02:50 PM.180 [003] [E]ChannelHandler::ReadAsync - Channel: 1 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:50 PM.192 [003] [S]Setting callback channel
10/18/18 6:02:51 PM.664 [011] [E]ChannelHandler::ReadAsync - Channel: 2 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:51 PM.665 [011] [S]Setting callback channel
10/18/18 6:02:51 PM.667 [011] [E]ChannelHandler::ReadAsync - Channel: 3 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:51 PM.667 [011] [S]Setting callback channel
10/18/18 6:02:53 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 5 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:53 PM.658 [011] [S]Setting callback channel
10/18/18 6:02:53 PM.669 [011] [E]ChannelHandler::ReadAsync - Channel: 6 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:53 PM.669 [011] [S]Setting callback channel
10/18/18 6:02:55 PM.655 [011] [E]ChannelHandler::ReadAsync - Channel: 7 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:55 PM.655 [011] [S]Setting callback channel
10/18/18 6:02:55 PM.661 [011] [E]ChannelHandler::ReadAsync - Channel: 8 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:55 PM.663 [011] [S]Setting callback channel
10/18/18 6:02:57 PM.656 [011] [E]ChannelHandler::ReadAsync - Channel: 9 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:57 PM.656 [011] [S]Setting callback channel
10/18/18 6:02:57 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 10 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:57 PM.658 [011] [S]Setting callback channel
10/18/18 6:02:59 PM.655 [011] [E]ChannelHandler::ReadAsync - Channel: 11 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:59 PM.655 [011] [S]Setting callback channel
10/18/18 6:02:59 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 12 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:02:59 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:01 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 13 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:01 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:01 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 14 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:01 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:03 PM.657 [011] [E]ChannelHandler::ReadAsync - Channel: 15 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:03 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:03 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 16 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:03 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:05 PM.656 [011] [E]ChannelHandler::ReadAsync - Channel: 17 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:05 PM.656 [011] [S]Setting callback channel
10/18/18 6:03:05 PM.658 [011] [E]ChannelHandler::ReadAsync - Channel: 18 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:05 PM.658 [011] [S]Setting callback channel
10/18/18 6:03:07 PM.660 [011] [E]ChannelHandler::ReadAsync - Channel: 19 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:07 PM.660 [011] [S]Setting callback channel
10/18/18 6:03:07 PM.663 [011] [E]ChannelHandler::ReadAsync - Channel: 20 failed
IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
10/18/18 6:03:07 PM.663 [011] [S]Setting callback channel
^C10/18/18 6:03:08 PM.283 [013] [S]Cancel key pressed
10/18/18 6:03:08 PM.283 [013] [S]ServiceContext.Shutdown
10/18/18 6:03:08 PM.284 [013] [S]Stopping service...
10/18/18 6:03:08 PM.285 [013] [S]Stopping client connections...
10/18/18 6:03:08 PM.293 [013] [S]Closing log
|
|
|
|
Any update on the API?  Hey soothaa, We have the API mostly done, but we need to do a bit more testing. Unfortunately, because we're so busy getting cnv8 working, we don't have the time to do a separate release for just the API before doing another release for cnv8. We should have the next release out with API and cnv8 support by Oct 18th, hopefully a bit sooner. I hope ya'll have good CNv8 performance.. looks like Lyra2z just got released to all the FPGA's out there so that algo will now be ded for all GPU mining  |
|
|
|
Anyone notice Zpool reporting wrong profit on Equihash? Had my 8x1080ti earning $49 PER day. How can we check this?
Most likely they changed their reporting from mBTC/MHs to mBTC/GHs or something like that. |
|
|
|
I'm not sure why buy SRB just never worked right for me. CastXMR has always been so simple.. I gravitate towards making my life easy |
|
|
|
|
I think Cast also will auto switch to CNv8
|
|
|
|
Any update on the API? |
|
|
|
|
Anybody got a nice website with countdowns to the Monero fork like last time? Should be soon shouldn't it?
|
|
|
|
|
Show Posts
