Advertisement
Guest User

Untitled

a guest
Jun 2nd, 2021
78
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.88 KB | None | 0 0
  1. =====================
  2. = Umbrel debug info =
  3. =====================
  4.  
  5. Umbrel version
  6. --------------
  7. 0.3.10
  8.  
  9. Memory usage
  10. ------------
  11. total used free shared buff/cache available
  12. Mem: 3,9G 2,1G 127M 146M 1,7G 1,5G
  13. Swap: 448M 336M 111M
  14.  
  15. total: 52,9%
  16. bitcoin: 15,3%
  17. electrs: 6,1%
  18. lnd: 1,2%
  19. tor: 0,8%
  20. system: %
  21.  
  22. Filesystem information
  23. ----------------------
  24. Filesystem Size Used Avail Use% Mounted on
  25. /dev/sda5 960G 490G 431G 54% /
  26. /dev/sda5 960G 490G 431G 54% /
  27.  
  28. Karen logs
  29. ----------
  30.  
  31. Deriving keys...
  32. cat: /home/sg/db/umbrel-seed/seed: No such file or directory
  33. Missing derivation parameter, this is unsafe, exiting.
  34. Got signal: change-password
  35. karen is getting triggered!
  36. This script must only be run on Umbrel OS
  37. Got signal:
  38. karen is getting triggered!
  39. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  40. Got signal:
  41. karen is getting triggered!
  42. Got signal:
  43. karen is getting triggered!
  44. Got signal: debug
  45. karen is getting triggered!
  46. Got signal: debug
  47. karen is getting triggered!
  48. Got signal: debug
  49. karen is getting triggered!
  50. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  51. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  52. Got signal:
  53. karen is getting triggered!
  54. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  55. Got signal:
  56. karen is getting triggered!
  57. Got signal:
  58. karen is getting triggered!
  59. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  60. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  61. Got signal:
  62. karen is getting triggered!
  63. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  64. Got signal:
  65. karen is getting triggered!
  66. Got signal:
  67. karen is getting triggered!
  68. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  69. ./karen: line 68: /home/sg/events/triggers/: Is a directory
  70. Debug result file generated
  71. Debug result file generated
  72. Debug result file generated
  73. 574624 pts/0 S 0:00 bash ./karen
  74. 574651 pts/0 S 0:00 bash ./karen
  75. karen is already running
  76. Got signal: change-password
  77. karen is getting triggered!
  78. This script must only be run on Umbrel OS
  79. Got signal: debug
  80. karen is getting triggered!
  81.  
  82. Docker containers
  83. -----------------
  84. NAMES STATUS
  85. middleware Up 7 minutes
  86. bitcoin Up 7 minutes
  87. nginx Up 7 minutes
  88. lnd Up 7 minutes
  89. manager Up 7 minutes
  90. electrs Up 7 minutes
  91. dashboard Up 7 minutes
  92. tor Up 7 minutes
  93.  
  94. Bitcoin Core logs
  95. -----------------
  96.  
  97. Attaching to bitcoin
  98. bitcoin | 2021-06-02T17:30:00Z init message: Done loading
  99. bitcoin | 2021-06-02T17:30:00Z msghand thread start
  100. bitcoin | 2021-06-02T17:30:00Z opencon thread start
  101. bitcoin | 2021-06-02T17:30:00Z addcon thread start
  102. bitcoin | 2021-06-02T17:30:00Z net thread start
  103. bitcoin | 2021-06-02T17:30:00Z dnsseed thread start
  104. bitcoin | 2021-06-02T17:30:00Z Waiting 300 seconds before querying DNS seeds.
  105. bitcoin | 2021-06-02T17:30:02Z New outbound peer connected: version: 70015, blocks=685984, peer=0 (block-relay)
  106. bitcoin | 2021-06-02T17:30:05Z New outbound peer connected: version: 70015, blocks=685984, peer=1 (block-relay)
  107. bitcoin | 2021-06-02T17:30:11Z P2P peers available. Skipped DNS seeding.
  108. bitcoin | 2021-06-02T17:30:11Z dnsseed thread exit
  109. bitcoin | 2021-06-02T17:30:18Z New outbound peer connected: version: 70015, blocks=685984, peer=2 (full-relay)
  110. bitcoin | 2021-06-02T17:30:36Z Socks5() connect to 2a01:cb19:849c:6300:e868:ed57:f0e5:3c1:8333 failed: general failure
  111. bitcoin | 2021-06-02T17:30:39Z New outbound peer connected: version: 70016, blocks=685984, peer=3 (full-relay)
  112. bitcoin | 2021-06-02T17:31:00Z Socks5() connect to 83.68.131.39:8333 failed: general failure
  113. bitcoin | 2021-06-02T17:31:02Z New outbound peer connected: version: 70015, blocks=685984, peer=4 (full-relay)
  114. bitcoin | 2021-06-02T17:31:02Z Socks5() connect to 2a00:f440:0:3001::162:8333 failed: general failure
  115. bitcoin | 2021-06-02T17:31:04Z New outbound peer connected: version: 70016, blocks=685984, peer=5 (full-relay)
  116. bitcoin | 2021-06-02T17:31:05Z New outbound peer connected: version: 70015, blocks=685984, peer=6 (full-relay)
  117. bitcoin | 2021-06-02T17:31:06Z New outbound peer connected: version: 70015, blocks=685984, peer=7 (full-relay)
  118. bitcoin | 2021-06-02T17:31:34Z Imported mempool transactions from disk: 7528 succeeded, 1 failed, 0 expired, 48 already there, 0 waiting for initial broadcast
  119. bitcoin | 2021-06-02T17:31:34Z loadblk thread exit
  120. bitcoin | 2021-06-02T17:31:49Z New outbound peer connected: version: 70015, blocks=685984, peer=8 (full-relay)
  121. bitcoin | 2021-06-02T17:31:50Z New outbound peer connected: version: 70015, blocks=685984, peer=9 (full-relay)
  122. bitcoin | 2021-06-02T17:31:51Z New outbound peer connected: version: 70016, blocks=685984, peer=11 (full-relay)
  123. bitcoin | 2021-06-02T17:32:33Z New outbound peer connected: version: 70016, blocks=685984, peer=12 (full-relay)
  124. bitcoin | 2021-06-02T17:32:55Z Socks5() connect to 118.173.163.196:8333 failed: general failure
  125. bitcoin | 2021-06-02T17:33:32Z UpdateTip: new best=00000000000000000007fbcc44b1c4cc68f333a29686de9b9ecb2cbd1957563b height=685985 version=0x20400004 log2_work=92.916918 tx=646520323 date='2021-06-02T17:33:16Z' progress=1.000000 cache=4.7MiB(33982txo)
  126. bitcoin | 2021-06-02T17:33:36Z New outbound peer connected: version: 70016, blocks=685985, peer=13 (full-relay)
  127. bitcoin | 2021-06-02T17:33:57Z New outbound peer connected: version: 70016, blocks=685985, peer=14 (full-relay)
  128.  
  129. LND logs
  130. --------
  131.  
  132. Attaching to lnd
  133. lnd | 2021-06-02 17:28:15.886 [INF] LTND: Version: 0.12.1-beta commit=v0.12.1-beta, build=production, logging=default, debuglevel=info
  134. lnd | 2021-06-02 17:28:15.886 [INF] LTND: Active chain: Bitcoin (network=mainnet)
  135. lnd | 2021-06-02 17:28:15.886 [INF] LTND: Opening the main database, this might take a few minutes...
  136. lnd | 2021-06-02 17:28:15.887 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
  137. lnd | 2021-06-02 17:28:15.939 [INF] CHDB: Checking for schema update: latest_version=20, db_version=20
  138. lnd | 2021-06-02 17:28:15.939 [INF] LTND: Database now open (time_to_open=52.766291ms)!
  139. lnd | 2021-06-02 17:28:16.099 [INF] RPCS: Password RPC server listening on 0.0.0.0:10009
  140. lnd | 2021-06-02 17:28:16.121 [INF] RPCS: Password gRPC proxy started at 0.0.0.0:8080
  141. lnd | 2021-06-02 17:28:16.121 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
  142.  
  143. Tor logs
  144. --------
  145.  
  146. Attaching to tor
  147. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
  148. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
  149. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
  150. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
  151. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
  152. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
  153. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
  154. tor | Jun 02 17:28:08.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
  155. tor | Jun 02 17:28:08.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
  156. tor | Jun 02 17:28:09.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
  157. tor | Jun 02 17:28:09.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6769, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
  158. tor | Jun 02 17:28:10.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
  159. tor | Jun 02 17:28:11.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
  160. tor | Jun 02 17:28:13.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
  161. tor | Jun 02 17:28:14.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
  162. tor | Jun 02 17:28:14.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
  163. tor | Jun 02 17:28:14.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
  164. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
  165. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
  166. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
  167. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
  168. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
  169. tor | Jun 02 17:28:15.000 [notice] Bootstrapped 100% (done): Done
  170. tor | Jun 02 17:28:26.000 [warn] Guard tor1sethsimmonsme ($3CCEF96871A49AC06149E4AA8E14D270D881F6D3) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 1/151. Use counts are 0/0. 1 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  171. tor | Jun 02 17:28:43.000 [notice] Guard tor1sethsimmonsme ($3CCEF96871A49AC06149E4AA8E14D270D881F6D3) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 165/236. Use counts are 106/106. 165 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  172. tor | Jun 02 17:28:44.000 [warn] Guard tor1sethsimmonsme ($3CCEF96871A49AC06149E4AA8E14D270D881F6D3) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 146/295. Use counts are 106/106. 146 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  173. tor | Jun 02 17:28:56.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 388 buildtimes.
  174. tor | Jun 02 17:31:00.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  175. tor | Jun 02 17:32:55.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  176. ================
  177. ==== Result ====
  178. ================
  179. The debug script did not automatically detect any issues with your Umbrel.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement