home | log | search | bash | stats | wiki


Matches for danielpbarron, 10234 total results Sorted by newest | relevance

Sun Feb 21 03:19:29 UTC 2016  <BingoBoingo>   danielpbarron: This problem happened with quantrill this week. Was unresponsive so I ordered a reboot, after reboot... holy fucksticks the disappoint.

Sun Feb 21 03:17:50 UTC 2016  <BingoBoingo>   <danielpbarron> oh also, in getinfo I get this >> "errors" : "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." << The hard shutdown may have left your blockchain copy corrupted at the end. Gotta get a UPS.

Sun Feb 21 02:44:33 UTC 2016  <danielpbarron>   oh also, in getinfo I get this >> "errors" : "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

Sun Feb 21 02:40:10 UTC 2016  <danielpbarron>   gonna try a few more times to get it to continue building on the blocks i already had, and failing that I'll try it with an empty .bitcoin directory

Sun Feb 21 02:37:32 UTC 2016  <danielpbarron>   but that's not necessarily the fault of your thing; i had a power outage take this machine down without properly shutting down

Sun Feb 21 02:37:08 UTC 2016  <danielpbarron>   can't get a new block, just bastards and transactions that appear to be invalid

Sun Feb 21 02:36:18 UTC 2016  <danielpbarron>   well i got a bitcoind out of it, and when i run it against my already mostly complete .bitcoin directory i got black holed; trying again now with -connect=173.73.235.152

Sun Feb 21 02:34:57 UTC 2016  <danielpbarron>   yeah same error

Sun Feb 21 02:34:12 UTC 2016  <mod6>   danielpbarron: try `gpg --recv-key0xAB07D806D2CE741FB886EE50B025BA8B59C36319`

Sun Feb 21 02:34:05 UTC 2016  <danielpbarron>   regardless, the script ended with a bitcoind in rotor/TEST2/bitcoin/src/

Sun Feb 21 02:33:42 UTC 2016  <danielpbarron>   i get the same error when i do the same thing with the long key id you just showed

Sun Feb 21 02:32:43 UTC 2016  <danielpbarron>   when i try to get it, it gives the error linked above

Sun Feb 21 02:31:54 UTC 2016  <mod6>   danielpbarron: did you put this key 0xAB07D806D2CE741FB886EE50B025BA8B59C36319 in your gpg keyring?

Sun Feb 21 02:30:15 UTC 2016  <danielpbarron>   http://log.bitcoin-assets.com/?date=20-02-2016#1410987 << me too. and i get a weird error when trying to get his key >> http://danielpbarron.com/59C36319.txt

Sat Feb 20 03:53:49 UTC 2016  <danielpbarron>   !up dbclk

Sat Feb 20 03:50:08 UTC 2016  <danielpbarron>   !up dbclk

Sat Feb 20 03:11:36 UTC 2016  <mircea_popescu>   danielpbarron> is it a gamble? what was risked? << bb is just butthurt he didn't buy

Sat Feb 20 01:23:04 UTC 2016  <danielpbarron>   i think the trick with coinbase is a weekly small amount; the guy linked above was talking about several orders pending at once

Sat Feb 20 01:22:23 UTC 2016  <danielpbarron>   anyway thanks for the congrats, it is still a nice outcome

Sat Feb 20 01:21:45 UTC 2016  <danielpbarron>   i mean i wasn't gonna buy elsewhere, and it wasn't the last of my cash

« Previous Page    Next Page »