Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- =====================
- = Umbrel debug info =
- =====================
- Umbrel version
- --------------
- 0.3.10
- Memory usage
- ------------
- total used free shared buff/cache available
- Mem: 3,9G 2,1G 127M 146M 1,7G 1,5G
- Swap: 448M 336M 111M
- total: 52,9%
- bitcoin: 15,3%
- electrs: 6,1%
- lnd: 1,2%
- tor: 0,8%
- system: %
- Filesystem information
- ----------------------
- Filesystem Size Used Avail Use% Mounted on
- /dev/sda5 960G 490G 431G 54% /
- /dev/sda5 960G 490G 431G 54% /
- Karen logs
- ----------
- Deriving keys...
- cat: /home/sg/db/umbrel-seed/seed: No such file or directory
- Missing derivation parameter, this is unsafe, exiting.
- Got signal: change-password
- karen is getting triggered!
- This script must only be run on Umbrel OS
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- Got signal:
- karen is getting triggered!
- Got signal: debug
- karen is getting triggered!
- Got signal: debug
- karen is getting triggered!
- Got signal: debug
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- ./karen: line 68: /home/sg/events/triggers/: Is a directory
- Debug result file generated
- Debug result file generated
- Debug result file generated
- 574624 pts/0 S 0:00 bash ./karen
- 574651 pts/0 S 0:00 bash ./karen
- karen is already running
- Got signal: change-password
- karen is getting triggered!
- This script must only be run on Umbrel OS
- Got signal: debug
- karen is getting triggered!
- Docker containers
- -----------------
- NAMES STATUS
- middleware Up 7 minutes
- bitcoin Up 7 minutes
- nginx Up 7 minutes
- lnd Up 7 minutes
- manager Up 7 minutes
- electrs Up 7 minutes
- dashboard Up 7 minutes
- tor Up 7 minutes
- Bitcoin Core logs
- -----------------
- Attaching to bitcoin
- bitcoin | 2021-06-02T17:30:00Z init message: Done loading
- bitcoin | 2021-06-02T17:30:00Z msghand thread start
- bitcoin | 2021-06-02T17:30:00Z opencon thread start
- bitcoin | 2021-06-02T17:30:00Z addcon thread start
- bitcoin | 2021-06-02T17:30:00Z net thread start
- bitcoin | 2021-06-02T17:30:00Z dnsseed thread start
- bitcoin | 2021-06-02T17:30:00Z Waiting 300 seconds before querying DNS seeds.
- bitcoin | 2021-06-02T17:30:02Z New outbound peer connected: version: 70015, blocks=685984, peer=0 (block-relay)
- bitcoin | 2021-06-02T17:30:05Z New outbound peer connected: version: 70015, blocks=685984, peer=1 (block-relay)
- bitcoin | 2021-06-02T17:30:11Z P2P peers available. Skipped DNS seeding.
- bitcoin | 2021-06-02T17:30:11Z dnsseed thread exit
- bitcoin | 2021-06-02T17:30:18Z New outbound peer connected: version: 70015, blocks=685984, peer=2 (full-relay)
- bitcoin | 2021-06-02T17:30:36Z Socks5() connect to 2a01:cb19:849c:6300:e868:ed57:f0e5:3c1:8333 failed: general failure
- bitcoin | 2021-06-02T17:30:39Z New outbound peer connected: version: 70016, blocks=685984, peer=3 (full-relay)
- bitcoin | 2021-06-02T17:31:00Z Socks5() connect to 83.68.131.39:8333 failed: general failure
- bitcoin | 2021-06-02T17:31:02Z New outbound peer connected: version: 70015, blocks=685984, peer=4 (full-relay)
- bitcoin | 2021-06-02T17:31:02Z Socks5() connect to 2a00:f440:0:3001::162:8333 failed: general failure
- bitcoin | 2021-06-02T17:31:04Z New outbound peer connected: version: 70016, blocks=685984, peer=5 (full-relay)
- bitcoin | 2021-06-02T17:31:05Z New outbound peer connected: version: 70015, blocks=685984, peer=6 (full-relay)
- bitcoin | 2021-06-02T17:31:06Z New outbound peer connected: version: 70015, blocks=685984, peer=7 (full-relay)
- 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
- bitcoin | 2021-06-02T17:31:34Z loadblk thread exit
- bitcoin | 2021-06-02T17:31:49Z New outbound peer connected: version: 70015, blocks=685984, peer=8 (full-relay)
- bitcoin | 2021-06-02T17:31:50Z New outbound peer connected: version: 70015, blocks=685984, peer=9 (full-relay)
- bitcoin | 2021-06-02T17:31:51Z New outbound peer connected: version: 70016, blocks=685984, peer=11 (full-relay)
- bitcoin | 2021-06-02T17:32:33Z New outbound peer connected: version: 70016, blocks=685984, peer=12 (full-relay)
- bitcoin | 2021-06-02T17:32:55Z Socks5() connect to 118.173.163.196:8333 failed: general failure
- 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)
- bitcoin | 2021-06-02T17:33:36Z New outbound peer connected: version: 70016, blocks=685985, peer=13 (full-relay)
- bitcoin | 2021-06-02T17:33:57Z New outbound peer connected: version: 70016, blocks=685985, peer=14 (full-relay)
- LND logs
- --------
- Attaching to lnd
- 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
- lnd | 2021-06-02 17:28:15.886 [INF] LTND: Active chain: Bitcoin (network=mainnet)
- lnd | 2021-06-02 17:28:15.886 [INF] LTND: Opening the main database, this might take a few minutes...
- lnd | 2021-06-02 17:28:15.887 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
- lnd | 2021-06-02 17:28:15.939 [INF] CHDB: Checking for schema update: latest_version=20, db_version=20
- lnd | 2021-06-02 17:28:15.939 [INF] LTND: Database now open (time_to_open=52.766291ms)!
- lnd | 2021-06-02 17:28:16.099 [INF] RPCS: Password RPC server listening on 0.0.0.0:10009
- lnd | 2021-06-02 17:28:16.121 [INF] RPCS: Password gRPC proxy started at 0.0.0.0:8080
- 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.
- Tor logs
- --------
- Attaching to tor
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
- 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.
- tor | Jun 02 17:28:08.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
- tor | Jun 02 17:28:09.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
- 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.)
- tor | Jun 02 17:28:10.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
- tor | Jun 02 17:28:11.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
- tor | Jun 02 17:28:13.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
- tor | Jun 02 17:28:14.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
- tor | Jun 02 17:28:14.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
- tor | Jun 02 17:28:14.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
- tor | Jun 02 17:28:15.000 [notice] Bootstrapped 100% (done): Done
- 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.
- 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.
- 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.
- 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.
- tor | Jun 02 17:31:00.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
- tor | Jun 02 17:32:55.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
- ================
- ==== Result ====
- ================
- The debug script did not automatically detect any issues with your Umbrel.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement