Bitcoin Forum
December 03, 2016, 09:40:58 AM *
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 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51]
  Print  
Author Topic: Algorithmically placed FPGA miner: 255MH/s/chip, supports all known boards  (Read 109469 times)
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
June 21, 2013, 09:23:44 PM
 #1001


I'm surprised it worked at all.  The code you sent me wasn't able to talk to the board.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
1480758058
Hero Member
*
Offline Offline

Posts: 1480758058

View Profile Personal Message (Offline)

Ignore
1480758058
Reply with quote  #2

1480758058
Report to moderator
1480758058
Hero Member
*
Offline Offline

Posts: 1480758058

View Profile Personal Message (Offline)

Ignore
1480758058
Reply with quote  #2

1480758058
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480758058
Hero Member
*
Offline Offline

Posts: 1480758058

View Profile Personal Message (Offline)

Ignore
1480758058
Reply with quote  #2

1480758058
Report to moderator
zulu83465
Newbie
*
Offline Offline

Activity: 14


View Profile
July 31, 2013, 08:11:33 PM
 #1002

what could it be? all servers are unavailable?
an hour ago it worked without problems


unable to connect: java.net.SocketTimeoutException: connect timed out
             exception in work queueing thread: java.net.SocketTimeoutException: connect timed out
             opening signcryption connection to limp.tricone-mining.com/96.8.120.116:7778
               unable to connect: java.net.NoRouteToHostException: No route to host
             exception in work queueing thread: java.net.NoRouteToHostException: No route to host
             opening signcryption connection to limp.tricone-mining.com/109.75.176.36:7778
               unable to connect: java.net.SocketException: Connection reset
             exception in work queueing thread: java.net.SocketException: Connection reset
             opening signcryption connection to limp.tricone-mining.com/23.23.249.133:7778
               unable to connect: java.net.SocketTimeoutException: Read timed out
             exception in work queueing thread: java.net.SocketTimeoutException: Read timed out
             opening signcryption connection to limp.tricone-mining.com/54.248.103.36:7779
               unable to connect: java.net.SocketTimeoutException: Read timed out
             exception in work queueing thread: java.net.SocketTimeoutException: Read timed out
             opening signcryption connection to limp.tricone-mining.com/23.23.249.133:7779
               unable to connect: java.net.SocketTimeoutException: Read timed out
             exception in work queueing thread: java.net.SocketTimeoutException: Read timed out
             opening signcryption connection to limp.tricone-mining.com/54.248.103.36:7779
               unable to connect: java.net.SocketTimeoutException: Read timed out


thanks
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
July 31, 2013, 10:28:26 PM
 #1003

The signcryption network was down today from 31-Jul-2013 11:49 UTC until 22:24:35 UTC.  Service has been restored.

There are two "backend" servers in secure locations which hold copies of the signcryption keys.  The frontend machines load balance signcryption requests between them automatically.

Last night one of the two backend machines had a hardware failure.  Unfortunately unbeknownst to me the other server had not been participating for the last several days due to a software problem (runit got stuck in a peculiar state), but I had not noticed because the first one had been handling the whole load without problems.

I have added to my monitoring software to let me know immediately when either one of the backend servers stops servicing requests rather than waiting until requests stop being serviced completely.  This is a bit tricky since one of the machines is slower (worse network connection) than the other and the clients will always favor whichever one is responding most quickly, so even under normal circumstances the load is very heavily skewed.

I apologize for the inconvenience.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
zulu83465
Newbie
*
Offline Offline

Activity: 14


View Profile
July 31, 2013, 10:34:21 PM
 #1004

ok, thanks for the clarification
I will watch as much as possible
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51]
  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!