API tools faq
paste
Advertisement
Guest User

Debug Test

a guest
May 21st, 2019
266
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.28 KB | None | 0 0
raw download clone embed print report
  1. ***************************************************************
  2. * RASPIBLITZ DEBUG LOGS
  3. ***************************************************************
  4. blitzversion: 1.2
  5. chainnetwork: bitcoin / main
  6. 15:07:54 up 12:38, 2 users, load average: 1.10, 1.15, 1.09
  7.  
  8. *** BCLOCKHAIN SYSTEMD STATUS ***
  9. â bitcoind.service - Bitcoin daemon
  10. Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
  11. Active: active (running) since Tue 2019-05-21 02:31:35 BST; 12h ago
  12. Process: 2047 ExecStart=/usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid (code=exited, status=0/SUCCESS)
  13. Process: 2041 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/SUCCESS)
  14. Main PID: 2106 (bitcoind)
  15. CGroup: /system.slice/bitcoind.service
  16. ââ2106 /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid
  17.  
  18. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
  19.  
  20. *** LAST BCLOCKHAIN ERROR LOGS ***
  21. sudo journalctl -u bitcoind -b --no-pager -n8
  22. -- No entries --
  23.  
  24. *** LAST BCLOCKHAIN 20 INFO LOGS ***
  25. sudo tail -n 20 /mnt/hdd/bitcoin/debug.log
  26. 2019-05-21T13:18:44Z ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: 000000fc8edcaed1073cb52440514a4c5fdec31ec4244a29a8b215467eac6345, high-hash, proof of work failed (code 16)
  27. 2019-05-21T13:18:59Z socket recv error Connection reset by peer (104)
  28. 2019-05-21T13:19:38Z socket recv error Connection reset by peer (104)
  29. 2019-05-21T13:19:41Z socket recv error Connection reset by peer (104)
  30. 2019-05-21T13:23:40Z socket recv error Connection reset by peer (104)
  31. 2019-05-21T13:33:13Z socket send error Broken pipe (32)
  32. 2019-05-21T13:33:35Z UpdateTip: new best=000000000000000000200eaa5543d1e203a3613708266505ec2375af20086d75 height=577085 version=0x20c00000 log2_work=90.659626 tx=415779612 date='2019-05-21T13:33:07Z' progress=1.000000 cache=62.3MiB(549977txo) warning='34 of last 100 blocks have unexpected version'
  33. 2019-05-21T13:36:58Z socket recv error Connection timed out (110)
  34. 2019-05-21T13:38:09Z UpdateTip: new best=00000000000000000019cd678954ded131bd44d559dc6116da2bff1316320fdf height=577086 version=0x20400000 log2_work=90.659647 tx=415781531 date='2019-05-21T13:37:41Z' progress=1.000000 cache=62.6MiB(552994txo) warning='35 of last 100 blocks have unexpected version'
  35. 2019-05-21T13:38:10Z socket recv error Connection reset by peer (104)
  36. 2019-05-21T13:44:44Z socket recv error Connection reset by peer (104)
  37. 2019-05-21T13:46:13Z Pre-allocating up to position 0x800000 in rev01647.dat
  38. 2019-05-21T13:46:13Z UpdateTip: new best=000000000000000000197e51ec3f1a97489a100d4f9186ec4bf751bf33595dc0 height=577087 version=0x20000000 log2_work=90.659669 tx=415784168 date='2019-05-21T13:45:58Z' progress=1.000000 cache=63.1MiB(557772txo) warning='34 of last 100 blocks have unexpected version'
  39. 2019-05-21T13:48:38Z socket recv error Connection reset by peer (104)
  40. 2019-05-21T13:50:51Z socket recv error Connection reset by peer (104)
  41. 2019-05-21T13:54:51Z socket recv error Connection reset by peer (104)
  42. 2019-05-21T13:55:43Z socket recv error Connection reset by peer (104)
  43. 2019-05-21T13:57:50Z UpdateTip: new best=0000000000000000000fe970113a9ff04627ce95d3a5e500d362fcb2f14e3afb height=577088 version=0x20400000 log2_work=90.65969 tx=415787375 date='2019-05-21T13:57:38Z' progress=1.000000 cache=63.8MiB(564256txo) warning='35 of last 100 blocks have unexpected version'
  44. 2019-05-21T14:01:30Z socket recv error Connection reset by peer (104)
  45. 2019-05-21T14:02:11Z UpdateTip: new best=0000000000000000000777f861570664a3e8111f7179b532ebc443efc3d6baab height=577089 version=0x20000000 log2_work=90.659711 tx=415789330 date='2019-05-21T14:01:49Z' progress=1.000000 cache=64.0MiB(565764txo) warning='35 of last 100 blocks have unexpected version'
  46.  
  47. *** LND SYSTEMD STATUS ***
  48. â lnd.service - LND Lightning Daemon
  49. Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
  50. Active: activating (auto-restart) (Result: exit-code) since Tue 2019-05-21 15:07:09 BST; 44s ago
  51. Process: 19705 ExecStart=/usr/local/bin/lnd --externalip=${publicIP}:${lndPort} (code=exited, status=1/FAILURE)
  52. Process: 19701 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log lightning STARTED (code=exited, status=0/SUCCESS)
  53. Main PID: 19705 (code=exited, status=1/FAILURE)
  54.  
  55. May 21 15:07:09 Zand systemd[1]: lnd.service: Unit entered failed state.
  56. May 21 15:07:09 Zand systemd[1]: lnd.service: Failed with result 'exit-code'.
  57.  
  58. *** LAST LND ERROR LOGS ***
  59. sudo journalctl -u lnd -b --no-pager -n12
  60. -- Logs begin at Tue 2019-05-21 11:42:12 BST, end at Tue 2019-05-21 15:07:54 BST. --
  61. May 21 15:05:35 Zand lnd[17995]: edge not found
  62. May 21 15:05:35 Zand systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
  63. May 21 15:05:35 Zand systemd[1]: lnd.service: Unit entered failed state.
  64. May 21 15:05:35 Zand systemd[1]: lnd.service: Failed with result 'exit-code'.
  65. May 21 15:06:35 Zand systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
  66. May 21 15:06:35 Zand systemd[1]: Stopped LND Lightning Daemon.
  67. May 21 15:06:35 Zand systemd[1]: Starting LND Lightning Daemon...
  68. May 21 15:06:36 Zand systemd[1]: Started LND Lightning Daemon.
  69. May 21 15:07:09 Zand lnd[19705]: edge not found
  70. May 21 15:07:09 Zand systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
  71. May 21 15:07:09 Zand systemd[1]: lnd.service: Unit entered failed state.
  72. May 21 15:07:09 Zand systemd[1]: lnd.service: Failed with result 'exit-code'.
  73. 1558444787 ERROR: LND RPC is not responding. LND may have problems starting up. Check logs, config files and systemd service. Org-Error: [lncli] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:10009: connect: connection refused"
  74.  
  75. *** LAST 30 LND INFO LOGS ***
  76. sudo tail -n 30 /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log
  77. 2019-05-21 15:07:03.097 [INF] CNCT: ChannelArbitrator(f7c4a65fe42190498baadb20ce9a2eb204abcfc610c16f9450e7d6409c957620:0): starting state=StateDefault
  78. 2019-05-21 15:07:03.544 [INF] CNCT: ChannelArbitrator(9c201a2118bfc87afbac59b289c7ebe40e3a6cd1708504c3f0f6e6a8f698ed7b:0): starting state=StateDefault
  79. 2019-05-21 15:07:03.550 [INF] CNCT: ChannelArbitrator(eecc926e409dd57800b203b8b3d3c3cf2b66f437069082c3c51366ae76f9a6b1:0): starting state=StateDefault
  80. 2019-05-21 15:07:04.094 [INF] CNCT: ChannelArbitrator(7bc0acd71af7e3bd8a5532c1558ce11516a0ee3c15fbc89876c6ff882d67c77b:0): starting state=StateDefault
  81. 2019-05-21 15:07:04.111 [INF] CNCT: ChannelArbitrator(52b529c66019afcc29768ee74bcda7140b3dc62ee26c2217484f234ae05247ee:0): starting state=StateDefault
  82. 2019-05-21 15:07:04.638 [INF] CNCT: ChannelArbitrator(29c603b1b182b00d51818a873ed90f70cdbfc41aef0dcc1c470ecd4f51e8cef9:1): starting state=StateDefault
  83. 2019-05-21 15:07:04.644 [INF] CNCT: ChannelArbitrator(d95c3d7f8e3a6b7d4bcad9fc77b7fe83176186309a85e0e5e84506eace2c1bda:0): starting state=StateDefault
  84. 2019-05-21 15:07:05.062 [INF] CNCT: ChannelArbitrator(b248ed3343337bcea39f81fcfb69ee7a6b3b12629d04456fd284d5acf5d8a5ba:1): starting state=StateDefault
  85. 2019-05-21 15:07:05.069 [INF] CNCT: ChannelArbitrator(665a171609edd5dc772705a3ee12bfcb16bd27780b56b4c38c1dcfe3d5ed7e01:0): starting state=StateDefault
  86. 2019-05-21 15:07:05.454 [INF] CNCT: ChannelArbitrator(f8a66ba12f4eda60b669f5ec947310de5028de21517a6a0c5954b2cd4d10425e:0): starting state=StateDefault
  87. 2019-05-21 15:07:05.460 [INF] CNCT: ChannelArbitrator(a359190f54d33c29a3b27ef26d6181620dec55ab188795a64a4b52572570b5fc:1): starting state=StateDefault
  88. 2019-05-21 15:07:05.833 [INF] CNCT: ChannelArbitrator(789dd1f553ce1caa22acc5f37eb48fd7d298e511d4e55edc33d6703a3ee01b74:1): starting state=StateDefault
  89. 2019-05-21 15:07:05.906 [INF] CNCT: ChannelArbitrator(5ded6a4ef071fffb8e23b9ca779229b209ef0b39e97e75422e858c14eeaf4653:1): starting state=StateDefault
  90. 2019-05-21 15:07:06.308 [INF] CNCT: ChannelArbitrator(1af5f726e8630361fc625486d1d721e84d2930d76c9cf8f6f3a8028b7b848f8f:1): starting state=StateDefault
  91. 2019-05-21 15:07:06.320 [INF] CNCT: ChannelArbitrator(59181c21c3a989056b9fad7506976e00a5655069674163b1f273fbd109bd937c:0): starting state=StateDefault
  92. 2019-05-21 15:07:06.764 [INF] CNCT: ChannelArbitrator(db713c270520b71a5ee629a6e07d207c502d7b0d12a4e62ec9a5d5cb429774e3:0): starting state=StateCommitmentBroadcasted
  93. 2019-05-21 15:07:06.771 [INF] CNCT: ChannelArbitrator(db713c270520b71a5ee629a6e07d207c502d7b0d12a4e62ec9a5d5cb429774e3:0): noop trigger chainTrigger
  94. 2019-05-21 15:07:06.786 [INF] CNCT: ChannelArbitrator(7718497fbd67cbca65b4659f79a6b2da406177980d6965de43cb7d9171ad880c:1): starting state=StateDefault
  95. 2019-05-21 15:07:07.322 [INF] DISC: Authenticated Gossiper is starting
  96. 2019-05-21 15:07:07.322 [INF] BRAR: Starting contract observer, watching for breaches.
  97. 2019-05-21 15:07:07.322 [INF] NTFN: New block epoch subscription
  98. 2019-05-21 15:07:07.704 [INF] CRTR: FilteredChainView starting
  99. 2019-05-21 15:07:09.622 [ERR] SRVR: unable to start server: edge not found
  100.  
  101. 2019-05-21 15:07:09.622 [INF] RPCS: Stopping RPC Server
  102. 2019-05-21 15:07:09.622 [INF] RPCS: Stopping WalletKitRPC Sub-RPC Server
  103. 2019-05-21 15:07:09.622 [INF] RPCS: Stopping SignRPC Sub-RPC Server
  104. 2019-05-21 15:07:09.622 [INF] RPCS: Stopping ChainRPC Sub-RPC Server
  105. 2019-05-21 15:07:09.623 [INF] RPCS: Stopping InvoicesRPC Sub-RPC Server
  106. 2019-05-21 15:07:09.744 [INF] LTND: Shutdown complete
  107. *** LAST 20 RTL LOGS ***
  108. -- No entries --
  109.  
  110. *** HARDWARE TEST RESULTS ***
  111. UndervoltageReports in Logs: 0
  112. powerFAIL=1
  113. powerWARN=15
  114. powerMIN='1200000 microVolt'
  115. tempFAIL=3
  116. tempWARN=13
  117. tempMAX='7200 centiGrad'
  118. IMPORTANT: There are some hardware issues with your setup.
  119. 'Run Hardwaretest' in main menu or: sudo /home/admin/05hardwareTest.sh
  120.  
  121. *** SYSTEM STATUS (can take some seconds to gather) ***
  122. localIP='192.168.1.41'
  123. tempCelsius='66.0'
  124. uptime=45492
  125. startcountBlockchain=1
  126. bitcoinActive=1
  127. blockchainHeight=
  128. initialSync=0
  129. syncProgress=0.00
  130. startcountLightning=455
  131. lndActive=0
  132. scriptRuntime=1
  133.  
  134. *** OPTION: SHARE THIS DEBUG OUTPUT ***
  135. An easy way to share this debug output on GitHub or on a support chat
  136. use the following command and share the resulting link:
  137. /home/admin/XXdebugLogs.sh | nc termbin.com 9999
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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!