Well if there is one thing that I've learned about bitcoin mining pools is that they're not exactly easy on server resources and it seems it's quite a challenge to keep a pool running without any problems. Also let's not forget the potential for getting DDoS'ed too!
Amen. |
|
|
|
|
I've troubles with database, pool was down for ~20 minutes. I modified database configuration, should be better next time.
|
|
|
|
Damn!
5043 2011-06-02 16:46:17 3:05:53 1671479 - invalid
5042 2011-06-02 13:40:24 1:48:14 981119 - invalid
Bloody long runs .. and with no payout! Probably due to network problems these precious block did not get to propagate fast enough.
Good news! Marking those blocks as invalid was network glitch. I investigated them (as I do for every invalid blocks) and found they were generated by pool. So you can check stats now, your reward for those blocks are on your accounts... |
|
|
|
For a lot of block there is no reward ? What's the point ? There is a minimal amount under there is no reward at all ?
Or it is related of full block processing ?
Hello, 0.6Mhash/s is _really_ slow worker, so your reward is +- fine. With such slow computer, you're hitting shares just for few blocks per day... |
|
|
|
|
I'm waiting on Linode developers response, I forced them before few minutes again. I hope it will be solved today.
|
|
|
|
Actually I just got it after like 10 attempted downloads on multiple PC's.
I'm solving it with server support, should get better soon... |
|
|
|
|
Pool will be down for ~15 minutes, I need to upgrade load balancer. Second load balancer will be in failover setup soon, which will prevent such outages in the future. I'm sorry for troubles...
Update: Talking with Linode support, we reached some soft limits on network layer. I'm negotiating rising of those limits, which should fix packetloss and timeouts. Stay tuned...
|
|
|
|
Maybe this is way last block took 3:05 hours
No, shares are still counting. It may of course affect total pool hashrate, but not shares per round ratio.... |
|
|
|
|
Hi, I'm solving this issues on load balancer, should be better in few hours.
|
|
|
|
Yep, down  . |
|
|
|
When the block being solved awards transaction fees, are those being divided up amongst participants?
No, fees are currently not divided, as in other pools. |
|
|
|
This is what I'm curious about now!
Current shares CFD: 100.00 %
Current Bitcoin block#: 0
bitcoind on webserver stopped working, it is running now. This is really annoying, because pool is using last bitcoind version which should solve lockup problems and it fall down after long time of smooth operation... |
|
|
|
Now Slush's website is down.
It was down for a moment because of migration to better server. Now it should be stable and much faster. |
|
|
|
Now it does not seem that on slush's site you can change your login password....at least as far as I've seen.
You can, use link on login page. Obviously certain pool members in slush's pool are thieves.
Pretty strong claim. Why necessary *members*? Login page is open for anybody and you used weak password. So be careful. It might worth paying a higher commission somewhere else
You don't need to pay higher commissions somewhere else. You have to setup stronger password. Please don't spread FUDs. |
|
|
|
Reward calculation was stopped for some time because of website migration. I recalculated rewards on new server then. So everything should be fine  / |
|
|
|
4979 2011-05-31 14:14:18 0:15:07 124173 0.xxxxxxxxx 127803 64 confirmations left
4978 2011-05-31 13:59:11 0:01:43 13200 0.xxxxxxxxx 127803 64 confirmations left one of those should actually be 12780 4... Fixed... |
|
|
|
I often get error 502 when I try to go to the website is there a DDOS Attack maybe?
Or is it just a normal Problem?
I don't know why no one responded to you already, but this is a problem as of late when the web front end for the pool has a problem or is overloaded. Slush has noted being victimized by some dDoS attacks lately so I don't know if that could be the case now as well. My miners are still connected though so it is just the UI right now. Recent 50x erros were related to website migration. Website stability should be much better now. |
|
|
|
|
Oh, I completely missed this thread. Yes, my pool was DDoSed - around 100Mbit/s of incomming traffic between 2am - 4am UTC. Then it went back to normal operation.
Btw Bitcoincharts.com is using hashrate from pools websites to draw chart. So when website is down/DDoSed and Bitcoincharts show zero % of some pool, that does not necessary mean that all pool hashpower is gone...
|
|
|
|
The password reset doesn't seem to be working for me, I've tried it several times and it always says it was reset successfully but then I can't log in again. This is for the admin password, my miner credentials work fine. The username I used is skorgu+bitcoincz@gmail.com and I'm using the reset link on the login page: http://mining.bitcoin.cz/accounts/password/reset/ I tested password reset now and it works fine. I'm receiving many similar emails about password reset and every time people find that they made some mistake . Please be sure that you really typed same passwords on both forms (reset & login) . Also try to delete passwords from browser's password manager; many people told me that some browsers are using old password for login form. |
|
|
|
|
Hello, it was pretty nasty DDoS attack (over 100Mbit/s). Report later...
|
|
|
|
|
Show Posts
