API tools faq
paste
Guest User

Untitled

a guest
Dec 4th, 2017
473
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.60 KB | None | 0 0
raw download clone embed print report
  1. 2017-12-02 05:15:59 Bitcoin version v0.15.1
  2. 2017-12-02 05:15:59 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
  3. 2017-12-02 05:15:59 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
  4. 2017-12-02 05:15:59 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
  5. 2017-12-02 05:15:59 Using the 'standard' SHA256 implementation
  6. 2017-12-02 05:15:59 Using RdRand as an additional entropy source
  7. 2017-12-02 05:15:59 Default data directory /home/ancientevil/.bitcoin
  8. 2017-12-02 05:15:59 Using data directory
  9. 2017-12-02 05:15:59 Using config file bitcoin.conf
  10. 2017-12-02 05:15:59 Using at most 125 automatic connections (1024 file descriptors available)
  11. 2017-12-02 05:15:59 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
  12. 2017-12-02 05:15:59 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
  13. 2017-12-02 05:15:59 Using 4 threads for script verification
  14. 2017-12-02 05:15:59 scheduler thread start
  15. 2017-12-02 05:15:59 HTTP: creating work queue of depth 16
  16. 2017-12-02 05:15:59 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
  17. 2017-12-02 05:15:59 HTTP: starting 4 worker threads
  18. 2017-12-02 05:15:59 init message: Verifying wallet(s)...
  19. 2017-12-02 05:15:59 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
  20. 2017-12-02 05:15:59 Using wallet wallet.dat
  21. 2017-12-02 05:15:59 CDBEnv::Open: LogDir=database ErrorFile=db.log
  22. 2017-12-02 05:15:59 Cache configuration:
  23. 2017-12-02 05:15:59 * Using 56.2MiB for block index database
  24. 2017-12-02 05:15:59 * Using 8.0MiB for chain state database
  25. 2017-12-02 05:15:59 * Using 385.8MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
  26. 2017-12-02 05:15:59 init message: Loading block index...
  27. 2017-12-02 05:15:59 Opening LevelDB in blocks/index
  28. 2017-12-02 05:15:59 Opened LevelDB successfully
  29. 2017-12-02 05:15:59 Using obfuscation key for blocks/index: 0000000000000000
  30. 2017-12-02 05:15:59 LoadBlockIndexDB: last block file = 0
  31. 2017-12-02 05:15:59 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
  32. 2017-12-02 05:15:59 Checking all blk files are present...
  33. 2017-12-02 05:15:59 LoadBlockIndexDB: transaction index enabled
  34. 2017-12-02 05:15:59 Initializing databases...
  35. 2017-12-02 05:15:59 Opening LevelDB in chainstate
  36. 2017-12-02 05:15:59 Opened LevelDB successfully
  37. 2017-12-02 05:15:59 Using obfuscation key for chainstate: fa63baf2491fc7eb
  38. 2017-12-02 05:15:59 init message: Rewinding blocks...
  39. 2017-12-02 05:15:59 block index 22ms
  40. 2017-12-02 05:15:59 init message: Loading wallet...
  41. 2017-12-02 05:15:59 nFileVersion = 150100
  42. 2017-12-02 05:15:59 Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total
  43. 2017-12-02 05:15:59 wallet 64ms
  44. 2017-12-02 05:15:59 setKeyPool.size() = 2000
  45. 2017-12-02 05:15:59 mapWallet.size() = 0
  46. 2017-12-02 05:15:59 mapAddressBook.size() = 1
  47. 2017-12-02 05:15:59
  48.  
  49. ************************
  50. EXCEPTION: N5boost10filesystem16filesystem_errorE
  51. boost::filesystem::space: Operation not permitted
  52. bitcoin in AppInit()
  53.  
  54. 2017-12-02 05:15:59 scheduler thread interrupt
  55. 2017-12-02 05:15:59 Shutdown: In progress...
  56. 2017-12-02 05:15:59 *** System error while flushing: boost::filesystem::space: Operation not permitted
  57. 2017-12-02 05:15:59 Error: Error: A fatal internal error occurred, see debug.log for details
  58. 2017-12-02 05:15:59 *** System error while flushing: boost::filesystem::space: Operation not permitted
  59. 2017-12-02 05:15:59 Error: Error: A fatal internal error occurred, see debug.log for details
  60. 2017-12-02 05:15:59 Shutdown: done
  61.  
  62. ##
  63. ## bitcoin.conf configuration file. Lines beginning with # are comments.
  64. ##
  65.  
  66.  
  67.  
  68.  
  69. datadir=/media/ancientevil/Storage/BitcoinBlocks
  70. txindex=1
  71.  
  72.  
  73. # Network-related settings:
  74.  
  75. # Run on the test network instead of the real bitcoin network.
  76. #testnet=0
  77.  
  78. # Run a regression test network
  79. #regtest=0
  80.  
  81. # Connect via a SOCKS5 proxy
  82. #proxy=127.0.0.1:9050
  83.  
  84. # Bind to given address and always listen on it. Use [host]:port notation for IPv6
  85. #bind=<addr>
  86.  
  87. # Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
  88. #whitebind=<addr>
  89.  
  90. ##############################################################
  91. ## Quick Primer on addnode vs connect ##
  92. ## Let's say for instance you use addnode=4.2.2.4 ##
  93. ## addnode will connect you to and tell you about the ##
  94. ## nodes connected to 4.2.2.4. In addition it will tell ##
  95. ## the other nodes connected to it that you exist so ##
  96. ## they can connect to you. ##
  97. ## connect will not do the above when you 'connect' to it. ##
  98. ## It will *only* connect you to 4.2.2.4 and no one else.##
  99. ## ##
  100. ## So if you're behind a firewall, or have other problems ##
  101. ## finding nodes, add some using 'addnode'. ##
  102. ## ##
  103. ## If you want to stay private, use 'connect' to only ##
  104. ## connect to "trusted" nodes. ##
  105. ## ##
  106. ## If you run multiple nodes on a LAN, there's no need for ##
  107. ## all of them to open lots of connections. Instead ##
  108. ## 'connect' them all to one node that is port forwarded ##
  109. ## and has lots of connections. ##
  110. ## Thanks goes to [Noodle] on Freenode. ##
  111. ##############################################################
  112.  
  113. # Use as many addnode= settings as you like to connect to specific peers
  114. #addnode=69.164.218.197
  115. #addnode=10.0.0.2:8333
  116.  
  117. # Alternatively use as many connect= settings as you like to connect ONLY to specific peers
  118. #connect=69.164.218.197
  119. #connect=10.0.0.1:8333
  120.  
  121. # Listening mode, enabled by default except when 'connect' is being used
  122. #listen=1
  123.  
  124. # Maximum number of inbound+outbound connections.
  125. #maxconnections=
  126.  
  127. #
  128. # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  129. #
  130.  
  131. # server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
  132. server=1
  133.  
  134. # Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
  135. # This option can be specified multiple times (default: bind to all interfaces)
  136. #rpcbind=<addr>
  137.  
  138. # If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
  139. # is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
  140. # when the server and client are run as the same user.
  141. #
  142. # If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
  143. # method(DEPRECATED) is to set this pair for the server and client:
  144. rpcuser=rpcUser
  145. rpcpassword=WITHHELD
  146.  
  147. #
  148. # The second method `rpcauth` can be added to server startup argument. It is set at intialization time
  149. # using the output from the script in share/rpcuser/rpcuser.py after providing a username:
  150. #
  151. # ./share/rpcuser/rpcuser.py alice
  152. # String to be appended to bitcoin.conf:
  153. # rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
  154. # Your password:
  155. # DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
  156. #
  157. # On client-side, you add the normal user/password pair to send commands:
  158. #rpcuser=alice
  159. #rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
  160. #
  161. # You can even add multiple entries of these to the server conf file, and client can use any of them:
  162. # rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99
  163.  
  164. # How many seconds bitcoin will wait for a complete RPC HTTP request.
  165. # after the HTTP connection is established.
  166. rpcclienttimeout=6
  167.  
  168. # By default, only RPC connections from localhost are allowed.
  169. # Specify as many rpcallowip= settings as you like to allow connections from other hosts,
  170. # either as a single IPv4/IPv6 or with a subnet specification.
  171.  
  172. # NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
  173. # because the rpcpassword is transmitted over the network unencrypted.
  174.  
  175. # server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
  176. # it is also read by bitcoind to determine if RPC should be enabled
  177. #rpcallowip=10.1.1.34/255.255.255.0
  178. #rpcallowip=1.2.3.4/24
  179. #rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96
  180.  
  181. # Listen for RPC connections on this TCP port:
  182. rpcport=8332
  183.  
  184. # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
  185. # running on another host using this option:
  186. rpcconnect=127.0.0.1
  187.  
  188. # Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
  189. # This setting is over-ridden by the -paytxfee option.
  190. #txconfirmtarget=n
  191.  
  192. # Miscellaneous options
  193.  
  194. # Pre-generate this many public/private key pairs, so wallet backups will be valid for
  195. # both prior transactions and several dozen future transactions.
  196. #keypool=100
  197.  
  198. # Pay an optional transaction fee every time you send bitcoins. Transactions with fees
  199. # are more likely than free transactions to be included in generated blocks, so may
  200. # be validated sooner.
  201. #paytxfee=0.00
  202.  
  203. # Enable pruning to reduce storage requirements by deleting old blocks.
  204. # This mode is incompatible with -txindex and -rescan.
  205. # 0 = default (no pruning).
  206. # 1 = allows manual pruning via RPC.
  207. # >=550 = target to stay under in MiB.
  208. #prune=550
  209.  
  210. # User interface options
  211.  
  212. # Start Bitcoin minimized
  213. #min=1
  214.  
  215. # Minimize to the system tray
  216. #minimizetotray=1
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!