Bitcoin Forum
December 09, 2016, 07:34:09 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 »  All
  Print  
Author Topic: Is mining.bitcoin.cz dead?  (Read 14444 times)
cdnbcguy
Full Member
***
Offline Offline

Activity: 128


View Profile WWW
March 25, 2011, 10:05:56 AM
 #1

I've had no response from it for a few days now....

Annona ad! Please keep in mind that there is nothing wrong with Bitcoin itself. All it's scandals are caused by wonky websites and sleazy people exploiting it. The light attracts bugs.

When all this bullshit drys up and blows away, Bitcoin will be stronger than ever.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481312049
Hero Member
*
Offline Offline

Posts: 1481312049

View Profile Personal Message (Offline)

Ignore
1481312049
Reply with quote  #2

1481312049
Report to moderator
ColdHardMetal
Hero Member
*****
Offline Offline

Activity: 701



View Profile
March 25, 2011, 10:10:22 AM
 #2

Works fine for me.

Manjago
Sr. Member
****
Offline Offline

Activity: 294


я не ламер, я java-прогаммер :-)


View Profile WWW
March 25, 2011, 10:35:33 AM
 #3

Works fine for me.

+1
TenthReality
Member
**
Offline Offline

Activity: 76


View Profile
March 25, 2011, 11:14:52 AM
 #4

Have you tried things such as traceroute to attempt to isolate the issue?

Slush is very much up and working.
cdnbcguy
Full Member
***
Offline Offline

Activity: 128


View Profile WWW
March 25, 2011, 11:49:36 PM
 #5

after adding a / to the url I run it now and get

[2011-02-25 19:47:17] 2 miner threads started, using SHA256 'c' algorithm.
[2011-02-25 19:47:31] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:47:31] json_rpc_call failed, retry after 30 seconds
[2011-02-25 19:48:02] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:48:02] json_rpc_call failed, retry after 30 seconds


any ideas?

Annona ad! Please keep in mind that there is nothing wrong with Bitcoin itself. All it's scandals are caused by wonky websites and sleazy people exploiting it. The light attracts bugs.

When all this bullshit drys up and blows away, Bitcoin will be stronger than ever.
lachesis
Full Member
***
Offline Offline

Activity: 210


View Profile
March 26, 2011, 12:06:28 AM
 #6

Permissions problems, most likely.

Bitcoin Calculator | Scallion | GPG Key | WoT Rating | 1QGacAtYA7E8V3BAiM7sgvLg7PZHk5WnYc
CoinMan
Member
**
Offline Offline

Activity: 104



View Profile
March 26, 2011, 04:44:32 AM
 #7

I'm going to take a guess that your options parameter is not correct for the url it should be

--url http://mining.bitcoin.cz:8332

after adding a / to the url I run it now and get

[2011-02-25 19:47:17] 2 miner threads started, using SHA256 'c' algorithm.
[2011-02-25 19:47:31] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:47:31] json_rpc_call failed, retry after 30 seconds
[2011-02-25 19:48:02] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:48:02] json_rpc_call failed, retry after 30 seconds


any ideas?

My Bitcoin Identity
Bitcoin: 183DFFQXR4xCyseBXzmh3XWc22izDWE5Dw
8668
Member
**
Offline Offline

Activity: 102



View Profile WWW
March 27, 2011, 12:56:23 AM
 #8

I'm going to take a guess that your options parameter is not correct for the url it should be

--url http://mining.bitcoin.cz:8332

after adding a / to the url I run it now and get

[2011-02-25 19:47:17] 2 miner threads started, using SHA256 'c' algorithm.
[2011-02-25 19:47:31] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:47:31] json_rpc_call failed, retry after 30 seconds
[2011-02-25 19:48:02] JSON decode failed(1): '[' or '{' expected near '<'
[2011-02-25 19:48:02] json_rpc_call failed, retry after 30 seconds


any ideas?

I'm getting the same message myself

[2011-02-26 20:54:18] HTTP request failed: couldn't connect to host
[2011-02-26 20:54:18] json_rpc_call failed, retry after 30 seconds
[2011-02-26 20:54:19] 1 miner threads started, using SHA256 'c' algorithm.
[2011-02-26 20:54:48] HTTP request failed: couldn't connect to host
[2011-02-26 20:54:48] json_rpc_call failed, retry after 30 seconds

i am using

minerd --url=http://mining.bitcoin.cz:8332 --user=xxxx.xxx --pass=xxxxxxxxxxx

maybe I am missing something as well. Any help would be greatly appreciated

slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
March 27, 2011, 02:18:23 AM
 #9

Quote
[2011-02-25 19:47:31] JSON decode failed(1): '[' or '{' expected near '<'

Is there any possibility to log what the miner receives? Looks like server is sending non-json response, but I don't see why exactly. Log should help...

slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
March 27, 2011, 02:24:56 AM
 #10

[2011-02-26 20:54:18] HTTP request failed: couldn't connect to host
[2011-02-26 20:54:18] json_rpc_call failed, retry after 30 seconds
[2011-02-26 20:54:19] 1 miner threads started, using SHA256 'c' algorithm.
[2011-02-26 20:54:48] HTTP request failed: couldn't connect to host
[2011-02-26 20:54:48] json_rpc_call failed, retry after 30 seconds

