too much of a downtime lately
working on something or the server acts up ?
Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 220. (Read 837101 times)
May 22, 2013, 02:17:46 PM
May 22, 2013, 08:37:30 AM
Wow what a little run of good luck there! Nice job guys!
Also, looks like maybe realasicminer is on his way out? They have been cutting back here in the last couple days I think. Also what happened to testtest? Used to be 700,000 mh/s there at number 1/2 on the hash list.
Also, looks like maybe realasicminer is on his way out? They have been cutting back here in the last couple days I think. Also what happened to testtest? Used to be 700,000 mh/s there at number 1/2 on the hash list.
May 21, 2013, 10:55:43 AM
Thanks guys, I appreciate it 
And yeah, web sessions timing out is intentional. It's a long timeout though, much longer than most sites that handle money. I know it's annoying to get logged out of the livestats. Maybe I can get that to keep working, but still time out sessions so someone else can't cash out your bitcoins if you forgot to log out.
And yeah, web sessions timing out is intentional. It's a long timeout though, much longer than most sites that handle money. I know it's annoying to get logged out of the livestats. Maybe I can get that to keep working, but still time out sessions so someone else can't cash out your bitcoins if you forgot to log out.
May 20, 2013, 09:42:15 PM
I will join the crowd for the kudos do DrHaribo's great work and support. I leave most of my hashrate here. And the unlucky days are over ;-)
I also had a look at BitGamesInc, a link that he tweeted a couple of days ago, it looks very promising too. Mining for micro-payments, I was wondering who would be the first to make it in a viable way. It looks like they did!
I also had a look at BitGamesInc, a link that he tweeted a couple of days ago, it looks very promising too. Mining for micro-payments, I was wondering who would be the first to make it in a viable way. It looks like they did!
May 20, 2013, 09:40:11 PM
Apologies for the downtime.
One of the servers ran into low memory issues. Seems everything is happening today at once. I'll be working to improve stability during the next few days.
One of the servers ran into low memory issues. Seems everything is happening today at once. I'll be working to improve stability during the next few days.
Hey DrHaribo,
I've been testing around with several mining pools over the past 3 weeks and have now decided to stay with bitminter permanently.
The few main factors that gave me my decisions are:
1. You are always around to answer questions. From the site itself, it's obvious how dedicated you are to this pool.
2. Your statistic page is beyond amazing. Amazing.
3. Merged NMC mining.
You are doing a great job and I think I should at least made it known to you that someone here is appreciating all your work.
PS: I can't seem to stay permanently logged on the site. Is it an intended feature? Since google login bugs out sometimes and I have to try multiple times to get myself logged.
From my experience, it only keeps you logged in for as long as your browser is open, or a few hours, whichever comes first. It would be nice for it to stay logged in, but Google sign-in makes it relatively easy still.
May 20, 2013, 09:31:22 PM
I too am impressed with DrHaribo's pool, efforts and presence. It's been a stable environment, and truly "bitcoin mining made easy". I'm pretty impressed with the miner client, which I tried because I couldn't get cgminer to run for days on end. Although since I found cgwatcher, I'm back to cgminer.
Keep up the great work.
Keep up the great work.
May 20, 2013, 05:59:27 PM
Apologies for the downtime.
One of the servers ran into low memory issues. Seems everything is happening today at once. I'll be working to improve stability during the next few days.
One of the servers ran into low memory issues. Seems everything is happening today at once. I'll be working to improve stability during the next few days.
Hey DrHaribo,
I've been testing around with several mining pools over the past 3 weeks and have now decided to stay with bitminter permanently.
The few main factors that gave me my decisions are:
1. You are always around to answer questions. From the site itself, it's obvious how dedicated you are to this pool.
2. Your statistic page is beyond amazing. Amazing.
3. Merged NMC mining.
You are doing a great job and I think I should at least made it known to you that someone here is appreciating all your work.
PS: I can't seem to stay permanently logged on the site. Is it an intended feature? Since google login bugs out sometimes and I have to try multiple times to get myself logged.
May 20, 2013, 03:56:33 PM
Goody! Can you also add payout notification via email as well? 
It's on my list.
Down again?
I just restarted the mining backend to get an update in. Now it can recover by itself from some types of failure. It should also be better able to handle stormy internet weather disrupting communications between bitminter servers in different data centers.
More stability improvements coming soon..
May 20, 2013, 03:41:15 PM
Down again?
May 20, 2013, 08:44:25 AM
Can you please add Idle Worker Notification to Bitminter?
Yep, that's coming soon.Goody! Can you also add payout notification via email as well?
May 19, 2013, 03:52:58 PM
(latest git with minrelaytxfee set to 0.005)
I might have been mistaken: the git HEAD version uses satoshis for this parameter (which means it probably is faster than 0.8.1 even with defaults parameters). I converted it to satoshis and my latency is back to <0.10s. May 19, 2013, 03:35:28 PM
(latest git with minrelaytxfee set to 0.005)
I might have been mistaken: the git HEAD version uses satoshis for this parameter (which means it probably is faster than 0.8.1 even with defaults parameters). I converted it to satoshis and my latency is back to <0.10s. May 19, 2013, 03:30:41 PM
Thanks for the info, guys.
I also see bitcoind driving one CPU core at 100% for 1-3 seconds. That happens several times per minute. Looking at the log before and as it happens, the only thing I see is new transactions being received.
And yeah, memory usage is much much higher than it used to be.
Maybe I should try the latest from git. I don't like running code that hasn't seen much testing, though.
I also see bitcoind driving one CPU core at 100% for 1-3 seconds. That happens several times per minute. Looking at the log before and as it happens, the only thing I see is new transactions being received.
And yeah, memory usage is much much higher than it used to be.
Maybe I should try the latest from git. I don't like running code that hasn't seen much testing, though.
The on-disk storage format didn't change.
As a p2pool user with BitMinter as backup pool
I didn't have any hesitation testing the current git HEAD.If I were in your shoes, I'd make a backup copy of the blockchain with rsync (maybe using its --bwlimit parameter to avoid stressing your storage) in a backup dir while compiling the new bitcoind.
Archive the old bitcoind, move the new over.
Once these steps are done, stop bitcoind, rsync one last time (should be very fast) to make sure you have a consistent backup and start the new bitcoind.
Useful bitcoin.conf parameters for a pool owner who wants to minimize downtime:
Code:
checkblocks=72
checklevel=1
bitcoind startup is much quicker (defaults are 288 and 3 IIRC).checklevel=1
Any problem with the new bitcoind: stop and start the old one. Any on-disk corruption by the new bitcoind, stop, restore backup, start. Syncing a few hours/days worth of blocks should be fast.
May 19, 2013, 02:49:57 PM
Thanks for the info, guys.
I also see bitcoind driving one CPU core at 100% for 1-3 seconds. That happens several times per minute. Looking at the log before and as it happens, the only thing I see is new transactions being received.
And yeah, memory usage is much much higher than it used to be.
Maybe I should try the latest from git. I don't like running code that hasn't seen much testing, though.
I also see bitcoind driving one CPU core at 100% for 1-3 seconds. That happens several times per minute. Looking at the log before and as it happens, the only thing I see is new transactions being received.
And yeah, memory usage is much much higher than it used to be.
Maybe I should try the latest from git. I don't like running code that hasn't seen much testing, though.
May 19, 2013, 02:17:18 PM
Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.
Yeah, I'll probably make that the way it is sorted.
That's coming.
1. Ability to sort workers alphabetically
Yeah, I'll probably make that the way it is sorted.
2. Display my reward of each mined block on the Blocks (Income) page
That's coming.
There's a problem with some very large (in bytes) transactions slowing bitcoind RPC interface (getblocktemplate mainly) currently, p2pool users are battling with it. I find the latest git version is twice faster (but still slower than the average we are accustomed to).
I don't think it's size related. I think it's time related. Like there's a leak somewhere or something. Mine starts low and slowly gets larger.
M
bitcoind getmininginfo result:
Code:
{
"blocks" : 236952,
"currentblocksize" : 49792,
"currentblocktx" : 122,
"difficulty" : 11187257.46136079,
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1693,
"testnet" : false
}
Notice the pooledtx? There are lots of transactions waiting to go into a block. And I use aggressive settings (latest git with minrelaytxfee set to 0.005) to filter low fees transactions: blockchain.info reports more than 2300 tx totalling 13MB. So ordinary bitcoind installations are suffering right now. "blocks" : 236952,
"currentblocksize" : 49792,
"currentblocktx" : 122,
"difficulty" : 11187257.46136079,
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1693,
"testnet" : false
}
May 19, 2013, 01:53:42 PM
Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.
Yeah, I'll probably make that the way it is sorted.
That's coming.
1. Ability to sort workers alphabetically
Yeah, I'll probably make that the way it is sorted.
2. Display my reward of each mined block on the Blocks (Income) page
That's coming.
There's a problem with some very large (in bytes) transactions slowing bitcoind RPC interface (getblocktemplate mainly) currently, p2pool users are battling with it. I find the latest git version is twice faster (but still slower than the average we are accustomed to).
I don't think it's size related. I think it's time related. Like there's a leak somewhere or something. Mine starts low and slowly gets larger.
M
May 19, 2013, 01:32:10 PM
Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.
Yeah, I'll probably make that the way it is sorted.
That's coming.
1. Ability to sort workers alphabetically
Yeah, I'll probably make that the way it is sorted.
2. Display my reward of each mined block on the Blocks (Income) page
That's coming.
There's a problem with some very large (in bytes) transactions slowing bitcoind RPC interface (getblocktemplate mainly) currently, p2pool users are battling with it. I find the latest git version is twice faster (but still slower than the average we are accustomed to).
May 19, 2013, 01:10:31 PM
Thanks bro. Love your pool. Keep up the great work !
Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.
Yeah, I'll probably make that the way it is sorted.
That's coming.
1. Ability to sort workers alphabetically
Yeah, I'll probably make that the way it is sorted.
2. Display my reward of each mined block on the Blocks (Income) page
That's coming.
May 19, 2013, 01:00:04 PM
Keep up the good work DrHaribo. You have a great pool.
May 19, 2013, 12:55:04 PM
Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.
Yeah, I'll probably make that the way it is sorted.
That's coming.
1. Ability to sort workers alphabetically
Yeah, I'll probably make that the way it is sorted.
2. Display my reward of each mined block on the Blocks (Income) page
That's coming.
Jump to: