api2.bitcoin.cz - problem

[ifinta]

Hi,

I am using a Slush's pool.

Currently the pool do not shows my blocks, but my worker do and log they.

I used ping to see the ip of api2.bitcoin.cz:

ifinta@koeppeloeppe:~$ ping api2.bitcoin.cz
PING api2.bitcoin.cz (178.79.185.185) 56(84) bytes of data.
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=1 ttl=54 time=51.6 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=2 ttl=54 time=51.8 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=3 ttl=54 time=52.3 ms
64 bytes from 178.79.185.185: icmp_req=4 ttl=54 time=51.9 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=5 ttl=54 time=53.0 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=6 ttl=54 time=54.6 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=7 ttl=54 time=53.8 ms
64 bytes from li354-185.members.linode.com (178.79.185.185): icmp_req=8 ttl=54 time=52.3 ms
^C
--- api2.bitcoin.cz ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 18721ms
rtt min/avg/max/mdev = 51.630/52.712/54.689/1.034 ms
ifinta@koeppeloeppe:~$ date
2011. júl. 26., kedd, 20.52.01 CEST

I switched my computer off.

Please notify Slush - I am new - so can't post direct in Slush's topic.

Thanks

[jh1523]

I have the same problem, and also can't post to the thread.

http://forum.bitcoin.org/index.php?topic=32126.0

I even switched the url to api.bitcoin.cz and no luck.

It seems that other people have the same problem too. But others don't.

I'll go mine in another pool until this one is fixed.

[ifinta]

I think it is an new attack, and slush give us just a new address: (?)

kdiana@nockstein:~$ ping api3.bitcoin.cz
PING api3.bitcoin.cz (109.74.195.190) 56(84) bytes of data.
64 bytes from kuzlatko.palatinus.cz (109.74.195.190): icmp_req=1 ttl=54 time=53.1 ms
64 bytes from kuzlatko.palatinus.cz (109.74.195.190): icmp_req=2 ttl=54 time=53.5 ms
64 bytes from kuzlatko.palatinus.cz (109.74.195.190): icmp_req=3 ttl=54 time=53.0 ms
64 bytes from kuzlatko.palatinus.cz (109.74.195.190): icmp_req=4 ttl=54 time=52.5 ms
64 bytes from kuzlatko.palatinus.cz (109.74.195.190): icmp_req=5 ttl=54 time=52.0 ms
^C
--- api3.bitcoin.cz ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 52.077/52.882/53.597/0.572 ms

and what my worker see

ifinta@koeppeloeppe:~$ tail -F DiabloMiner/var/log/diabloMiner.log
[2011.07.26. 22:01:39] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:41] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:43] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:43] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:43] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:44] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:44] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:44] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:46] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:48] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:48] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
[2011.07.26. 22:01:48] ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Server temporarily down for maintenance
mhash 1497,0/1580,7 | accept: 0 | reject: 0 | hw error: 0^C

I stopped my worker, and wait for an message from slush...

[ifinta]

I read the message from Slush.
It is no attack, no new address.
Only problem with www.

I see my block's again.