[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[slush]

Restarted all my miners, everything was fine, untill the last LongPoll

Now I get the 'Pool 0 not providing work fast enough'  messages again....

...which makes no sense for me. Actually LonPoll is *providing* job for miner, there's no need to ask server after LP broadcast.

[DutchBrat]

I'm now can't mine at your pool at all... I can ping it though....

Stopped connecting 35 mins ago, yet I see the current round get more shares, so the pool is not down completely

[slush]

what's your IP in miners? Isn't that mining.bitcoin.cz (instead of api.bitcoin.cz or api2.bitcoin.cz)? I redirected website (mining.bitcoin.cz) to new server roughly before half an hour, which can explain your troubles.

[slush]

Yes, I see that problem.

TO ALL MINERS: Don't USE http://mining.bitcoin.cz for your miners! Don't use IPs for your miners! Use just and only api.bitcoin.cz or api2.bitcoin.cz!

As a temporary solution I setup permanent redirect on port 8332 here, however some miners can have problems with following redirects. And also mining against website does not have any sense ;-).

[DutchBrat]

Ah, yes I am still at mining.bitcoin.cz

I'll restart my miners

To flush dns

I redirected them to api & api2... works like a charm now !

Thanks

[Crypt_Current]

Yes, I see that problem.

TO ALL MINERS: Don't USE http://mining.bitcoin.cz for your miners! Don't use IPs for your miners! Use just and only api.bitcoin.cz or api2.bitcoin.cz!

As a temporary solution I setup permanent redirect on port 8332 here, however some miners can have problems with following redirects. And also mining against website does not have any sense ;-).

Whew OK, yeah I was noticing some weirdness suddenly too, i'd better go change this...

thanks!

[AngelusWebDesign]

I know variance is a...err... "pain" and all, but heavens to betsy! is this the worst luck ever.
A 5:42 round, followed directly by a 6:56 round which *still* hasn't ended!!!
And this isn't some small pool with 400 GH/s. We've collectively thrown 1200 GH/s at this for hours and still can't get a block -- I notice the number is dropping, as people give up.

Slush better not go outside today -- an asteroid might fall on his head. Talk about HORRIBLE luck!

I think my income is going to be 1/3 of normal today -- which means I'm *losing* money.

[slush]

I notice the number is dropping, as people give up.

Um, no. I cut off ~100GHash by moving webserver (mining.bitcoin.cz) from London to France, then I realized a lot of people has been mining on this URL and setup HTTP proxy here, so this hashrate is back. Unfortunately miners using URL mining.bitcoin.cz  are routed thru France server, so their mining experience may be a little... crappy.

Except this issue there wasn't any downtime on pool today, so those two long rounds are just really bad luck. There's no reason to think that anything is wrong, I'm keeping my eyes on pool all day.

[bulanula]

I notice the number is dropping, as people give up.

Um, no. I cut off ~100GHash by moving webserver (mining.bitcoin.cz) from London to France, then I realized a lot of people has been mining on this URL and setup HTTP proxy here, so this hashrate is back. Unfortunately miners using URL mining.bitcoin.cz  are routed thru France server, so their mining experience may be a little... crappy.

Except this issue there wasn't any downtime on pool today, so those two long rounds are just really bad luck. There's no reason to think that anything is wrong, I'm keeping my eyes on pool all day.

So if my physical location is London which is the best URL or IP to be using ( api or api2 or something else ) ? It seems ATM I am not supposed to use an IP or mining.bitcoin.cz right ?

Thank you.

[slush]

Current migration status:

* Website is working in France very well
* There wasn't any issue on mining (if you're using correct URLs)
* The rest (database server, mining backends) are prepared for migration, I'll continue tomorrow.

[slush]

So if my physical location is London which is the best URL or IP to be using ( api or api2 or something else ) ? It seems ATM I am not supposed to use an IP or mining.bitcoin.cz right ?

It does not matter, both (api and api2) will point to France since tomorrow. But mining.bitcoin.cz won't be working since tomorrow anymore, I just setup routing thru webserver, which is dirty hack which is only giving time to users to fix their settings.

Btw latency between both servers is under 4ms, so if you're in London, the migration should not affect you at all - connection to France is excellent.

[jaybones]

In guiminer setup for slush pool
it points to mining.bitcoin.cz

im assuming people using guiminer need to choose Other
and enter api.bitcoin.cz or api2.bitcoin.cz
what port?

jay

[slush]

In guiminer setup for slush pool
it points to mining.bitcoin.cz

im assuming people using guiminer need to choose Other
and enter api.bitcoin.cz or api2.bitcoin.cz
what port?

jay

No, please use newer version instead (you're using almost half a year old miner!):

GUIMiner version 20110614 changelog:
- Slush's pool moved from mining.bitcoin.cz to api.bitcoin.cz

It also fixes many other issues, so I definitely recommend you to upgrade.

Edit: Btw mining port is 8332, as described on pool homepage.

[jaybones]

i have v2001-08-24
i didnt know there was new version..
could u link me the new one?

i'll try searching 4 it meen time

[slush]

Newest GUI miner (2008-08-24): https://bitcointalk.org/?topic=3878.0

Then you have correct GUI miner, so it should use api.bitcoin.cz correctly. Website is still mining.bitcoin.cz, of course.

[DutchBrat]

And we have reached 10 hours on the current block !!!

Let's see if we can make it 20

 

[slush]

And we have reached 10 hours on the current block !!!

Hehe, yes, it's going to be a little crazy.

What's your miner? Is it doing better on api.bitcoin.cz? Actually mining over webserver could be a reason for additional latency, because webserver was pretty overloaded (all those mining widgets polling webserver every minute are making me mad). And because webserver was doing only a proxy for your requests, I didn't see this latency in backend log.

[worldinacoin]

I know variance is a...err... "pain" and all, but heavens to betsy! is this the worst luck ever.
A 5:42 round, followed directly by a 6:56 round which *still* hasn't ended!!!
And this isn't some small pool with 400 GH/s. We've collectively thrown 1200 GH/s at this for hours and still can't get a block -- I notice the number is dropping, as people give up.

Slush better not go outside today -- an asteroid might fall on his head. Talk about HORRIBLE luck!

I think my income is going to be 1/3 of normal today -- which means I'm *losing* money.

And I thought my luck was bad.....

[DutchBrat]

And we have reached 10 hours on the current block !!!

Hehe, yes, it's going to be a little crazy.

What's your miner? Is it doing better on api.bitcoin.cz? Actually mining over webserver could be a reason for additional latency, because webserver was pretty overloaded (all those mining widgets polling webserver every minute are making me mad). And because webserver was doing only a proxy for your requests, I didn't see this latency in backend log.

It's absolutely fine now, I'm partly to blame myself since I have a widget running in chrome  

Thanks !!!

It will be a juicy namecoin payout for this block ! Already 50 NMC blocks have been found in this 10 hour period... running bad on one side and lucky on the other... I love merged mining 

[allinvain]

Wow this round is ridiculously long. The gods of odds are certainly against us on this one.