|
au node down for maintenance. back up in 10 minutes.
|
|
|
|
|
booyaaa! more blocks please.
btw, not exactly p2pool specific but I use p2pool so if it makes a difference specifically to p2pool then also interested.
I have a handful of miners, all varying speeds, i'm best to:
1. point them all at my pool with the same wallet address (no manual diff set)
2. point them all at the pool with same wallet address and each with the suitable diff set as calculated off the hash rate
3. have them all on different wallet addresses with a manual diff set for each device based on it's hashing power
4. have all different wallet addresses and no need to worry about setting diff.
One lot of miners which is a mix of 2 x 2gh u2's, 1 x 2.5gh yellowjacket and a bfl single 30gh at one site
second lot is a single s1 at different site.
|
|
|
|
Looks like a drive failure on the main database machine... working on it.
Trying to get us back up, at least in failsafe mode, for now.
that sucks mate, hope you get it back up without any dramas. |
|
|
|
Hi all.
Please help: my Ant S1 has stopped work exactly after 3 months.
In Miner Status I constantly see ''This section contains no values yet''. Fan is working, but slowlier than it used to. Miner configuration: as always, I didn't change anything. In Overview I see from 3 to 16 connections (0%). There is connection to the internet (Ant do not beep). Green light in the middle of the first blade flashing (the blade, where is connector for ethernet cable).
I tried: Switch off and on several times. Clean it from dust. Reboot system.
What else should I try? Thank you.
eligius is in fail-safe and seems totally down. try adding a backup pool in case its your pool and not the miner yeah I would check the pool you are on. try pointing to another, there's one -VV- just down there -VV-  |
|
|
|
Tumbleweeds, where are the blocks?
I'd be interested still in updating my copy of p2pool stats. If anyone could assist with updating the db so it is useful it'd be much appreciated.
Ask and ye shall receive! haha in that case, some more blocks please! |
|
|
|
|
Tumbleweeds, where are the blocks?
I'd be interested still in updating my copy of p2pool stats. If anyone could assist with updating the db so it is useful it'd be much appreciated.
|
|
|
|
Is your cloud mining only on your own pool or can you point them at a pool of your choosing?
Only at our own pool. How big is your pool and are there any fees? |
|
|
|
|
Is your cloud mining only on your own pool or can you point them at a pool of your choosing?
|
|
|
|
|
do these work with cgminer and bfgminer? what is the error rate like? do you have any stats you can show us?
|
|
|
|
Looks like my pool stats did report normally after a couple shares were submitted, and I was also paid the other missing shares after I had restarted p2pool. Now I have a couple of questions maybe you can help me out with:
I would like to have each miner use a non wallet address rather than configure each miner with the same address for better individual tracking. I figured this could happen a couple ways, 1 would be to create a new receiving address in the wallet for each miner, but that seems to wasteful. 2. I was thinking to set the pool fee to 100% and set the -a payout address and then configure miners with any textual username I prefer.
How would one do this will the least amount of effort?
There's nothing wasteful with giving your workers individual addresses - and it's the easiest If you name a miner anything other than a direct wallet address then it'll go to the default wallet |
|
|
|
|
42-44 degrees. I've put a rear fan on out of an old antec power supply so it's staying quite cool.
|
|
|
|
Are you sure you didn't lose connection to the pool for whatever reason? Because that will also happen if its not hashing, meaning no connection to pool. If it happens again see if it is hashing. I would venture to guess its not a fan problem.
no the hashing looked fine and the miner status page showed everything hashing away merrily. the front fan had completely stopped though. |
|
|
|
|
I just had my ant start beeping at me and everything was up ok in the console. I looked over and the front fan had stopped. I rebooted and it was still stopped so I unplugged it and plugged it back in and it's happily spinning again.
should I replace the fan?
|
|
|
|
...
You need to use a recent cgminer https://github.com/kanoi/cgminer-binaries/tree/master/AntS1(bitmain's "cgminer" in the S1 and the S2 is ... very old) Then it will use the bitcoind getblocktemplate when it connects solo to bitcoind, however it needs the --btc-address option to know where to pay. Kano, with that driver, would you still recommend running the /0+diff option with p2pool or do you think the s1 is happy to work with it at default. Also my discarded have gone very very high Accepted 504 v discarded 14123. pool hash speed looks ok, should I be worried? You need to look at the correct fields to make sense of them. "Accepted" is usually confused to mean something it does not mean. "Difficulty Accepted" is usually what people are looking for. the +diff option is only useful if p2pool is assigning a lower work difficulty than you want to your ant - don't forget to give it a while to correct "Discarded" is the amount of unused work so doesn't represent anything with regards to anything but CPU usage. This is high due to the ridiculously high bitmain default --queue 9999 in their init script  Great, thanks for clearing that up.  |
|
|
|
...
You need to use a recent cgminer https://github.com/kanoi/cgminer-binaries/tree/master/AntS1(bitmain's "cgminer" in the S1 and the S2 is ... very old) Then it will use the bitcoind getblocktemplate when it connects solo to bitcoind, however it needs the --btc-address option to know where to pay. Kano, with that driver, would you still recommend running the /0+diff option with p2pool or do you think the s1 is happy to work with it at default. Also my discarded have gone very very high Accepted 504 v discarded 14123. pool hash speed looks ok, should I be worried? |
|
|
|
Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.
This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results. I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same Peace. whats the S1 miner tweaks he has done? Replacement updated version of CGMiner for the S1: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1awesome thanks! |
|
|
|
Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.
This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results. I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same Peace. whats the S1 miner tweaks he has done? |
|
|
|
Is it just me or did the p2pool hash rate just double to almost 1ph/s?!
I'm showing 682TH/s on my node, a nice jump.... If you have some new miners hitting your node you may want to set your share diff and pseudo share diff on your miner.... bitcoin_address/<share>+<pseudo_share> If your running S1's set <share> to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73) And <pseudo_share> to 220.4 (optimized for 190GH/s) <pseudo_share> is calculated as your hash rate in KH/s times 0.00000116 i.e. 190,000,000 * 0.00000116 = 220.4 Here is an example for an ant S1: 19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj/0+220.4 If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares... Thanks for the info. |
|
|
|
Getting ready for the next release of our front end this week, I believe I have all the data your looking for and would be happy to create a view for it. Would just need a little help putting together exactly what you are looking for....
I have active miners for a given p2pool block (addresses that were paid and how much)
I have node, pool, and global hashrate.
I think what you are looking for is the estimated hash rate per p2pool payout address based on the payment from the last block?
Yes, I believe that's what was shown on one of the tabs for p2pool.info. Since the site is still down, and using Norgon's clone of it as a reference (even though it's not up-to-date yet... blockchain data from 6 months ago), you can check out the Active Users tab. That shows the data I'm talking about: http://p2poolinfo.azurewebsites.net/Edit: from the disclaimer text on the clone site, it sounds a bit different. Based more on the valid shares submitted in the last 24 hours. It would essentially be the hashrate estimate corresponding to the current Payout Estimate shown on the various node UI's. From the p2pool.info clone: The following users / addresses have submitted at least 1 valid share in the past 24 hours. Note: Hashrates are very rough estimates based on the number of shares submitted in the past day. They may be off by 10-20% or more due to variance. Yea, those numbers look a little fuzzy to me... What do you think about instead showing this: [Address] - [Current Expected Payout] - [Last Block Payout] - [%+/-] For each miner with active shares in a block? I followed the deployment docs on that clone and it just won't update. Anyone know how I can get it up to date? |
|
|
|
|
Is it just me or did the p2pool hash rate just double to almost 1ph/s?!
|
|
|
|
|
Show Posts
