To all people spamming me with IP lists on all possible channels  . Please, stop this, I'm unable to find relevant messages now. I have many pages of unread emails in gmail and so on. Everybody will be able to enter his email IP/address on profile page, stay tuned. I'm working on it. |
|
|
|
I'm having the same problem. The machine ran fine most of last night (until I went to sleep). When I woke up I got the following:
PLease read pool's forum thread, everything explained here. |
|
|
|
|
During the DDoS, hashrate wasn't distributed proportionally. Somebody was more lucky and was able to submit shares, somebody does not. So it's completely worthless to ask 'why my reward for block during that attack is lower/higher than usually'. Attack itself is the reason.
I'm sorry, but I'm unable to manage whitelist manually; I was literally DDoSed by IRC, PMs, emails, skype messages, jabber messages etc. Most of users is whitelisted, but please be patient, I'm now working on web interface for whitelisting IPs.
|
|
|
|
|
All IPs sent me via PM or email until now are whitelisted. Those miners with dynamic IPs (dyndns etc) will be solved in release introducing ip whitelist on website later today.
|
|
|
|
the mining2 does not work for me (web is fine, but miner does not connect)
If web is working, but mining interface isn't, PM me your IP address... |
|
|
|
I can't connect now, the site just times out  Been using this pool for a week or so now, how old is that list? Oh, I forgot. Use http://mining2.bitcoin.cz, at least temporary. |
|
|
|
I can't connect now, the site just times out Been using this pool for a week or so now, how old is that list? site isn't behind whitelist, so this must be something else. |
|
|
|
|
I solved DDoS by whitelisting IPs of miners, but that log of IPs is few days old. This means that you might have problems with connecting to pool, because you're new in this pool.
It is just temporary solution, I'm working on possibility to whitelisting your mining addresses on web interface, which will be available later this day.
|
|
|
|
|
Pool is back up. I had to change IP, so it might take a while to refresh DNS on your miners. You can speed it up by pointing miners against "mining2.bitcoin.cz". I recommend this change to all miners, at least temporary. Original domain might not work for some time...
|
|
|
|
was hard to ask in pool's main thread?
Please don't open new topic for everything, it's a mess then. I'm not going to follow this thread, please continue there. Also, there is already a response to your question.
He is not welcome to post any other place than right here because he is a newbie. It was not his choice it is the policy of this forum. Oh, sorry, didn't know about this rule. |
|
|
|
can anyone connect to mining.bitcoin.cz?
was hard to ask in pool's main thread? Please don't open new topic for everything, it's a mess then. I'm not going to follow this thread, please continue there. Also, there is already a response to your question. |
|
|
|
Thanks for the update slush. Once you deal with the DDoS attack can you please have a look at my post about my account getting hacked.
Of course, later. I woke up just because ddos now. |
|
|
|
|
That issues are called ddos, I'm solving it.
|
|
|
|
The pool is growing and just passed the 1.8 TH/sec mark. Currently the total network hashrate is 6.7 TH/sec and Deepbit still has the lead with 2.2 TH/sec.
So if Slush's pool surpasses Deepbit, how soon till we start seeing all those "LEAVE SLUSH' POOL IF YOU WANT TO SAVE BITCOIN!" threads?
Actually hashrate is spreaded between many pools and no one is reaching 50% of the network, so I think things are getting better . |
|
|
|
who can explain this to me, 2x 5970 shown on console 1300 Mhash/s and in my account 1090 Mhash/s
Something isn't right here or am I missing something ?
No, calculation on profile page is made from shares of current round and it is expected to be very inaccurate. Actually 1Ghash from real 1.3 Ghash is pretty good estimation, nothing to worry about. |
|
|
|
Yea, I mean. I don't really get how all these works. It's in the name of reducing exploits and all I get it. If it's luck I get it. It's almost a 7th day and my average is going no where near my calculated. This is not right, I thought all these is not suppose to affect your reward 'that' much. We're still suppose to be able to go close to the calculated (expected) reward. It was 3.18 the day I posted about this. That is less than 50%, it's 5 on the last graph. My expected is 7.33 my 7-day average is 4.37. What's going on?
P.S And it even had a high system reward on the last graph 2800 BTC.
Yes, score system should not affect mining income so much and definitely not over so long period. Do you see any troubles on miner side? Unusually high invalid ratio, idling miners or something? Do you use separate worker accounts for every gpu? It may be really something small.... |
|
|
|
Yea precisely my point. It's suppose to go closer (more or less) to the expected figure. 2.3 is A LOT of difference in my opinion (I'm not sure if it's this much of a difference), so I'm asking around unless everyone is getting a 2+ tolerence or I'm missing something...
And 2+ is a modest estimate because I only hit the maximum of 5 BTC only 2 times. I'd like to know if this is a common thing or do everyone get so much a difference from the calculator then I don't understand how people are getting into mining so blindly putting faith into the calculator.
If you're giving only 50% performance all the time, then something is probably wrong. There are too many factors which can hurt your earnings: mining hardware itself (are you really mining at expected hashrate?), connection quality (any connection downtime?), network lags (what's your ping/packetloss?). Then of course luck (but should not be *so* important), pool downtime (yesterday it was around 15 minutes in total caused by attack) and weird thinks like using all gpus on same worker etc. Daily rewards fluctuate a bit on my miners, too. It's pretty natural to mining process. But I'm not observing such huge drops, so I'm expecting something wrong on your side. |
|
|
|
Lets hope the 1 second one is invalid then. Would suck to crunch for 3 hours and then have it divided between 52 shares in the end (of which I had none of course ). Yes, invalid is that one with 53 shares. Too bad for being invalid, afaik it is all time record, previous one (but valid) was 83-shares round. But it was in times of 30k difficulty . |
|
|
|
"other" raising fast ... 3 hour 1 thash block .. that makes me wondering ...
I have no reason to think that this 3hour round was caused by some p2p network attack (except that pool hashrate was lower for some time because of that DoS). Also keep in mind that 'other' are just estimation. There is no way to measure 'other' hashrate exactly. |
|
|
|
Ow wow, a 1 second round?
Unfortunately invalid one. Actually two servers found solution for the same block almost at same time (heh, after 3 hours of trying), but only one can count. 1 sec is too short to synchronize over bitcoin p2p... |
|
|
|
|
Show Posts
