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

[milk]

Mining works somehow, but at a guestimated 80% rate. Login is still quite laggy, the funny picture may or may not appear 

[Litt]

man i'm getting so tired of miner idle messages.

[slush]

Hello, ddos is over for some time, mining should work normally.  Please check that you're using IP 178.79.179.32 (api.bitcoin.cz).

Edit: I'm going to restart balancer now, should be back in a minute.

[OCNewB]

Mining is working but the main website is somehow buggy still.

[sniper_sniperson]

Hello, ddos is over for some time, mining should work normally.  Please check that you're using IP 178.79.179.32 (api.bitcoin.cz).

Edit: I'm going to restart balancer now, should be back in a minute.

So some of us can't use the old address and should go to api.bitcoin.cz instead of mining.bitcoin.cz

[slush]

Hello, ddos is over for some time, mining should work normally.  Please check that you're using IP 178.79.179.32 (api.bitcoin.cz).

Edit: I'm going to restart balancer now, should be back in a minute.

So some of us can't use the old address and should go to api.bitcoin.cz instead of mining.bitcoin.cz

Actually, both mining.bitcoin.cz and api.bitcoin.cz still works, but really, change it on your side.

[Ruudsy]

hello slush,

have you anything changed about the api token or the json reqest??? i had a windows gadget running, which doesnt show my stats anymore! yersterday in the evening everything was all right ...

thanks!

[slush]

have you anything changed about the api token or the json reqest??? i had a windows gadget running, which doesnt show my stats anymore! yersterday in the evening everything was all right ...

Is website working for you? I didn't changed anything in this code. As site is up and running json stats should work, too.

[Ruudsy]

site is up!

ok, maybe something wrong with windows ;-)

[Justsomeforumuser]

What we have here is a failure to communicate.
The webinterface still reports mining progress, but I don't even want to know how much efficiency is lost simply due to dysfunctional communication.

Even if it isn't much, it just feels wrong to have errors pop up every 2-60 seconds.

I've popped in 178.79.179.32  directly as host now, maybe there was some DNS screwup or something.

Listener for "Default": 17/06/2011 15:24:14, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:24:28, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:01, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:19, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:25, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:31, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:37, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:40, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:42, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:44, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:47, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:49, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:51, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:53, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:56, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:25:58, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:00, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:03, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:05, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:07, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:09, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:12, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:14, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:16, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:19, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:21, Problems communicating with bitcoin RPC
Listener for "Default": 17/06/2011 15:26:27, Problems communicating with bitcoin RPC
etc etc etc

[Ruudsy]

site is up!

ok, maybe something wrong with windows ;-)

an update screwed it up, after installing and restarting there it was again!

[Justsomeforumuser]

Using 178.79.179.32  directly seems to have helped the comms.

[tommyl]

My stats seem to be wrong as well. They don't update as fast as they usually do. Anyone else have this problem?

Is this a problem with the webpage or am I losing BTCs here?

[Druas]

Using 178.79.179.32  directly seems to have helped the comms.

Same, but who really knows what is helping at this point. So much has changed.

[bradminer]

I've just set my two miners to this pool. First one runs ok (winXP), second has a hash rate 1/10 than usual (win7). Both run fine on other pools.

Thanks for help.

[TowlieLives]

Slush!  I went from lurker to member for one main reason, to thank you!  Your pool is my favorite, don't care what anyone says about it.  I've seen you on here night and day every time something goes wrong or the pool gets ddos'd.  So again, thank you thank you thank you!

[slush]

Everything seems to work fine right now, I don't see any problem with json api at all. Please check that you're using 'mining.bitcoin.cz' for calling api.

api.bitcoin.cz = getwork api for miners
mining.bitcoin.cz = website, json stats and everything else.

I see that some people are still accessing old IP (not *.32 one), it's probably their DNS cache issue. Unfortunately I cannot help with that.

Thank you for all your support, it really helps me with fighting those attacks.

[Jack of Diamonds]

Haven't had significant issues or RPC errors for over 24 hours. Upping another 2ghash to your pool.

[Justsomeforumuser]

I've been fine by using the IP directly now. I recommend doing this if you have been having issues these last few hours.

[d3m0n1q_733rz]

Hey Slush, it doesn't look like my miner is using long polling with your pool.  Is that just me or have you not incorporated that function into your pool as of yet?