Problem with Slush's Pool

[Bongo098]

Hi there, I'm new here and my English is not perfect, please excuse me...

Because I'm not able to reply to the orginal Threat ( http://forum.bitcoin.org/index.php?topic=1976.msg226123 ) i post my request here:

I am mining with the GuiMiner i already have set the adress to: api.bitcoin.cz like its said on the Webside... but the GuiMiner show me that in Consol:

Code:

2011-06-16 12:54:47: Listener for "api.bitcoin.cz": 16/06/2011 12:54:47, Problems communicating with bitcoin RPC
2011-06-16 12:54:51: Listener for "api.bitcoin.cz": 16/06/2011 12:54:51, warning: job finished, miner is idle
2011-06-16 12:55:30: Listener for "api.bitcoin.cz": 16/06/2011 12:55:30, Problems communicating with bitcoin RPC
2011-06-16 12:56:20: Listener for "api.bitcoin.cz": 16/06/2011 12:56:20, Problems communicating with bitcoin RPC
2011-06-16 12:58:21: Listener for "api.bitcoin.cz": 16/06/2011 12:58:21, Problems communicating with bitcoin RPC
2011-06-16 13:01:12: Listener for "api.bitcoin.cz": 16/06/2011 13:01:12, Problems communicating with bitcoin RPC
2011-06-16 13:06:12: Listener for "api.bitcoin.cz": 16/06/2011 13:06:12, Problems communicating with bitcoin RPC
2011-06-16 13:07:46: Listener for "api.bitcoin.cz": 16/06/2011 13:07:46, Problems communicating with bitcoin RPC
2011-06-16 13:07:51: Listener for "api.bitcoin.cz": 16/06/2011 13:07:51, Problems communicating with bitcoin RPC
2011-06-16 13:08:55: Listener for "api.bitcoin.cz": 16/06/2011 13:08:55, Problems communicating with bitcoin RPC
2011-06-16 13:09:19: Listener for "api.bitcoin.cz": 16/06/2011 13:09:19, Problems communicating with bitcoin RPC
2011-06-16 13:12:26: Listener for "api.bitcoin.cz": 16/06/2011 13:12:26, Problems communicating with bitcoin RPC
2011-06-16 13:13:38: Listener for "api.bitcoin.cz": 16/06/2011 13:13:38, Problems communicating with bitcoin RPC
2011-06-16 13:14:18: Listener for "api.bitcoin.cz": 16/06/2011 13:14:18, Problems communicating with bitcoin RPC
2011-06-16 13:14:26: Listener for "api.bitcoin.cz": 16/06/2011 13:14:26, warning: job finished, miner is idle
2011-06-16 13:14:27: Listener for "api.bitcoin.cz": 16/06/2011 13:14:27, Problems communicating with bitcoin RPC
2011-06-16 13:22:28: Listener for "api.bitcoin.cz": 16/06/2011 13:22:28, Problems communicating with bitcoin RPC
2011-06-16 13:22:33: Listener for "api.bitcoin.cz": 16/06/2011 13:22:33, warning: job finished, miner is idle
2011-06-16 13:23:02: Listener for "api.bitcoin.cz": 16/06/2011 13:23:02, Problems communicating with bitcoin RPC
2011-06-16 13:23:31: Listener for "api.bitcoin.cz": 16/06/2011 13:23:31, Problems communicating with bitcoin RPC
2011-06-16 13:23:51: Listener for "api.bitcoin.cz": 16/06/2011 13:23:51, Problems communicating with bitcoin RPC
2011-06-16 13:25:04: Listener for "api.bitcoin.cz": 16/06/2011 13:25:04, Problems communicating with bitcoin RPC
2011-06-16 13:25:22: Listener for "api.bitcoin.cz": 16/06/2011 13:25:22, Problems communicating with bitcoin RPC
2011-06-16 13:27:35: Listener for "api.bitcoin.cz": 16/06/2011 13:27:35, Problems communicating with bitcoin RPC
2011-06-16 13:28:02: Listener for "api.bitcoin.cz": 16/06/2011 13:28:02, Problems communicating with bitcoin RPC
2011-06-16 13:28:16: Listener for "api.bitcoin.cz": 16/06/2011 13:28:16, Problems communicating with bitcoin RPC
2011-06-16 13:29:22: Listener for "api.bitcoin.cz": 16/06/2011 13:29:22, Problems communicating with bitcoin RPC
2011-06-16 13:29:32: Listener for "api.bitcoin.cz": 16/06/2011 13:29:32, Problems communicating with bitcoin RPC
2011-06-16 13:31:18: Listener for "api.bitcoin.cz": 16/06/2011 13:31:18, Problems communicating with bitcoin RPC
2011-06-16 13:33:10: Listener for "api.bitcoin.cz": 16/06/2011 13:33:10, Problems communicating with bitcoin RPC
2011-06-16 13:33:23: Listener for "api.bitcoin.cz": 16/06/2011 13:33:23, Problems communicating with bitcoin RPC
2011-06-16 13:33:35: Listener for "api.bitcoin.cz": 16/06/2011 13:33:35, Problems communicating with bitcoin RPC
2011-06-16 13:34:19: Listener for "api.bitcoin.cz": 16/06/2011 13:34:19, Problems communicating with bitcoin RPC
2011-06-16 13:38:36: Listener for "api.bitcoin.cz": 16/06/2011 13:38:36, Problems communicating with bitcoin RPC
2011-06-16 13:39:22: Listener for "api.bitcoin.cz": 16/06/2011 13:39:22, Problems communicating with bitcoin RPC
2011-06-16 13:39:27: Listener for "api.bitcoin.cz": 16/06/2011 13:39:27, warning: job finished, miner is idle
2011-06-16 13:39:28: Listener for "api.bitcoin.cz": 16/06/2011 13:39:28, Problems communicating with bitcoin RPC
2011-06-16 13:40:33: Listener for "api.bitcoin.cz": 16/06/2011 13:40:33, Problems communicating with bitcoin RPC
2011-06-16 13:42:49: Listener for "api.bitcoin.cz": 16/06/2011 13:42:49, Problems communicating with bitcoin RPC
2011-06-16 13:44:33: Listener for "api.bitcoin.cz": 16/06/2011 13:44:33, Problems communicating with bitcoin RPC
2011-06-16 13:46:22: Listener for "api.bitcoin.cz": 16/06/2011 13:46:22, Problems communicating with bitcoin RPC
2011-06-16 13:46:46: Listener for "api.bitcoin.cz": 16/06/2011 13:46:46, Problems communicating with bitcoin RPC
2011-06-16 13:46:58: Listener for "api.bitcoin.cz": 16/06/2011 13:46:58, Problems communicating with bitcoin RPC
2011-06-16 13:48:29: Listener for "api.bitcoin.cz": 16/06/2011 13:48:29, Problems communicating with bitcoin RPC
2011-06-16 13:52:24: Listener for "api.bitcoin.cz": 16/06/2011 13:52:24, Problems communicating with bitcoin RPC
2011-06-16 13:54:05: Listener for "api.bitcoin.cz": 16/06/2011 13:54:05, Problems communicating with bitcoin RPC
2011-06-16 13:58:09: Listener for "api.bitcoin.cz": 16/06/2011 13:58:09, Problems communicating with bitcoin RPC
2011-06-16 13:58:14: Listener for "api.bitcoin.cz": 16/06/2011 13:58:14, Problems communicating with bitcoin RPC
2011-06-16 14:03:14: Listener for "api.bitcoin.cz": 16/06/2011 14:03:14, Problems communicating with bitcoin RPC
2011-06-16 14:03:20: Listener for "api.bitcoin.cz": 16/06/2011 14:03:20, Problems communicating with bitcoin RPC

