Jam not working on Umbrel 1.1

Question

Jam not working on Umbrel 1.1

TowyTowy opened this issue a month ago · 8 comments

Hey, today I tried to install Jam on my Umbrel running Umbrel v1.1 but it simply gives me the following error. I've tried restarting, reinstalling etc. but to no avail.
No connection to backend: The server reported a problem: 502 Bad Gateway.

Logs:

tor_server-1  | Apr 26 13:05:56.180 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
tor_server-1  | Apr 26 13:05:56.180 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
tor_server-1  | Apr 26 13:05:56.180 [notice] Read configuration file "/tmp/torrc".
tor_server-1  | Apr 26 13:05:56.193 [notice] Opening Socks listener on 127.0.0.1:9050
tor_server-1  | Apr 26 13:05:56.193 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
tor_server-1  | Apr 26 13:05:56.000 [notice] Bootstrapped 0% (starting): Starting
tor_server-1  | Apr 26 13:05:56.000 [notice] Starting with guard context "default"
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor_server-1  | Apr 26 13:05:57.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
tor_server-1  | Apr 26 13:05:58.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
tor_server-1  | Apr 26 13:05:58.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
tor_server-1  | Apr 26 13:05:59.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
tor_server-1  | Apr 26 13:05:59.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
tor_server-1  | Apr 26 13:05:59.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7155, 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_server-1  | Apr 26 13:05:59.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7155, 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_server-1  | Apr 26 13:06:00.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
tor_server-1  | Apr 26 13:06:01.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
tor_server-1  | Apr 26 13:06:06.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
tor_server-1  | Apr 26 13:06:07.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors
tor_server-1  | Apr 26 13:06:08.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
tor_server-1  | Apr 26 13:06:08.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_server-1  | Apr 26 13:06:09.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_server-1  | Apr 26 13:06:09.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_server-1  | Apr 26 13:06:09.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_server-1  | Apr 26 13:06:10.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_server-1  | Apr 26 13:06:10.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_server-1  | Apr 26 13:06:11.000 [notice] Bootstrapped 100% (done): Done
jam_web_1     | [WARN  tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper.
jam_web_1     | Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
jam_web_1     | To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
jam_web_1     | Remove leftover wallet lockfiles before startup...
jam_web_1     | Waiting for bitcoind to accept RPC requests...
jam_web_1     | Successfully waited for bitcoind to accept RPC requests.
jam_web_1     | Creating wallet jam_default if missing...
jam_web_1     | Loading wallet jam_default...
jam_web_1     | [  OK  ] nginx
jam_web_1     | [  OK  ] tor
jam_web_1     | [  OK  ] ob-watcher
jam_web_1     | [  OK  ] jmwalletd
jam_web_1     | [  OK  ] boot
jam_web_1     | dinit: Service jmwalletd process terminated with exit code 1
jam_web_1     | dinit: Service ob-watcher process terminated with exit code 1
jam_web_1     | dinit: Service jmwalletd process terminated with exit code 1
jam_web_1     | dinit: Service ob-watcher process terminated with exit code 1
jam_web_1     | dinit: Service ob-watcher process terminated with exit code 1
jam_web_1     | dinit: Service jmwalletd process terminated with exit code 1
jam_web_1     | dinit: Service ob-watcher process terminated with exit code 1
jam_web_1     | dinit: Service ob-watcher restarting too quickly; stopping.
jam_web_1     | dinit: Service ob-watcher restarting too quickly; stopping.
jam_web_1     | [STOPPD] ob-watcher
jam_web_1     | dinit: Service jmwalletd process terminated with exit code 1
jam_web_1     | dinit: Service jmwalletd restarting too quickly; stopping.
jam_web_1     | dinit: Service jmwalletd restarting too quickly; stopping.
jam_web_1     | [STOPPD] jmwalletd
jam_app_proxy_1  | yarn run v1.22.19
jam_app_proxy_1  | $ node ./bin/www
jam_app_proxy_1  | [HPM] Proxy created: /  -> http://jam_web_1:80
jam_app_proxy_1  | Waiting for jam_web_1:80 to open...
jam_app_proxy_1  | Jam is now ready...
jam_app_proxy_1  | Listening on port: 5002
jam_app_proxy_1  | [HPM] Upgrading to WebSocket
jam_app_proxy_1  | [HPM] Upgrading to WebSocket
jam_app_proxy_1  | [HPM] Upgrading to WebSocket
jam_app_proxy_1  | [HPM] Upgrading to WebSocket
jam_app_proxy_1  | [HPM] Upgrading to WebSocket

Answer 1 · 2024-04-27T06:37:11.000Z

I can confirm that the issue is not exclusive to v1.0. v0.5.4 is also affected. The web container seems to use dinit to run jmwalletd, which fails. Can you obtain logs from it? (I'm not sure is dinit even has logs)

Answer 2 · 2024-04-27T09:22:45.000Z

Okay, interesting. I am not savvy enough to find the logs for jmwalletd (I tried). Luke told me he would let the relevant team know about this issue.

Answer 3 · 2024-05-01T04:18:32.000Z

Hey @TowyTowy and @highghlow I'm currently looking into this issue here: getumbrel/umbrel-bitcoin#19 (comment)

Can you let me know if simply restarting the Jam app fixes the issue?

umbrelOS 1.x: right click on Jam on homescreen and select "restart"
umbrelOS 0.5x: when SSHd in to your device run sudo ~/umbrel/scripts/app restart jam (don't run this on 1.x)

Answer 4 · 2024-05-01T08:42:43.000Z

Hey @nmfretz I'm glad someone's looking into it.

A restart does not fix it.

Answer 5 · 2024-05-01T10:11:41.000Z

Thanks @TowyTowy that's helpful 🤝

Answer 6 · 2024-05-01T23:57:32.000Z

Adding deprecatedrpc=create_bdb to bitcoin.conf fixed it for now.

Answer 7 · 2024-05-02T00:28:24.000Z

Bitcoin Node update just went live with a fix getumbrel/umbrel-apps#1074

Answer 8 · 2024-05-02T10:25:45.000Z

Great! Thank you.