I just realized that I have in total about 20% more accepted namecoin shares compared to bitcoin shares.
This was a crash we had earlier. The work tracking subsystem was seeing something from the database it didn't like. It tried to roll back transactions and retry them. Somehow despite rollbacks work data for the bitcoin round got registered multiple times. Not sure if I can fix the numbers now. Perhaps I could by comparing bitcoin and namecoin rounds, only problem is that they don't always end at the same time. I hope it's not too much bother seeing the extra proofs of work in the stats? In other news, BitMinter client v1.3.1beta2 is ready for testing: https://bitcointalk.org/index.php?topic=31163.msg1444466#msg1444466And... (drumroll) .. we have minted over 100 000 bitcoins now!
|
|
|
|
BitMinter client v1.3.1beta2 is ready for testing. The first beta tried to reduce CPU usage when mining on BFL FPGAs, but it gave a lower hashrate if you mined on Windows. Most of all with beta2 I would like to know how the hashrate and CPU usage compares to v1.3.0 when mining on different operating systems. So please test that if you have the opportunity! New since beta1: - Attempt to fix slowdown in beta1 when BFL mining on Windows
- Add workaround for SecurityException bug in some Java 7 releases. If you were running Java 7 but not the latest release then you may have experienced the client suddenly ceasing to mine. This will fix that. Also you could fix it by upgrading to the latest update release of Java 7. If you are on Java 6 don't worry about it.
- Fixed window being visible in taskbar when starting minimized in systray
- Suppress spammy "batch acquisition of 0 triggers" log messages
Please check it out:  |
|
|
|
So the website won't load but the API works now? Does it help restarting the browser, or using another browser?
restarting browser fixed it. That happened to me once too. Some kind of Cloudflare annoyance. Maybe it's cookie related. Or perhaps they change DNS settings and your browser still sticks with the old IP because of DNS pinning (a browser security feature). Whatever it is I hope it won't happen frequently. |
|
|
|
website seems to be unreachable. API is as well.
It works for me - tested right now. Maybe Cloudflare is being problematic. What are you seeing? Timeouts? 403 errors? I did see a cloudflare message "bad gateway error" Then I got: "website is offline, cached version is not available", with cloudflare referenced I'm still getting the 2nd error, but API is working. So the website won't load but the API works now? Does it help restarting the browser, or using another browser? |
|
|
|
website seems to be unreachable. API is as well.
It works for me - tested right now. Maybe Cloudflare is being problematic. What are you seeing? Timeouts? 403 errors? |
|
|
|
I was under the assumption I mentioned this to you on irc as I discovered it, apologies if I did not.
Could be that you did. I think this was months ago, and I don't remember all the details. I had a look at the numbers and I think I know what it was, but I need to check some more. I also investigated a problem today that can cause BitMinter client to stop downloading more work, causing all GPUs to run out of work. If you have the java console enabled you could see a SecurityException. This would happen randomly after some hours of mining. It's actually a bug from Java 6 that they fixed but it has later reappeared in Java 7. The client has a workaround in case you run a buggy version of Java 6 and a new beta will be out very soon with a workaround for Java 7. The problem should also go away if you update to the latest Java 7 release. |
|
|
|
I just realized that I have in total about 20% more accepted namecoin shares compared to bitcoin shares. Not speaking of per round shares here, those will obviously be wildly different because the chains don't have same difficulty. Maybe I just don't understand merged mining well enough, but shouldn't the total share numbers be roughly equal? I thought every share is used on both chains.
One crash some months ago did the same thing for my shares, cant remember what my hashrate was, but the difference stands at around 2 million shares. Thanks, that may have something to do with it. Those numbers do look odd. I will investigate. |
|
|
|
What is the minimum hashes to earn 1 btc per day? Mine's about 220 Khps and I can earn 0.1 mBTC/day (xD)
Note that there is a bug in the current BitMinter client versions. They don't take into consideration the reward halving and show twice the daily BTC. This has been corrected in the beta. This should be coming out of beta soon. I'm just busy with something else at the moment. Easy way to check average income and whether mining is profitable: google "bitcoin calculator" .. there are some pretty nice ones  |
|
|
|
|
Sorry for the slow server response this morning. Some buggy miners were hammering the server. It was pushing out up to 50 Mb/s of work data at times. After a restart the amount of work requests looks to be back to normal. I'll be working on ways to better deal with this.
Stratum didn't go away. But some miners seem to think that if there is 1 failure on Stratum then they should go back to getwork or getblocktemplate forever, where multiple failures are allowed (by the miner client). At least that's the impression I have. Perhaps it helps to specify explicitly in the config that you want Stratum by using a stratum+tcp://mint.bitminter.com:3333 URL, instead of relying on the miner to see the X-Stratum HTTP header and switch over automatically.
In addition to low traffic, Stratum has another advantage. It will never hammer the server with work requests because of a bug. With Stratum there are no work requests.
|
|
|
|
Happy new year Yeah, we are back online. There may be a little downtime now and then today as I make some changes, though. |
|
|
|
I'm not too concerned about merged mining as namecoin is useless.
Last I checked namecoins give about 3% extra income. Namecoins and transaction fees are much more important now after the reward halving. |
|
|
|
|
I am working on setting up with a new hosting provider. I'm sorry that payouts are delayed, but no coins are gone and payouts will be running as soon as I have things working again on a new server.
Regarding attack IPs and the type of attack... it's the pure amount of traffic of these DDoS attacks that is the problem. You don't block that with (your own) firewall. And there's no point posting the source IPs. They could be fake for all I know.
And no, BitMinter client isn't lacking failover pools because I don't want people to use those. It's lacking them because adding support for that takes time. I have a very long TODO list and I try to get things done one at a time.
I would like to improve handling of ddos attacks, namecoin crashes, buggy miners that do "friendly fire" ddos, and other service instabilities. I'd also like to set up multiple mining servers, not because the load requires it, but because it adds to stability. And in case all that fails I would like to have failover pools for BitMinter client, and also solo mining as a failover option. First of all I need to get the service up and running again, though.
|
|
|
|
Looks like we may be down a while. Also, I am looking for a new hosting provider, if anyone knows one that deals well with ddos attacks. If anyone has difficulties setting up mining on a different pool while we are down, feel free to ask here, or in the newbie section at https://bitcointalk.org/index.php?topic=22432.0 (if you have not been using bitcointalk before you are only allowed to post in the newbie section). |
|
|
|
|
No, I haven't received anything.
Last time there was an extortion email sent through the contact form on the website just before the attack started. Nothing this time.
|
|
|
|
|
Currently under ddos attack. That's why everything is down right now.
|
|
|
|
Do you attribute the significant decrease in mining power to be a result of the issues?
I think it is partly because of reward halving and partly because of the various issues that caused an unstable service lately. Of course miner bugs related to being disconnected by the server makes the consequences of a server failure more serious as it can cause miners to bug out as well. I am working on server stability and I am sure miner authors are working on their issues. |
|
|
|
Not sure if this is the same incident or not, but cgminer lost the pool for half an hour. Cgminer was stuck. Bitminter alive, but no work. Wouldn't fail over. Going to get the new version and see what happens.
After getting Stratum support it seems some miner programs had various issues. Crashing if the server disconnects them, going to failover and never returning to the main pool, or not going to failover pool at all. Just make sure you use the latest version of your chosen miner, things are getting sorted out. The good thing with ASICs being delayed for months is that by the time they arrive most client and server issues have already been fixed.  |
|
|
|
Date was 2012-12-20 17:29:06 UTC.
Nothing logged at that time. I don't really have any data to go on. Have you seen this multiple times or just that once? If it happens repeatedly I could add more logging to try and figure out what's going on. |
|
|
|
juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?
Yes, that's with stratum. The target is the exact same you mentioned previously, so the share should be accepted. Do you have the time when this happened? If so I'll have a look at the logs if there are any errors. Maybe the data is mangled somehow, so when the server hashes it the share doesn't even meet diff 1. |
|
|
|
|
Show Posts