why is that so? I suggest that is the reason why I not getting so much earnings like normal? The Problem startet after the Ddos attack a few days ago...

I hope you can help me and excuse if this is wrong section for my Problem...

[1715156643]

1715156643

[1715156643]

1715156643

[1715156643]

1715156643

[1715156643]

1715156643

[1715156643]

1715156643

[bitminers]

We've had a tonne of connection problems in past hour or 2!!!

[Buzzard]

Bongo,

Have you gone to the Slush's site and registered your IP address?
The server (last I heard) is set to reject any connection attempt from any IP that isn't whitelisted.

And yes, Slush's pool is running just fine for me.

[Bongo098]

Is it only a "Pool" problem or a problem from the whole network? Because with other pools there are no errors or not so much... or is it possible that i made something wrong?

@Buzzard Yes my ip is white listed...

[Wuked]

You should have a backup pool ready to use if you can't connect to one.

Did you say you can connect to all other pools or not ? "not so much" doesn't really explain ?

Are you behind a firewall? Are ports closed ?

[Bongo098]

deepbit for example is without problems... or this one: btc.x8s.de

But my favorite is slushs pool and i think connection etc are working but i get these errors...

[Buzzard]

Ugh..  And just to rule things out...  
You've registered that miner unit with the site (Bongo.Miner1, pw)
You've checked to make sure that the miner name and pw are correctly copied into GUIMiner

The only other thing I can think of is troubles with the internet between you and the server (it only takes 1 node to fail)
Using a command line box (get a DOS prompt) and do:
TRACERT api.bitcoin.cz

Watch the numbers at each jump.  If something times out, or has really high numbers, there may be a problem at that location.  

[Bongo098]

Yes i have done it like you said...

when i run tracert every station have under 50ms reaction time and no time outs... i have run deepbit now over 1 Hour and no problems. Slushs Pool says: 2011-06-16 15:49:04: Listener for "api.bitcoin.cz": 16/06/2011 15:49:04, Problems communicating with bitcoin RPC
its not that slushs pool is not working it works not 100% good and give errors back...

so i suggest the mistake have to be by slush...