Kokojamboo

Troubleshoot

Jan 25th, 2024
116
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 31.89 KB | None | 0 0
  1. Loading data...
  2. ==============
  3. = Debug info =
  4. ==============
  5.  
  6. Node version
  7. ------------
  8. 0.3.1
  9.  
  10. Flashed OS version
  11. -----------------
  12. v0.5.17
  13.  
  14. Raspberry Pi Model
  15. ------------------
  16. Model : Raspberry Pi 4 Model B Rev 1.5
  17.  
  18. Temperature
  19. -----------
  20. temp=47.7'C
  21.  
  22. Throttling
  23. ----------
  24. throttled=0x0
  25.  
  26. Memory usage
  27. ------------
  28. total used free shared buff/cache available
  29. Mem: 7.8G 1.3G 91M 1.0M 6.4G 6.4G
  30. Swap: 4.1G 538M 3.6G
  31.  
  32. Calculating memory usage...
  33. This may take a while, please wait...
  34. bitcoin: 41.97%
  35. total: 16.8%
  36. system: 8.7%
  37. lnd: 3.60%
  38. tor: 0.54%
  39. ride-the-lightning: 0.40%
  40. lightning: %
  41.  
  42. Memory monitor logs
  43. -------------------
  44.  
  45. Filesystem information
  46. ----------------------
  47. Filesystem Size Used Avail Use% Mounted on
  48. /dev/root 119G 8.1G 107G 8% /
  49. /dev/sda1 1.8T 648G 1.1T 38% /home/citadel/citadel
  50.  
  51. Startup service logs
  52. --------------------
  53. Jan 25 16:58:59 citadel start[2532]: Container lnd-service-1 Creating
  54. Jan 25 16:58:59 citadel start[2532]: Container lnd-tor-1 Creating
  55. Jan 25 16:58:59 citadel start[2532]: Container lnd-neutrino-switcher-1 Creating
  56. Jan 25 16:58:59 citadel start[2532]: Container lnd-backup-1 Creating
  57. Jan 25 16:59:00 citadel start[2532]: Container lnd-neutrino-switcher-1 Created
  58. Jan 25 16:59:00 citadel start[2532]: Container lnd-backup-1 Created
  59. Jan 25 16:59:00 citadel start[2532]: Container lnd-main-1 Created
  60. Jan 25 16:59:00 citadel start[2532]: Container lnd-tor-1 Created
  61. Jan 25 16:59:00 citadel start[2532]: Container lnd-service-1 Created
  62. Jan 25 16:59:00 citadel start[2532]: Container lnd-middleware-1 Creating
  63. Jan 25 16:59:00 citadel start[2532]: Container lnd-middleware-1 Created
  64. Jan 25 16:59:00 citadel start[2532]: Container lnd-backup-1 Starting
  65. Jan 25 16:59:00 citadel start[2532]: Container lnd-main-1 Starting
  66. Jan 25 16:59:00 citadel start[2532]: Container lnd-tor-1 Starting
  67. Jan 25 16:59:00 citadel start[2532]: Container lnd-service-1 Starting
  68. Jan 25 16:59:00 citadel start[2532]: Container lnd-neutrino-switcher-1 Starting
  69. Jan 25 16:59:07 citadel start[2532]: Container lnd-main-1 Started
  70. Jan 25 16:59:08 citadel start[2532]: Container lnd-backup-1 Started
  71. Jan 25 16:59:09 citadel start[2532]: Container lnd-tor-1 Started
  72. Jan 25 16:59:09 citadel start[2532]: Container lnd-neutrino-switcher-1 Started
  73. Jan 25 16:59:09 citadel start[2532]: Container lnd-service-1 Started
  74. Jan 25 16:59:09 citadel start[2532]: Container lnd-middleware-1 Starting
  75. Jan 25 16:59:12 citadel start[2532]: Container lnd-middleware-1 Started
  76. Jan 25 16:59:12 citadel start[1020]: Citadel is now accessible at
  77. Jan 25 16:59:12 citadel start[1020]: http://citadel.local
  78. Jan 25 16:59:12 citadel start[1020]: http://192.168.0.38
  79. Jan 25 16:59:12 citadel systemd[1]: Started Citadel Startup Service.
  80. Jan 25 18:32:31 citadel passwd[52384]: pam_unix(passwd:chauthtok): password changed for citadel
  81. Jan 25 19:49:04 citadel passwd[90229]: pam_unix(passwd:chauthtok): password changed for citadel
  82.  
  83. External storage service logs
  84. -----------------------------
  85. Jan 23 14:54:03 citadel systemd[1]: Finished External Storage Mounter.
  86. Jan 25 16:58:01 citadel systemd[1]: Stopping External Storage Mounter...
  87. Jan 25 16:58:01 citadel systemd[1]: citadel-external-storage.service: Succeeded.
  88. Jan 25 16:58:01 citadel systemd[1]: Stopped External Storage Mounter.
  89. Jan 25 16:58:01 citadel systemd[1]: citadel-external-storage.service: Consumed 1h 26min 11.282s CPU time.
  90. -- Boot a9d7ce56c01c4c739660af46aca59ecd --
  91. Jan 25 16:58:05 citadel systemd[1]: Starting External Storage Mounter...
  92. Jan 25 16:58:05 citadel mount[370]: Running external storage mount script...
  93. Jan 25 16:58:06 citadel mount[370]: Found device "Samsung PSSD T7"
  94. Jan 25 16:58:06 citadel mount[370]: Disabling UAS for USB devices...
  95. Jan 25 16:58:06 citadel mount[370]: Rebinding USB drivers...
  96. Jan 25 16:58:07 citadel mount[370]: Checking if the devices can be found again...
  97. Jan 25 16:58:09 citadel mount[370]: Checking if the device is ext4...
  98. Jan 25 16:58:09 citadel mount[370]: Yes, it is ext4
  99. Jan 25 16:58:09 citadel mount[370]: Checking if device contains a Citadel install...
  100. Jan 25 16:58:09 citadel mount[370]: Yes, it contains a Citadel install
  101. Jan 25 16:58:09 citadel mount[370]: Bind mounting external storage over local Citadel installation...
  102. Jan 25 16:58:09 citadel mount[370]: Bind mounting external storage over local Docker data dir...
  103. Jan 25 16:58:09 citadel mount[370]: Bind mounting external storage to /swap
  104. Jan 25 16:58:09 citadel mount[370]: Bind mounting SD card root at /sd-card...
  105. Jan 25 16:58:09 citadel mount[370]: Checking Citadel root is now on external storage...
  106. Jan 25 16:58:10 citadel mount[370]: Checking /var/lib/docker is now on external storage...
  107. Jan 25 16:58:10 citadel mount[370]: Checking /swap is now on external storage...
  108. Jan 25 16:58:10 citadel mount[370]: Setting up swapfile
  109. Jan 25 16:58:12 citadel mount[540]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
  110. Jan 25 16:58:12 citadel mount[540]: no label, UUID=f2b6c412-432b-434e-b1c9-ded660ccd391
  111. Jan 25 16:58:12 citadel mount[370]: Checking SD Card root is bind mounted at /sd-root...
  112. Jan 25 16:58:12 citadel mount[370]: Starting external drive mount monitor...
  113. Jan 25 16:58:12 citadel mount[370]: Mount script completed successfully!
  114. Jan 25 16:58:12 citadel systemd[1]: Finished External Storage Mounter.
  115.  
  116. External storage SD card update service logs
  117. --------------------------------------------
  118. Jan 21 13:33:14 citadel update-from-sdcard[955]: No, SD version is not newer, exiting.
  119. Jan 21 13:33:14 citadel systemd[1]: Finished External Storage SDcard Updater.
  120. Jan 21 18:21:47 citadel systemd[1]: citadel-external-storage-sdcard-update.service: Succeeded.
  121. Jan 21 18:21:47 citadel systemd[1]: Stopped External Storage SDcard Updater.
  122. -- Boot bf7b68e11b1946d080ec92a47bd70bf6 --
  123. Jan 21 18:22:27 citadel systemd[1]: Starting External Storage SDcard Updater...
  124. Jan 21 18:22:27 citadel update-from-sdcard[962]: Checking if SD card Citadel is newer than external storage...
  125. Jan 21 18:22:27 citadel update-from-sdcard[962]: No, SD version is not newer, exiting.
  126. Jan 21 18:22:27 citadel systemd[1]: Finished External Storage SDcard Updater.
  127. Jan 21 19:53:13 citadel systemd[1]: citadel-external-storage-sdcard-update.service: Succeeded.
  128. Jan 21 19:53:13 citadel systemd[1]: Stopped External Storage SDcard Updater.
  129. -- Boot b2e6ad1380b74a1b81d1000383a76b4a --
  130. Jan 21 19:54:08 citadel systemd[1]: Starting External Storage SDcard Updater...
  131. Jan 21 19:54:08 citadel update-from-sdcard[959]: Checking if SD card Citadel is newer than external storage...
  132. Jan 21 19:54:09 citadel update-from-sdcard[959]: No, SD version is not newer, exiting.
  133. Jan 21 19:54:09 citadel systemd[1]: Finished External Storage SDcard Updater.
  134. Jan 23 14:53:53 citadel systemd[1]: citadel-external-storage-sdcard-update.service: Succeeded.
  135. Jan 23 14:53:53 citadel systemd[1]: Stopped External Storage SDcard Updater.
  136. -- Boot d1745748ef76439bb62657bb0dc7f449 --
  137. Jan 23 14:54:31 citadel systemd[1]: Starting External Storage SDcard Updater...
  138. Jan 23 14:54:31 citadel update-from-sdcard[957]: Checking if SD card Citadel is newer than external storage...
  139. Jan 23 14:54:31 citadel update-from-sdcard[957]: No, SD version is not newer, exiting.
  140. Jan 23 14:54:31 citadel systemd[1]: Finished External Storage SDcard Updater.
  141. Jan 25 16:58:01 citadel systemd[1]: citadel-external-storage-sdcard-update.service: Succeeded.
  142. Jan 25 16:58:01 citadel systemd[1]: Stopped External Storage SDcard Updater.
  143. -- Boot a9d7ce56c01c4c739660af46aca59ecd --
  144. Jan 25 16:58:41 citadel systemd[1]: Starting External Storage SDcard Updater...
  145. Jan 25 16:58:41 citadel update-from-sdcard[949]: Checking if SD card Citadel is newer than external storage...
  146. Jan 25 16:58:41 citadel update-from-sdcard[949]: No, SD version is not newer, exiting.
  147. Jan 25 16:58:41 citadel systemd[1]: Finished External Storage SDcard Updater.
  148.  
  149. Karen logs
  150. ----------
  151.  
  152. Container tor Removed
  153. Network citadel_main_network Removing
  154. Network citadel_main_network Removed
  155. 2024-01-25T17:01:16.234532Z ERROR citadel_apps::cli::preprocessing: App samourai-server does not have an app.yml file!
  156. 2024-01-25T17:01:16.259744Z ERROR citadel_apps::cli: Missing app.yml for app samourai-server
  157. 2024-01-25T17:01:16.262933Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  158. 2024-01-25T17:01:16.283588Z WARN citadel_apps::composegenerator::v4::convert: App defines network-mode, but does not request the network permission
  159. 2024-01-25T17:01:16.391627Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  160. 2024-01-25T17:01:16.637905Z ERROR citadel_apps::cli::preprocessing: Error converting app jinja files for /citadel/apps/samourai-server: app.yml not found in /citadel/apps/samourai-server
  161. 2024-01-25T17:01:16.671732Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  162. main Pulling
  163. boltz Pulling
  164. loop Pulling
  165. boltz Pulled
  166. main Pulled
  167. loop Pulled
  168. Container ride-the-lightning-main-1 Creating
  169. Container ride-the-lightning-loop-1 Creating
  170. Container ride-the-lightning-boltz-1 Creating
  171. Container ride-the-lightning-boltz-1 Created
  172. Container ride-the-lightning-loop-1 Created
  173. Container ride-the-lightning-main-1 Created
  174. Container ride-the-lightning-main-1 Starting
  175. Container ride-the-lightning-boltz-1 Starting
  176. Container ride-the-lightning-loop-1 Starting
  177. Container ride-the-lightning-boltz-1 Started
  178. Container ride-the-lightning-loop-1 Started
  179. Container ride-the-lightning-main-1 Started
  180. 2024-01-25T17:01:30.376284Z ERROR citadel_apps::cli::preprocessing: App samourai-server does not have an app.yml file!
  181. 2024-01-25T17:01:30.422840Z ERROR citadel_apps::cli: Missing app.yml for app samourai-server
  182. 2024-01-25T17:01:30.429111Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  183. 2024-01-25T17:01:30.482388Z WARN citadel_apps::composegenerator::v4::convert: App defines network-mode, but does not request the network permission
  184. 2024-01-25T17:01:30.639476Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  185. 2024-01-25T17:01:30.919748Z ERROR citadel_apps::cli::preprocessing: Error converting app jinja files for /citadel/apps/samourai-server: app.yml not found in /citadel/apps/samourai-server
  186. 2024-01-25T17:01:30.934793Z WARN citadel_apps::composegenerator::v4::utils: "web" as service name is deprecated and will be removed in Nirvati.
  187. Error response from daemon: No such container: lightning
  188. tail: cannot open '/home/citadel/citadel/scripts/../logs/memory-monitor.log' for reading: No such file or directory
  189. time="2024-01-25T17:30:22Z" level=warning msg="The \"APP_ELECTRUM_IP\" variable is not set. Defaulting to a blank string."
  190. time="2024-01-25T17:30:22Z" level=warning msg="The \"TOR_ARTI_PROXY_IP6\" variable is not set. Defaulting to a blank string."
  191. time="2024-01-25T17:30:23Z" level=warning msg="The \"APP_ELECTRUM_IP\" variable is not set. Defaulting to a blank string."
  192. time="2024-01-25T17:30:23Z" level=warning msg="The \"TOR_ARTI_PROXY_IP6\" variable is not set. Defaulting to a blank string."
  193. time="2024-01-25T17:30:23Z" level=warning msg="The \"APP_ELECTRUM_IP\" variable is not set. Defaulting to a blank string."
  194. time="2024-01-25T17:30:23Z" level=warning msg="The \"TOR_ARTI_PROXY_IP6\" variable is not set. Defaulting to a blank string."
  195. time="2024-01-25T17:30:23Z" level=warning msg="The \"APP_ELECTRUM_IP\" variable is not set. Defaulting to a blank string."
  196. time="2024-01-25T17:30:23Z" level=warning msg="The \"TOR_ARTI_PROXY_IP6\" variable is not set. Defaulting to a blank string."
  197. no such service: api
  198. New password: Retype new password: passwd: password updated successfully
  199. New password: Retype new password: passwd: password updated successfully
  200. Error response from daemon: No such container: lightning
  201. tail: cannot open '/home/citadel/citadel/scripts/../logs/memory-monitor.log' for reading: No such file or directory
  202.  
  203. Docker containers
  204. -----------------
  205. NAMES STATUS
  206. ride-the-lightning-boltz-1 Up 3 hours
  207. ride-the-lightning-main-1 Up 3 hours
  208. lnd-middleware-1 Up 3 hours
  209. lnd-backup-1 Up 3 hours
  210. lnd-main-1 Up 3 hours
  211. lnd-service-1 Up 3 hours
  212. lnd-tor-1 Up 3 hours
  213. manager Up 3 hours
  214. bitcoin Up 3 hours
  215. dashboard Up 3 hours
  216. app-tor Up 3 hours
  217. caddy Up 3 hours
  218. arti Up 3 hours
  219. i2p Up 3 hours
  220. tor Up 3 hours
  221.  
  222. Bitcoin Core logs
  223. -----------------
  224.  
  225. bitcoin | 2024-01-25T18:57:53Z New outbound peer connected: version: 70016, blocks=827355, peer=171 (block-relay-only)
  226. bitcoin | 2024-01-25T18:58:28Z Socks5() connect to 135.181.69.25:8333 failed: general failure
  227. bitcoin | 2024-01-25T19:09:40Z New outbound peer connected: version: 70016, blocks=827355, peer=189 (block-relay-only)
  228. bitcoin | 2024-01-25T19:12:20Z Socks5() connect to 193.150.69.254:8333 failed: general failure
  229. bitcoin | 2024-01-25T19:15:03Z Socks5() connect to 24.17.214.2:8333 failed: general failure
  230. bitcoin | 2024-01-25T19:22:31Z New outbound peer connected: version: 70016, blocks=827355, peer=200 (block-relay-only)
  231. bitcoin | 2024-01-25T19:23:33Z Socks5() connect to 2a01:4f9:3b:3b51::2:8333 failed: general failure
  232. bitcoin | 2024-01-25T19:27:38Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1885 seconds ago)
  233. bitcoin | 2024-01-25T19:27:47Z New outbound peer connected: version: 70016, blocks=827355, peer=207 (outbound-full-relay)
  234. bitcoin | 2024-01-25T19:30:43Z Saw new header hash=00000000000000000001825757e588e981da31e04ff746c14ae7861040bd5726 height=827356
  235. bitcoin | 2024-01-25T19:30:43Z [net] Saw new cmpctblock header hash=00000000000000000001825757e588e981da31e04ff746c14ae7861040bd5726 peer=126
  236. bitcoin | 2024-01-25T19:30:43Z UpdateTip: new best=00000000000000000001825757e588e981da31e04ff746c14ae7861040bd5726 height=827356 version=0x20000000 log2_work=94.688430 tx=957289914 date='2024-01-25T19:30:07Z' progress=1.000000 cache=28.5MiB(136738txo)
  237. bitcoin | 2024-01-25T19:30:46Z Socks5() connect to 157.230.233.211:0 failed: general failure
  238. bitcoin | 2024-01-25T19:35:17Z Socks5() connect to 2001:19f0:7400:26cb:5400:4ff:fe91:ca66:8333 failed: general failure
  239. bitcoin | 2024-01-25T19:35:42Z New outbound peer connected: version: 70016, blocks=827356, peer=221 (outbound-full-relay)
  240. bitcoin | 2024-01-25T19:42:25Z Socks5() connect to 157.245.35.47:8335 failed: general failure
  241. bitcoin | 2024-01-25T19:42:45Z New outbound peer connected: version: 70016, blocks=827356, peer=228 (outbound-full-relay)
  242. bitcoin | 2024-01-25T19:43:04Z Saw new header hash=00000000000000000000b94a6f77a8d4853e20e19bdf8e112523ccb7b9deff0a height=827357
  243. bitcoin | 2024-01-25T19:43:04Z [net] Saw new cmpctblock header hash=00000000000000000000b94a6f77a8d4853e20e19bdf8e112523ccb7b9deff0a peer=114
  244. bitcoin | 2024-01-25T19:43:04Z UpdateTip: new best=00000000000000000000b94a6f77a8d4853e20e19bdf8e112523ccb7b9deff0a height=827357 version=0x2389a000 log2_work=94.688443 tx=957292597 date='2024-01-25T19:42:46Z' progress=1.000000 cache=31.2MiB(158147txo)
  245. bitcoin | 2024-01-25T19:44:30Z Saw new header hash=00000000000000000000bd1e38026642fff6e1bf124d38295b4eaafab065b2c5 height=827358
  246. bitcoin | 2024-01-25T19:44:30Z [net] Saw new cmpctblock header hash=00000000000000000000bd1e38026642fff6e1bf124d38295b4eaafab065b2c5 peer=114
  247. bitcoin | 2024-01-25T19:44:31Z UpdateTip: new best=00000000000000000000bd1e38026642fff6e1bf124d38295b4eaafab065b2c5 height=827358 version=0x2701c000 log2_work=94.688457 tx=957294747 date='2024-01-25T19:44:04Z' progress=1.000000 cache=32.1MiB(165093txo)
  248. bitcoin | 2024-01-25T19:44:59Z Socks5() connect to 2409:40f2:2e:b7d8:e1ef:f101:add2:2af4:8333 failed: general failure
  249. bitcoin | 2024-01-25T19:50:09Z New outbound peer connected: version: 70016, blocks=827358, peer=238 (block-relay-only)
  250. bitcoin | 2024-01-25T19:52:46Z Socks5() connect to 45.82.243.148:8333 failed: connection refused
  251.  
  252. Tor logs
  253. --------
  254.  
  255. tor | Jan 25 17:01:03.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $79ACC2417F4301FC02F04165F31E20B851CC7AF5~kaenguru [JejBgW801mcf2K4rChOO+nSNFVuRoPuaB4z+wePySxY] at 109.70.100.69. Retrying on a new circuit.
  256. tor | Jan 25 17:01:19.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $864B095917EA3486738A138303FFC322E395D3AA~NTH41R3 [yS2hBQ2tllM8+el11QZ3fONpy8+y1HgS7qVXL9by3wE] at 192.42.116.204. Retrying on a new circuit.
  257. tor | Jan 25 17:01:19.000 [notice] Tried for 127 seconds to get a connection to [scrubbed]:443. Giving up.
  258. tor | Jan 25 17:01:20.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  259. tor | Jan 25 17:04:29.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  260. tor | Jan 25 17:09:50.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  261. tor | Jan 25 17:28:36.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  262. tor | Jan 25 18:07:42.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  263. tor | Jan 25 18:21:23.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  264. tor | Jan 25 18:23:06.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  265. tor | Jan 25 18:37:56.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  266. tor | Jan 25 18:46:03.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  267. tor | Jan 25 18:58:28.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  268. tor | Jan 25 19:12:20.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  269. tor | Jan 25 19:15:03.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  270. tor | Jan 25 19:30:46.000 [notice] Application asked to connect to port 0. Refusing.
  271. tor | Jan 25 19:35:17.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  272. tor | Jan 25 19:42:25.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  273. tor | Jan 25 19:44:59.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
  274. app-tor | Jan 25 16:58:58.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
  275. app-tor | Jan 25 16:59:02.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
  276. app-tor | Jan 25 16:59:04.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
  277. app-tor | Jan 25 16:59:05.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
  278. app-tor | Jan 25 16:59:06.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
  279. app-tor | Jan 25 16:59:06.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
  280. app-tor | Jan 25 16:59:06.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
  281. app-tor | Jan 25 16:59:06.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
  282. app-tor | Jan 25 16:59:07.000 [notice] Bootstrapped 100% (done): Done
  283. app-tor | Jan 25 16:59:38.000 [warn] Guard platinumbutterfly ($B7F27FBA6058F4F6D2ECBB715DE7539AF9E6C7BC) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 0/151. Use counts are 0/0. 0 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  284. app-tor | Jan 25 16:59:38.000 [warn] Guard zensursula ($0FBABB8C7B22CEDDFC849331E8E9E29C18081235) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 0/151. Use counts are 0/0. 0 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  285. app-tor | Jan 25 16:59:39.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 168 buildtimes.
  286. app-tor | Jan 25 16:59:42.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 423 buildtimes.
  287. app-tor | Jan 25 16:59:58.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 104 buildtimes.
  288. app-tor | Jan 25 17:00:10.000 [notice] Guard zensursula ($0FBABB8C7B22CEDDFC849331E8E9E29C18081235) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 229/328. Use counts are 206/206. 229 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  289. app-tor | Jan 25 17:00:14.000 [warn] Guard zensursula ($0FBABB8C7B22CEDDFC849331E8E9E29C18081235) 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 229/459. Use counts are 206/206. 229 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  290. app-tor | Jan 25 17:00:18.000 [notice] Guard platinumbutterfly ($B7F27FBA6058F4F6D2ECBB715DE7539AF9E6C7BC) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 228/326. Use counts are 118/118. 228 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  291. app-tor | Jan 25 17:00:25.000 [warn] Guard platinumbutterfly ($B7F27FBA6058F4F6D2ECBB715DE7539AF9E6C7BC) 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 201/403. Use counts are 115/115. 201 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
  292. app-tor | Jan 25 17:00:30.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 137 buildtimes.
  293. app-tor | Jan 25 17:00:35.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 125 buildtimes.
  294. app-tor | Jan 25 17:00:55.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 186 buildtimes.
  295. app-tor | Jan 25 17:01:04.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 120000ms after 18 timeouts and 46 buildtimes.
  296. app-tor | Jan 25 17:02:02.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 240000ms after 18 timeouts and 47 buildtimes.
  297. app-tor | Jan 25 17:03:22.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 329920ms after 18 timeouts and 249 buildtimes.
  298. app-tor | Jan 25 18:21:46.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
  299. app-tor | Jan 25 18:31:17.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 180 buildtimes.
  300. app-tor | Jan 25 18:39:25.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 126 buildtimes.
  301. app-tor | Jan 25 19:02:03.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 488 buildtimes.
  302. app-tor | Jan 25 19:37:45.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 440 buildtimes.
  303. app-tor | Jan 25 19:40:46.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 106 buildtimes.
  304.  
  305. API logs
  306. --------
  307.  
  308.  
  309. App logs
  310. --------
  311.  
  312. lnd
  313.  
  314. lnd-middleware-1 | LNDService {
  315. lnd-middleware-1 | connectionUrl: '10.21.21.106:10009',
  316. lnd-middleware-1 | cert: <Buffer 2d 2d 2d 2d 2d 42 45 47 49 4e 20 43 45 52 54 49 46 49 43 41 54 45 2d 2d 2d 2d 2d 0a 4d 49 49 43 4f 6a 43 43 41 65 43 67 41 77 49 42 41 67 49 52 41 4b ... 784 more bytes>,
  317. lnd-middleware-1 | macaroonFile: '/lnd/data/chain/bitcoin/mainnet/admin.macaroon'
  318. lnd-middleware-1 | }
  319. lnd-middleware-1 | [AsyncFunction: expectWalletToExist]
  320. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:37 +0000] "GET /v1/pages/lnd HTTP/1.1" 200 7022 "http://192.168.0.38/lightning" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  321. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:37 +0000] "GET /v1/lnd/info/version HTTP/1.1" 200 68 "http://192.168.0.38/lightning" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  322. lnd-middleware-1 | LNDService {
  323. lnd-middleware-1 | connectionUrl: '10.21.21.106:10009',
  324. lnd-middleware-1 | cert: <Buffer 2d 2d 2d 2d 2d 42 45 47 49 4e 20 43 45 52 54 49 46 49 43 41 54 45 2d 2d 2d 2d 2d 0a 4d 49 49 43 4f 6a 43 43 41 65 43 67 41 77 49 42 41 67 49 52 41 4b ... 784 more bytes>,
  325. lnd-middleware-1 | macaroonFile: '/lnd/data/chain/bitcoin/mainnet/admin.macaroon'
  326. lnd-middleware-1 | }
  327. lnd-middleware-1 | [AsyncFunction: expectWalletToExist]
  328. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:44 +0000] "GET /v1/lnd/wallet/btc HTTP/1.1" 200 221 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  329. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:44 +0000] "GET /v1/lnd/info/sync HTTP/1.1" 200 65 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  330. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:44 +0000] "GET /v1/lnd/transaction/ HTTP/1.1" 200 10007 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  331. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:44 +0000] "GET /v1/lnd/lightning/invoices HTTP/1.1" 200 178479 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  332. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:52:44 +0000] "GET /v1/lnd/lightning/payments HTTP/1.1" 200 19970 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  333. lnd-middleware-1 | LNDService {
  334. lnd-middleware-1 | connectionUrl: '10.21.21.106:10009',
  335. lnd-middleware-1 | cert: <Buffer 2d 2d 2d 2d 2d 42 45 47 49 4e 20 43 45 52 54 49 46 49 43 41 54 45 2d 2d 2d 2d 2d 0a 4d 49 49 43 4f 6a 43 43 41 65 43 67 41 77 49 42 41 67 49 52 41 4b ... 784 more bytes>,
  336. lnd-middleware-1 | macaroonFile: '/lnd/data/chain/bitcoin/mainnet/admin.macaroon'
  337. lnd-middleware-1 | }
  338. lnd-middleware-1 | [AsyncFunction: expectWalletToExist]
  339. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:53:04 +0000] "GET /v1/lnd/wallet/btc HTTP/1.1" 200 221 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  340. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:53:04 +0000] "GET /v1/lnd/info/sync HTTP/1.1" 200 65 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  341. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:53:04 +0000] "GET /v1/lnd/transaction/ HTTP/1.1" 200 10007 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  342. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:53:04 +0000] "GET /v1/lnd/lightning/invoices HTTP/1.1" 200 178479 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  343. lnd-middleware-1 | ::ffff:10.21.21.1 - - [25/Jan/2024:19:53:04 +0000] "GET /v1/lnd/lightning/payments HTTP/1.1" 200 19970 "http://192.168.0.38/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
  344.  
  345. ride-the-lightning
  346.  
  347. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:49:34 LND node not synced yet
  348. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:49:34 Retrying in 15 seconds
  349. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:49:49 LND node not synced yet
  350. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:49:49 Retrying in 15 seconds
  351. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:50:04 LND node not synced yet
  352. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:50:04 Retrying in 15 seconds
  353. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:50:19 LND node not synced yet
  354. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:50:19 Retrying in 15 seconds
  355. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:50:34 LND node not synced yet
  356. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:50:34 Retrying in 15 seconds
  357. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:50:49 LND node not synced yet
  358. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:50:49 Retrying in 15 seconds
  359. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:51:04 LND node not synced yet
  360. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:51:04 Retrying in 15 seconds
  361. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:51:19 LND node not synced yet
  362. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:51:19 Retrying in 15 seconds
  363. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:51:34 LND node not synced yet
  364. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:51:34 Retrying in 15 seconds
  365. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:51:50 LND node not synced yet
  366. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:51:50 Retrying in 15 seconds
  367. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:52:05 LND node not synced yet
  368. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:52:05 Retrying in 15 seconds
  369. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:52:20 LND node not synced yet
  370. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:52:20 Retrying in 15 seconds
  371. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:52:35 LND node not synced yet
  372. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:52:35 Retrying in 15 seconds
  373. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:52:50 LND node not synced yet
  374. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:52:50 Retrying in 15 seconds
  375. ride-the-lightning-boltz-1 | WARN : 2024/01/25 19:53:05 LND node not synced yet
  376. ride-the-lightning-boltz-1 | INFO : 2024/01/25 19:53:05 Retrying in 15 seconds
  377. ================
  378. ==== Result ====
  379. ================
  380.  
  381. The debug script did not automatically detect any issues with your Citadel.
Advertisement
Add Comment
Please, Sign In to add comment