Jam Fails with No Connection to Backend 502 error

[Bonzbonanza]

Expected behavior

Jam to complete a sweep.

Actual behavior

Previously was able to complete a sweep over a day. Trying again and Jam is disconnecting from the backend after only one completed transaction, twice. The first time that this happened today I was able to restart Jam and schedule another sweep, but that has also failed.

Steps to reproduce the problem

1. Run Sweep
2. Wait

Specifications

• Version: Synology VM
• Platform: Umbrel
• Browser: N/A

Additional context

Logs attached (removed)

[theborakompanioni]

Hey @Bonzbonanza. Sorry for the delay and your unpleasant experience. There is too little info in the logs to actually determine the error cause. It seems Bitcoin Core is running and is reachable for Jam, but the wallet daemon keeps shutting down. Would it be possible to inspect the log files in /var/log/jam? Please do not include any private or personal information, possibly only the latest error messages :pray:

[Bonzbonanza]

Hi @Thebora,

No worries, thanks for the reply. Admittedly, I am very poor at using command line interfaces and had to search for basic Linux commands, but with the Terminal app built into UmbrelOS I don't seem to be able to even find the log. For instance, /var/log returns "Is a directory" but /var/log/jam returns "No such file or directory". Running ls only gives me one file for an SSH key that I created trying to connect during this session. Can you give any insight into how to get the log, or is Umbrel locked down?

[theborakompanioni]

I don't seem to be able to even find the log. For instance, /var/log returns "Is a directory" but /var/log/jam returns "No such file or directory".

You'd need switch into the Jam container, e.g. with docker exec -it jam_web_1 bash (maybe the container is named differently, find out with docker ps | grep jam if the previous command did not work). Then view the log file in /var/log/jam with tail -n 200 -f /var/log/jam/jmwalletd_stdout.log (and/or jmwalletd_stderr.log). https://jamdocs.org/FAQ/#how-do-i-view-the-log-file

Let me know if that works out for you. Please do not hesitate to write here if it did nor work or does not make sense to you. :pray:

[Bonzbonanza]

While the instructions are indeed over my head when though I could probably brute force them if I knew where to enter the commands, the first obstacle is that I'm not using a docker container. My Umbrel is running as it's own VM on a NAS. I'm remote from the NAS which makes it even harder as I access via a browser using TailScale. If you can suggest another method I'm willing to try.

This makes me think that a log output function in the app would be a good idea as it would then be a download in the browser.

[theborakompanioni]

While the instructions are indeed over my head when though I could probably brute force them if I knew where to enter the commands, the first obstacle is that I'm not using a docker container. My Umbrel is running as it's own VM on a NAS. I'm remote from the NAS which makes it even harder as I access via a browser using TailScale. If you can suggest another method I'm willing to try. This makes me think that a log output function in the app would be a good idea as it would then be a download in the browser.

Umbrel uses docker internally to run applications. You'd need to ssh into it (as I assume you did earlier when you said that there is no such directory).

There is a "log output function" in the app (for some integrations - those that use the standalone image), but it is of no use if the application does not start, damn.. :sweat_smile:

[Bonzbonanza]

Thebora, When trying to execute the commands mentioned @.:~$ exec -it jam_web_1 bash -bash: exec: -i: invalid option exec: usage: exec [-cl] [-a name] [command [argument ...]] [redirection ...] @.:~$ docker ps | grep jampermission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.44/containers/json": dial unix /var/run/docker.sock: connect: permission denied

I restarted Jam from the Umbrel Home screen and got access to the logs, though they seem to be pretty short. I assume from the restart, which makes me wonder what happens to the older logs.

Logs

User data location: /root/.joinmarket/ 2024-09-09 19:00:47,327 [INFO] Starting jmwalletd on port: 28183 2024-09-09 19:00:47,661 [INFO] Joinmarket daemon listening on port 27183 <Request at 0x7f0a182a0040 method=POST uri=/api/v1/wallet/JamWallet.jmdat/unlock clientproto=HTTP/1.1> b'POST' b'/api/v1/wallet/JamWallet.jmdat/unlock' {} b'/api/v1/wallet/JamWallet.jmdat/unlock' <_io.BytesIO object at 0x7f0a18253ef0> [(b'Host', [b'w.xxx.yyy:5002']), (b'X-Real-Ip', [b'10.21.0.14']), (b'X-Forwarded-For', [b'::ffff:10.21.0.1, 10.21.0.14']), (b'X-Forwarded-Proto', [b'http']), (b'Content-Length', [b'43']), (b'Priority', [b'u=4']), (b'Sec-Gpc', [b'1']), (b'Cookie', [b'_gorilla_csrf=; UMBREL_PROXY_TOKEN=]), (b'DNT', [b'1']), (b'Origin', [b'http://100.64.xxx.yyy:5002']), (b'Content-Type', [b'text/plain;charset=UTF-8']), (b'Referer', [b'http://w.xxx.yyy:5002/']), (b'Accept-Encoding', [b'gzip, deflate']), (b'Accept-Language', [b'en-US,en;q=0.5']), (b'Accept', [b'/']), (b'User-Agent', [b'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0']), (b'X-Forwarded-Host', [b'w.xxx.yyy:5002'])] 2024-09-09 19:01:24,319 [WARNING] Connection had broken pipe, attempting reconnect. 2024-09-09 19:01:28,655 [INFO] Starting transaction monitor in walletservice

[theborakompanioni]

So, it seems that it is sorted out? Or does it keep happening? Is there anything else you did before it the hiccups started? On integrations like Umbrel Jam tries to only start if Bitcoin Core accepts RPC requests and is completely synced. Maybe there is a chance this is not working properly on every Core version.. :thinking:

[Bonzbonanza]

No, same problems. Core just updated to 27.1 last night after using Jam to do a couple quick Conjoins, then my computer that I use to connect to the Umbrel via a browser rebooted overnight. This morning there's the same error. Restarting the app is only a temporary fix that seems to work while then using it, but during the Sweep operation it always fails.

-------- Original Message -------- On 9/12/24 1:33 AM, Thebora Kompanioni wrote:

So, it seems that it is sorted out? Or does it keep happening? Is there anything else you did before it the hiccups started? On integrations like Umbrel Jam tries to only start if Bitcoin Core accepts

DuckDuckGo removed one tracker. More

Deactivate

So, it seems that it is sorted out? Or does it keep happening? Is there anything else you did before it the hiccups started? On integrations like Umbrel Jam tries to only start if Bitcoin Core accepts RPC requests and is completely synced. Maybe there is a chance this is not working properly on every Core version.. 🤔

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[theborakompanioni]

I am sorry I cannot identify the error based on the description : / Do single collaborative transactions or direct-spends work normally?

[Bonzbonanza]

Yes, single collaborative transactions generally work, though some have taken a couple tries. Spends are no issue.

-------- Original Message -------- On 9/14/24 1:53 PM, Thebora Kompanioni wrote:

I am sorry I cannot identify the error based on the description : / Do single collaborative transactions or direct-spends work normally? —Reply to this email directly, view it on GitHub, or unsubscrib

DuckDuckGo removed one tracker. More

Deactivate

I am sorry I cannot identify the error based on the description : / Do single collaborative transactions or direct-spends work normally?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[theborakompanioni]

Hmm.. still scratching my head about this. I am really shooting in the dark here wondering what might be the culprit.. e.g. Have you updated Bitcoin Core recently? A new version should be released shortly. Hopefully your situation improves but this would be a more than lucky coincidence.