Show Posts
|
Pages: [1] 2 3 4 5 6 7 »
|
Good guy johoe. Hella props and good fortune to you.
|
|
|
Current pool rate: 370TH/s  I was like wat
|
|
|
I wanna try  Username: Squashpile
|
|
|
Correct.. thanks johnny, so can we say that, even after 36 hours, with that kinda hash power might not even get a share right?
|
|
|
A 0% fee pool like eligius or P2Pool. Why pay a fee?
|
|
|
246W @275 averaging around 141GH/s. Isn't that wattage high? THat's messed up. I need to redo it.
|
|
|
More blocks.. 0.06507941 on 1TH/s today so far. Not bad. One more today  You guys running nodes please advise. What is your average bitcoind RAM usage after a few days? I had been having some bitcoind crashing issues and recreated swap @ 2GB and changed swapiness and cache pressure. So far so good, but I'm curious on usage on other nodes. I have limited connections in Bitcoind to 40 too. I didn't mess with P2Pool connection limits (32/6 currently). I'm thinking I need to up the memory allocation if the swap changes don't work out. May be off-topic and need to post on support thread but the gurus are here.
|
|
|
Dat spike.. same thing on mine yesterday. Fun with share diff north of 40000 huh? Everyone left but me. lol In other news.. my expected payout is very nice today. We need to hit some blocks! In the chance this miner is on the thread, drop me a line.... 
|
|
|
bitcoinbearhk how is it going? Got an update on that 5 Th/s? I have had a good day. Defaults on s3's. I'm done messing with it. It works.
|
|
|
Good grief..ouch lol
New work for worker! Difficulty: 38074.924626
|
|
|
Pool over 3 PH/s right now. Noticed that the hash rate on P2Pool dropped significantly after the very lucky 4 blocks for today. Wonder if this is some kind of "unlucky avoidance" tactics? 
|
|
|
Nope.. that message is fine. No issues. I have got a lot of this message on my node:
Punishing share for "Block-stale detected .......
Does this mean anything bad?
|
|
|
You are good. DOA looks good compared to public nodes. I bet shares start rolling in. Stay with it  2hrs.. expected. Ha you good. Just restart everything if you are worried. 2.91 TH/s (DOA 70.50 GH/s / 2.43%) Expected time to share: 3h 40m 1 s That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all. You running on windows on linux? Got any screen output? Any P2Pool errors? I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope. Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs.... Actual share obtained so far: 1 total (1 ophaned, 0 good) ...... Pure bad luck or setup issue???  Seriously, should have got 6 shares under the "expected" scenario. P2Pool BTC Graphs Version: 13.4 Pool rate: 2.00PH/s (12% DOA+orphan) Share difficulty: 8820000 Node uptime: 13.5 hours Peers: 6 out, 0 in Local rate: 5.31TH/s (1.2% DOA) Expected time to share: 2.0 hours Shares: 1 total (1 orphaned, 0 dead) Efficiency: 0.000% Payout if a block were found NOW: 0.00823785 BTC to xxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0665 BTC per block. Current block value: 25.05109951 BTC Expected time to block: 14.2 hours 
|
|
|
That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all. You running on windows on linux? Got any screen output? Any P2Pool errors? I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope. Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs.... Actual share obtained so far: 1 total (1 ophaned, 0 good) ...... Pure bad luck or setup issue???  Seriously, should have got 6 shares under the "expected" scenario.
|
|
|
I have some undervolted s1's @140 here and rejected is .2%. I do remember trying Nicehash a while back and I think I had issues with my S1's. I'm not seeing that now for some reason. They were not undervolted before. I just tried westhash today for first time.
|
|
|
Ha.. well there ya go  Call off the raid.
|
|
|
p2pool.py --give-author 0 or whatever percentage  sad still no one can answer my question why that my Cointerra are only mining at 1320 GH/s instead of 1600 GH/s ...... SOS SOS SOS Anyway... another question please to my big brothers: I am new to p2pool, so not sure about how the share system works. How long will a share be paid? I mean how the the PPLNS system works in p2pool. I've heard someone once said the shares are paid for 3 days after it was found. Is that the case? Or are shares only paid the immediate next block? Oh and further, can someone teach me how to set the donation % on my node please? I see it's 1% by default.
|
|
|
I got your luck (miner luck).. after a real long unlucky streak. 0.21275023 mined since the 16th @ 1-1.1TH/s on P2pool. It's been crazy.
|
|
|
Let's get this party started. Block on deck
I'm using defaults on my s3 units and it's doing very well lately. 0.21275023 since Friday. Man that seems nuts. Amazing.. I think that would usually take around 7-8 days @ my HR.
|
|
|
That is suspicious on 3333. How did you notice this? I'm going to cap a bit with Wireshark. Is your pool on 3333? I'm guessing it's not or you would not have mentioned this. It would be very unusual for DNS traffic on that port as mjk mentioned. It's probably nothing. Talking about cgminer redirects, does anyone know who unknown.servercentral.net comes from? My S3 seems to be connected to it. Can't place it to any of the pools I use (slush and btcguild).
look like DNS thing 50.31.189.49 unknown.servercentral.net IP Address Information The Internet Service Provider (ISP) that owns the network address of 50.31.189.49 is Server Central Network and located in Illinois within the United States. The IP Address resolves to the DNS record of unknown.servercentral.net. Network Communications The following file have been seen to comunicate with this IP address in live environments. TCP port 3333 cgminer.exe I looked up that information too, which does not really give me any clue as to which pool it belongs. It connects on port 3333 so it really seems to be something to do with mining. that ip address wasnt pool but ip is for DNS. Odd that it's using that port though, DNS is usually TCP port 53.
|
|
|
|