Trump ftw! "Let's make crypto great again" lol would be a good slogan for this! SuchPool.pw/trump is hashing and ready for some more hash! |
|
|
|
|
I usually google the known nodes for the new coin to see if they are common with any other coins.
Back then, we debunked a lot of scamcoins that way.
|
|
|
|
Just so you all know we opened up a pool for Bitcoinultra! www.SuchPool.pw/btcuJoin us and grab some blocks! |
|
|
|
After setting up proper monitoring (screw you, Minera!) we found out our HW error rates are way low, in the order of 0.0018%. So thrilled seeing such low numbers.
As for the temps, our cooling setup isn't entirely completed yet. What is the temps you usually "accept" your blades to run at? I was seeing 63c on some miners, is that within reasonnable range? It's safe up to what temps?
Thanks for the help!
louiseth1, what are you using now to monitor your miners? You are using Nagios only to check temperature, right? Thanks. No, I am using Nagios with a set of custom plugins I have made pulling the cgminer-api of the S7's. I also graph all of that in PNP4nagios, graphs which then get included in our in-house "farm management" system. See an example below:  |
|
|
|
After setting up proper monitoring (screw you, Minera!) we found out our HW error rates are way low, in the order of 0.0018%. So thrilled seeing such low numbers.
As for the temps, our cooling setup isn't entirely completed yet. What is the temps you usually "accept" your blades to run at? I was seeing 63c on some miners, is that within reasonnable range? It's safe up to what temps?
Thanks for the help!
Opinions vary on this. But it has been observed with previous models: S5, S3, etc.. that lowering temperatures after a point also lowers the hashrate. So getting the absolute lowest temperature you can on those miners is not the way to optimize hashrate. I believe it is probably true of the S7 as well although I haven't run one in conditions where the temps get into the 40's as reported by the GUI. I am running mine in an environment where they are in the 60's most of the time. They do occasionally get as high as the low 70's (73 being the highest I have seen) on one or two boards for a few hours during certain times of the day depending on the outside temps. If they spent more time in the 70's I would probably make changes to bring down the temps. Previous generation miners were pretty much designed to run without AC but with some mechanism in place to get rid of the hot air. So in other words you could run them with room temp air going in without an issue. Makes sense. I had set my alarm tresholds on our Nagios at 60 celcius, I will have the alarms go up to 67 for warning, 70 for critical. The room runs at 25c intake temps, 35c exhaust temps. Monitored through RoomAlert 32w and their sensors. It's been "hotter" the last few days outside peaking at -3 celcius, at -20 celcius we intake 12-16celcius air inside and they tend to run at 40-45 degrees when that is the case. Thanks for the input. |
|
|
|
|
After setting up proper monitoring (screw you, Minera!) we found out our HW error rates are way low, in the order of 0.0018%. So thrilled seeing such low numbers.
As for the temps, our cooling setup isn't entirely completed yet. What is the temps you usually "accept" your blades to run at? I was seeing 63c on some miners, is that within reasonnable range? It's safe up to what temps?
Thanks for the help!
|
|
|
|
|
We were using Minera as a monitoring panel and found out the HW error % is totally innacurate.
After checking back directly on all antminer's interface we have a decent hw error rate. However, if we overclock our batch 7's they tend to raise above.
Nevermind my point then, our HW errors are well within acceptable range.
|
|
|
|
We are running about 100 of these units and the GLOBAL hw error state is of about 75%.
We have a huge number of hardware errors, on batch 6/7 miners at stock clock. Not sure where to go from that, these numbers can't be healthy.
Don't know what to do with this so far, other than downclocking but such high numbers aren't normal.
Wasn't batch 6 supposed to run at 600 mhz and batch 7 at 625 mhz default? Yes, sorry I had my numbers wrong. Those are Batch 8's. They come overclocked at 700 mhz per default, and have 45 chips per board. |
|
|
|
We are running about 100 of these units and the GLOBAL hw error state is of about 75%. We have a huge number of hardware errors, on batch 6/7 miners at stock clock. Not sure where to go from that, these numbers can't be healthy. Example of 1 miner:  And another one:  Don't know what to do with this so far, other than downclocking but such high numbers aren't normal. |
|
|
|
Stratums stopped since PoW has ended! You may withdraw your earnings from www.SuchPool.pw/scrt - we'll keep it online for a while to let you withdraw. |
|
|
|
We have added a pool following a request. This coin looks like a good ol coin, so happy to add it on our pool. www.SuchPool.pw/scrt Thanks dev to add our pool to the OP! |
|
|
|
Guys, http://umine.co.uk/ is offline. (( sent to such and aika now (our favourite pools ) + our pool soon Received your request! I'm at work, quite a bit busy at the moment but as soon as I have spare time I will add a pool for your coin  Our Rubit pool is now ready! www.SuchPool.pw/rubit
Come mine, we have 3 ports for the different type of miners. 1% fee. Support on irc.freenode.net on #SuchPool !
Thanks |
|
|
|
Simple solution is to spread hashrate amongst all pools! We're in need of some hashrate while some other pools have too much hashrate, spread some towards www.SuchPool.pw/xmgThanks! |
|
|
|
Coryvmcs1 is an nice Dude, worked hard for it. But coins back, Dev, helped, thatīs why i love INFX. Straight guy
Straight up, these developpers were a pleasure to work with and very cooperative. Big props to the INFX team! |
|
|
|
Dev has helped us fixing this situation. Missing coins were compensated, payouts are running so you can withdraw your balances.
We'll fix the accounting issues we have in our blockfinder scripts and will resume mining in the evening or tomorrow morning at the latest.
Thanks yall!
Allthough we try to notify all parties involved there can sometimes be a slip in the communication. I had notified as many pools explorers Exchanges as I could. Given that we also gave two weeks notice before the fork we thought it would be ample time. I am sorry for Suchpool Miners and to Louis for the headache. What I do love about all is the ability to make things right and not to hold grudges. Please let me or anyone on the INFX team know if you need any further assitance. We are here to help and appologize for one of our biggest supporters slippnig through the cracks. It won't happen again Louis I can promise you that.
We spawned a whole NEW pool onto www.SuchPool.pw/infx - stats are zeroed out, balances are wiped and everything is like new.
For those who HAD balances and wanted to see their previous stats, we have replicated the "broken" pool on www.SuchPool.pw/infxold . You can't mine there but payouts are working and you can withdraw the coins you had on the INFX pool and view your statistics. We have cheated the database to mark all orphaned (forked) blocks with 120 confirmations, this way the miners who mined during the fork ARE getting paid for those blocks using the amount that the developpers have given us towards compensation.
Mining is resumed onto www.SuchPool.pw/infx
Thank you all for your patience and trust, thanks also to the devteam who was pretty responsive (came to us within an hour or two) and which compensated our miners! |
|
|
|
|
Dev has helped us fixing this situation. Missing coins were compensated, payouts are running so you can withdraw your balances.
We'll fix the accounting issues we have in our blockfinder scripts and will resume mining in the evening or tomorrow morning at the latest.
Thanks yall!
|
|
|
|
|
We have had an issue on our pool...
There was an update, developpers did not let us know whatsoever, therefore we ended up mining the wrong fork for 4 days.
It's the developper's responsibility to notify his coin's related services regarding codefixes/updates that could impede the network's stability, especially when there is only a few related services.
Basically 2500 INFX were lost due to the fork (mined on the wrong chain but credited to miners)
We stopped our stratums and the findblock cronjobs, left only the payouts jobs.
That's it for the time being, unless the dev can find some sort of compensation for his lack of communication towards the services which support his coin we won't be restarting the stratums.
EDIT: Developpers have been very understanding and sent us the missing coins to cover the fork issue. We will work at manually fixing the findblock cronjobs which will likely take a good amount of hours, but at this time you can still withdraw your coins whenever you feel like it, nothing's missing in the end. Mining will probably be resumed tomorrow morning, once we are finished correcting the accounting issue created by the fork.
Thanks all!
|
|
|
|
Oddly enough this is the best looking launch in a few weeks.
Sadly it is one of the best looking ones but still not nice enough for us to put a pool up. I wish we had some decent coins to come out on a non-eth base. Some pool ops have lower criterias, we hope them all the best hosting this kind of coin. |
|
|
|
Cloud staking sites !! Are they reliable? How do we trust and put the coins on some external sites?
It's always risky especially if they are still under BETA. I would use it but with extreme caution! |
|
|
|
By the way thanks for helping us solve some blocks, we really appreciate!
You are welcome amigo. Think there is space for more miners right? I will keep promoting your pool also. Sure, we can stack 10's of thousands more without issues!  |
|
|
|
|
Show Posts