I think this is another issue than response parsing. The pool is up and running, so I don't see the reason why you cannot connect, except that there is something wrong on your side (firewall etc).

slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
March 27, 2011, 02:26:30 AM
 #11

I've had no response from it for a few days now....

Please edit the forum topic, pool wasn't dead for longer than 10 minutes since it started on December 2010 Wink.

FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 27, 2011, 04:00:07 AM
 #12

I've had no response from it for a few days now....

Please edit the forum topic, pool wasn't dead for longer than 10 minutes since it started on December 2010 Wink.

It could be your DNS server.  ATT DNS is having issues at the moment.

From a command prompt try

Code:
nslookup mining.bitcoin.cz 4.2.2.2

and see if that resolves to an IP address.  If so, you may want to change your DNS until ATT gets theirs fixed.

8668
Member
**
Offline Offline

Activity: 102



View Profile WWW
March 27, 2011, 04:07:46 PM
 #13

";; connection timed out; no servers could be reached"

I am beginning to think I am having problems outside the miner or pool...

I should note that this is a new machine on a new network. Fresh install of ubuntu 10.10


bobR
Member
**
Offline Offline

Activity: 112


View Profile
March 27, 2011, 06:07:03 PM
 #14

";; connection timed out; no servers could be reached"

I am beginning to think I am having problems outside the miner or pool...

I should note that this is a new machine on a new network. Fresh install of ubuntu 10.10





Check for firewall or dns problems
8668
Member
**
Offline Offline

Activity: 102



View Profile WWW
March 29, 2011, 06:41:55 PM
 #15

";; connection timed out; no servers could be reached"

I am beginning to think I am having problems outside the miner or pool...

I should note that this is a new machine on a new network. Fresh install of ubuntu 10.10





Check for firewall or dns problems


it was firewall/iptables. FIXED. Thanks for the sounding board!!
Veldy
Member
**
Offline Offline

Activity: 98



View Profile
April 17, 2011, 04:54:47 PM
 #16

As of now, it is responding as "502 Bad Gateway" (nginx/0.7.65).  The pool client is also showing bad response from server.  I suspect that I will not be able to get new work from them or at least won't be able to submit finished work.  So, maybe time to setup with an alternative pool as backup (I am tempted to put another (older) video card in my machine for the sole purpose of GPU computing (460GTX overclocked) and use it for another worker anyway, but I am not sure I have enough power and don't want fans screaming louder than they are.  Anyway, since this site is based on scoring which weights your uptime in a round for payout, this type of outage is rather unacceptable (site should be pooled with multiple IP addresses and redundant backbone connections (using a good ISP perhaps) and reliable software that doesn't all go down at once.  I like slush, but this is not good. Huh

If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
luca662
Newbie
*
Offline Offline

Activity: 15


View Profile
April 17, 2011, 05:02:42 PM
 #17

I'm having the same error (502 bad gateway), but I'm still able to mine and my shares are getting accepted.
[Tycho]
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
April 17, 2011, 05:03:02 PM
 #18

As of now, it is responding as "502 Bad Gateway" (nginx/0.7.65).  The pool client is also showing bad response from server.  I suspect that I will not be able to get new work from them or at least won't be able to submit finished work.  So, maybe time to setup with an alternative pool as backup.
Anyway, since this site is based on scoring which weights your uptime in a round for payout, this type of outage is rather unacceptable (site should be pooled with multiple IP addresses and redundant backbone connections (using a good ISP perhaps) and reliable software that doesn't all go down at once.  I like slush, but this is not good. ???
I think that only the site is broken, the pool itself may be still working fine.

There is no need to create a new "alternative" pool because we already have enough different pools.
My pool has servers in different DCs with automatic failover for high availability :)

Welcome to my bitcoin mining pool: https://deepbit.net - Both payment schemes (including PPS), instant payout, no invalid blocks !
ICBIT Trading platform : USD/BTC futures trading, Bitcoin difficulty futures (NEW!). Third year in bitcoin business.
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
April 17, 2011, 05:38:47 PM
 #19

I'm having the same error (502 bad gateway), but I'm still able to mine and my shares are getting accepted.

bitcoind freeze on webserver, it's restarted and running again. Mining was not affected.

Veldy
Member
**
Offline Offline

Activity: 98



View Profile
April 18, 2011, 04:33:03 AM
 #20

I'm having the same error (502 bad gateway), but I'm still able to mine and my shares are getting accepted.

Yes, it appears that the miner was working, but I had no way to tell if it was working on real data or just eating GPU cycles [especially stale data].  Looks like the slush contribution is very small according to bitcoin watch as well.  Slush screwed up it appears.  In any event, I am working another pool until I am convinced that Slush has things under control. 

BTW, the site was back up shortly after I wrote my original messages.  I noticed that 502 errors have been a common theme for that pool over the last couple of months, so I really wonder about the ability of the system Sad  I hope it is just my apprehension and that it will turn out to be fine and stable with significantly better uptime in the future.

If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
Pages: [1] 2 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!