Topic: [DOWN] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP - page 28. (Read 180847 times)
July 05, 2011, 04:18:48 PM
Thanks for the update.
July 05, 2011, 03:42:42 PM
We had issues there for a few minutes.
It should all be up now.
It seems something's wrong with our bitcoind patch.
Some kind of resource leak or similar, after about 24h it just stop's giving out work - without any reason.
Couldn't find anything wrong this time, at all.. not sure why.
EDIT: Still seems to be a few issues - we're working on it.
It should all be up now.
It seems something's wrong with our bitcoind patch.
Some kind of resource leak or similar, after about 24h it just stop's giving out work - without any reason.
Couldn't find anything wrong this time, at all.. not sure why.
EDIT: Still seems to be a few issues - we're working on it.
July 05, 2011, 03:39:22 PM
Pool having issues/DDoS?
Code:
2011-07-05 15:32:12: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:32:12] Phoenix 1.50 starting...
2011-07-05 15:32:15: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:32:15] Connected to server
2011-07-05 15:32:37: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:32:37] Warning: work queue empty, miner is idle
2011-07-05 15:33:23: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:23] Warning: work queue empty, miner is idle
2011-07-05 15:33:33: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:33] Disconnected from server
2011-07-05 15:33:39: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:39] Connected to server
2011-07-05 15:34:43: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:34:43] Warning: work queue empty, miner is idle
2011-07-05 15:36:12: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:36:12] Warning: work queue empty, miner is idle
2011-07-05 15:36:46: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:36:46] LP: New work pushed
2011-07-05 15:37:16: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:37:16] Warning: work queue empty, miner is idle
2011-07-05 15:38:47: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:38:47] Disconnected from server
2011-07-05 15:32:15: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:32:15] Connected to server
2011-07-05 15:32:37: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:32:37] Warning: work queue empty, miner is idle
2011-07-05 15:33:23: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:23] Warning: work queue empty, miner is idle
2011-07-05 15:33:33: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:33] Disconnected from server
2011-07-05 15:33:39: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:33:39] Connected to server
2011-07-05 15:34:43: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:34:43] Warning: work queue empty, miner is idle
2011-07-05 15:36:12: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:36:12] Warning: work queue empty, miner is idle
2011-07-05 15:36:46: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:36:46] LP: New work pushed
2011-07-05 15:37:16: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:37:16] Warning: work queue empty, miner is idle
2011-07-05 15:38:47: Listener for "Bitcoins.lc Phoenix": [05/07/2011 15:38:47] Disconnected from server
July 05, 2011, 09:19:59 AM
Sorry for being a bit inactive in this round.
I've worked hard with improving the pool and bitcoind/pushpoold. This have had some minor backsides with dropping hash rates due to failures in bitcoind etc.
It seems a lot more stable now then ever tho!
On an other note to - we just went from 500-550Gh to over 600Gh in just a few hours.
This is probably because BTC Guild is down, but it's good to see that the system holds up.
Even more improvements will come this week, including our new system that I've spoked a lot about.
(It's more or less a recoded version of the whole system to allow us to more easily add features and functions - including API and other user requested features)
I've worked hard with improving the pool and bitcoind/pushpoold. This have had some minor backsides with dropping hash rates due to failures in bitcoind etc.
It seems a lot more stable now then ever tho!
On an other note to - we just went from 500-550Gh to over 600Gh in just a few hours.
This is probably because BTC Guild is down, but it's good to see that the system holds up.
Even more improvements will come this week, including our new system that I've spoked a lot about.
(It's more or less a recoded version of the whole system to allow us to more easily add features and functions - including API and other user requested features)
July 04, 2011, 09:43:31 PM
Btw, yesterday must be some sort of mining record, pool luck -172%
I saw something like -16% on deepbit months ago, but.. wow.
(p.s. yes, I know it will likely average out tomorrow in the form of sub-1 hour rounds)
I saw something like -16% on deepbit months ago, but.. wow.
(p.s. yes, I know it will likely average out tomorrow in the form of sub-1 hour rounds)
July 04, 2011, 09:24:09 AM
The collective hashrate seems to bounce up and down randomly.
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
The stats on the web page don't mean much, they only show approximate values. I think it's because sometimes the pool website takes a 50 second long snapshot and sometimes a 70 second one, but calls them all mhash per minute. Stats are also randomly delayed, so that having good stats available can't be used against the pool. If you are mining and sending in accepted shares, then you get paid accurately for your work.
Things are summarized but even with time variable the stats for a time t are still going to average to be the same. With that said while this is happening my miners do report connection problems so there are some reoccurring issues. Some people jump to a backup pool when this happens, other miners may not recover, some recover fine but when it happens the pools hash rate will drop and take some time to recover.
July 04, 2011, 07:51:30 AM
The collective hashrate seems to bounce up and down randomly.
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
The stats on the web page don't mean much, they only show approximate values. I think it's because sometimes the pool website takes a 50 second long snapshot and sometimes a 70 second one, but calls them all mhash per minute. Stats are also randomly delayed, so that having good stats available can't be used against the pool. If you are mining and sending in accepted shares, then you get paid accurately for your work.
July 03, 2011, 03:55:48 PM
The collective hashrate seems to bounce up and down randomly.
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason
Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
July 03, 2011, 11:33:32 AM
Having Connection problems it seems... Both my miners --> Pool, and the website has been sporadic too.
DDoS? or other issues?
Thanks
Edit: 0922 PDT - ok.. seems issues have past... interesting.
DDoS? or other issues?
Thanks
Edit: 0922 PDT - ok.. seems issues have past... interesting.
July 02, 2011, 09:34:06 PM
It depends on the implementation of the Miner, if I were using multiple instances pointed at the same worker you are exactly right. I use Diablo which has a single set of threads of pushing work to and from all of the GPUs it handles. It's one of the oldest most mature miners out there and has always worked this way. The pool itself started having issues after the patch was applied and I happily use Diablo on any pool expect this one without any issues.
Ahh! I see! I haven't used Diablo, so I wouldn't know!
July 02, 2011, 12:39:49 PM
Jine,
Any word on the stale issue?
Any word on the stale issue?
The more I throw at it the worse it is, over 4.3 Gh/s pointing at the pool now, the faster the worker the higher the % of stales produced.
I run 7 total GPUs, and I get <.3%. Each has it's own worker!
It depends on the implementation of the Miner, if I were using multiple instances pointed at the same worker you are exactly right. I use Diablo which has a single set of threads of pushing work to and from all of the GPUs it handles. It's one of the oldest most mature miners out there and has always worked this way. The pool itself started having issues after the patch was applied and I happily use Diablo on any pool expect this one without any issues.
July 02, 2011, 10:59:40 AM
Jine,
Any word on the stale issue?
Any word on the stale issue?
The more I throw at it the worse it is, over 4.3 Gh/s pointing at the pool now, the faster the worker the higher the % of stales produced.
I run 7 total GPUs, and I get <.3%. Each has it's own worker!
July 02, 2011, 10:46:53 AM
Jine,
Any word on the stale issue?
Any word on the stale issue?
The more I throw at it the worse it is, over 4.3 Gh/s pointing at the pool now, the faster the worker the higher the % of stales produced.
July 01, 2011, 05:40:45 PM
Jine,
Any word on the stale issue?
Any word on the stale issue?
June 30, 2011, 10:19:25 PM
Please provide information about your setup and everything related that you could think of - and I'll have a look at it.
For now tho, something more funny:
"Bitcoins.lc is giving away FREE Google+ invites to MEMBERS - just retweet/share/spread this and send an e-mail to us!"
Link: http://twitter.com/BitcoinsLC/status/86613171061800962
For now tho, something more funny:
"Bitcoins.lc is giving away FREE Google+ invites to MEMBERS - just retweet/share/spread this and send an e-mail to us!"
Link: http://twitter.com/BitcoinsLC/status/86613171061800962
June 30, 2011, 09:56:58 PM
Just posed this for Diablo:
Quote
I didn't see this coming but it seems since bitcoins.lc patched their bitcoind to add support for socket reuse my primary rig running Diablo started getting 15% rejects. It seems my miners running 400Mh/s or so are alright but my main rig running at 2.3Gh/s is having a really hard time, other pools are no problems but bitcoins.lc is hating that speed on one worker. The backend is pushpool.
How would I go about running an instance per GPU or something similar, I hate the idea of doing it but it looks like that might be the only option?
How would I go about running an instance per GPU or something similar, I hate the idea of doing it but it looks like that might be the only option?
June 30, 2011, 09:55:59 PM
Any update on the stale shares? I threw another 2.2Gh/s back at it and I'm currently at 10% and climbing, this started with the patch yet other pools are still <1%.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
The strange thing is that this only seems to affect a few users.
Could you please provide a full description of the issue, including what miner and hardware you're using - and what internet conneciton (and ip).
I'll take a look at it then...
Jine,
Thanks for the reply, I just took a look at my other miners and see somthing, I run an aggregate of about 3.8Gh/s right now across a couple of machines.
Have the following stale percentages:
5770: .5%
5870: .25%
Primary 6 GPU 5970 rig: ~15%
The only one affected is my primary miner running 2.2Gh/s. Using DiabloMiner the 2.2Gh/s is on one worker and that is the only one having issues with rejects, with the patch you added it seems there is something about a single worker pushing through data that fast.
June 30, 2011, 09:47:30 PM
Any update on the stale shares? I threw another 2.2Gh/s back at it and I'm currently at 10% and climbing, this started with the patch yet other pools are still <1%.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
The strange thing is that this only seems to affect a few users.
Could you please provide a full description of the issue, including what miner and hardware you're using - and what internet conneciton (and ip).
I'll take a look at it then...
June 30, 2011, 09:37:21 PM
Any update on the stale shares? I threw another 2.2Gh/s back at it and I'm currently at 10% and climbing, this started with the patch yet other pools are still <1%.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
Didn't take long, leveling off at 15% stale shares, hoping it can be sorted out because 15% is too much to give up to the pool if alternatives are much lower.
June 30, 2011, 06:10:15 AM
I wonder when will Jine implement the Buy/Sell segments of the site. That would be a great feature, I know Jine ensuring that the pool is 100% operational and such. Also, like with Eclipse mining, having a Paypal direct withdraw option would be very nice especially with other miners having difficulty trading the coins. Just a thought.
Jump to: