Search content
Sort by
Showing 14 of 14 results by ntgrac
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
I am like a cat in a room full of rocking chairs.I need my stats page.lol. good job keeping us mining slush.
You are not alone :-D
Thanks to slush too.
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
Good effort, slush, thanks. I wish there was a 'thanks' button for posts, so we could share the sentiments of other posts without bloating the lone, long thread. Thanks.
+1Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
I just migrated pool to another datacentre (longer story later...). There are three loadbalancers behind every of following DNS:
stratum.bitcoin.cz
stratum2.bitcoin.cz
stratum3.bitcoin.cz
So nine machines filtering the traffic right now. Balancers behind stratum.bitcoin.cz seems to be dead from the attack, but time to time I see some accepted connection. Once the connection is established, it will be kept by the balancer (that's nice advantage of Stratum protocol).
Please try these URLs in your miners, some of them will, at least after few tries, work for you.
stratum.bitcoin.cz
stratum2.bitcoin.cz
stratum3.bitcoin.cz
So nine machines filtering the traffic right now. Balancers behind stratum.bitcoin.cz seems to be dead from the attack, but time to time I see some accepted connection. Once the connection is established, it will be kept by the balancer (that's nice advantage of Stratum protocol).
Please try these URLs in your miners, some of them will, at least after few tries, work for you.
stratum3.bitcoin.cz is working like a charm for me!
Same here....working on ....>>>stratum3.bitcoin.cz
Thank you for your continued hard work.
working on stratum2.bitcoin.cz , but with some strange issues described here: https://bitcointalk.org/index.php?topic=178722
and with problem to subscribe:
Code:
2013-04-18 02:16:24: Listener for "Slush" started
2013-04-18 02:16:25: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:25, started OpenCL miner on platform 0, device 0 (ATI RV770)
2013-04-18 02:16:25: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:25, checking for stratum...
2013-04-18 02:16:30: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:30, no response to getwork, using as stratum
2013-04-18 02:16:41: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:41, Failed to subscribe
2013-04-18 02:16:43: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:43, IO errors - 1, tolerance 2
2013-04-18 02:16:25: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:25, started OpenCL miner on platform 0, device 0 (ATI RV770)
2013-04-18 02:16:25: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:25, checking for stratum...
2013-04-18 02:16:30: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:30, no response to getwork, using as stratum
2013-04-18 02:16:41: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:41, Failed to subscribe
2013-04-18 02:16:43: Listener for "Slush": stratum2.bitcoin.cz:3333 18/04/2013 02:16:43, IO errors - 1, tolerance 2
UN/PW it's OK
other servers have time outs.
I know it's slow. :-)
:p 'slow' wasn't meant in any devaluing way -- it's unfortunately a factor that adds some variance at higher difficulties and our difficulty is high :/Quote
It's in GUIminer.
I am not familiar with GUIminer and how/if it measures actual hardware device output or also looks only at the found shares rate which might be low when you cannot get any new work from the pool. Anyway: It appears that the only problem is the DDOS attack.Maybe it is, just waiting now.
i have a little problem with hashrate, before DDos i have 65 MH/s, on slush and BTC 50,
when i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
65 MHashes/s is by todays standard slow, hence difficult to estimate accurately. The pools only look at the rate ofwhen i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
incoming shares and it might take a while to average (bad) luck out.
Also, the DDOS attacks don't seem to be over yet, maybe use a backup pool until the attacks stop/are dealt with.
I know it's slow. :-)
Yes, i did that, I'm mining on backup pool.
Lot's of pools under DDoS rolling attack it seems.
It depends where you are looking to see your hashrate. If it is the estimate from the account page - that is affected by the last 10 rounds, for all workers together, or based on shares in current round for each worker. If you join a round already in progress, that will be a poor estimate. If your hashrate on your actual device as seen from miner output, well now that would be weird!
//shortened
It depends where you are looking to see your hashrate. If it is the estimate from the account page - that is affected by the last 10 rounds, for all workers together, or based on shares in current round for each worker. If you join a round already in progress, that will be a poor estimate. If your hashrate on your actual device as seen from miner output, well now that would be weird!
//shortened
It's in GUIminer.
change pool
that is the last optionHi,
i have a little problem with hashrate, before DDos i have 65 MH/s, on slush and BTC 50,
when i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
i have a little problem with hashrate, before DDos i have 65 MH/s, on slush and BTC 50,
when i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
Maybe it's a connection problem??
You mean pool connection or my connection?
Your connection to the pool.
I will try restart router and PC, have you some other ideas?
Hi,
i have a little problem with hashrate, before DDos i have 65 MH/s, on slush and BTC 50,
when i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
i have a little problem with hashrate, before DDos i have 65 MH/s, on slush and BTC 50,
when i reconnect after DDos to slush pool, i have 45 - 50 MH/s, on BTC 50 i have stilll 65 MH/s.
What am I doing wrong?
Maybe it's a connection problem??
You mean pool connection or my connection?
Hi,
i have a little problem with hashrate, before DDos i have 65 Mh/s, on slush's and BTC 50,
when i reconnect after DDos to slush's pool, i have 45 - 50 Mh/s, on BTC 50 i have stilll 65 Mh/s.
What am I doing wrong?
//Edit: on BTCGuild i have 65 Mh/s
on Slush's pool still 50 Mh/s
//Edit_2: Sorry guys, it's solved, i haven't selected the CPU affinity. Now it's all fine.
i have a little problem with hashrate, before DDos i have 65 Mh/s, on slush's and BTC 50,
when i reconnect after DDos to slush's pool, i have 45 - 50 Mh/s, on BTC 50 i have stilll 65 Mh/s.
What am I doing wrong?
//Edit: on BTCGuild i have 65 Mh/s
on Slush's pool still 50 Mh/s
//Edit_2: Sorry guys, it's solved, i haven't selected the CPU affinity. Now it's all fine.