Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dinit: Service jmwalletd process terminated with exit code 1 #122

Open
m4v1-21 opened this issue Mar 31, 2024 · 2 comments
Open

dinit: Service jmwalletd process terminated with exit code 1 #122

m4v1-21 opened this issue Mar 31, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@m4v1-21
Copy link

m4v1-21 commented Mar 31, 2024

Running kubuntu 22.04 with bitcoin core 26.0

tried running jam in docker with different credentials first, had problems starting the service (maybe conflict with port because of local mempool.space inside docker), tried with different port - didnt work, tried after shutting down mempool. at this point i got the webservice running but encontered some kind of error after clicking through the starting we gui.
Tried again with different credentials:

bash:
sudo docker run --rm -it --add-host=host.docker.internal:host-gateway --env JM_RPC_HOST="host.docker.internal" --env JM_RPC_PORT="8332" --env JM_RPC_USER="RPCUSER" --env JM_RPC_PASSWORD="RPCPWD" --env APP_USER="JAM" --env APP_PASSWORD="JAMPWD" --env ENSURE_WALLET="true" --env REMOVE_LOCK_FILES="true" --env RESTORE_DEFAULT_CONFIG="true" --volume jmdatadir:/root/.joinmarket --publish "8080:80" ghcr.io/joinmarket-webui/jam-standalone:v0.2.0-clientserver-v0.9.11

A clear and concise description of what you expected to happen.

Remove leftover wallet lockfiles before startup...
~/.joinmarket/ssl /src/scripts
Generating a RSA private key
.......++++
.......................................................................................................................................................................................................................................................................................................................................................................++++
writing new private key to 'key.pem'

/src/scripts
Waiting for bitcoind to accept RPC requests...
Successfully waited for bitcoind to accept RPC requests.
Creating wallet jm_webui_default if missing...
Loading wallet jm_webui_default...
[ OK ] nginx
[ OK ] tor
[ OK ] jmwalletd
[ OK ] ob-watcher
[ OK ] boot
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service jmwalletd restarting too quickly; stopping.
dinit: Service jmwalletd restarting too quickly; stopping.
[STOPPD] jmwalletd
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service ob-watcher restarting too quickly; stopping.
dinit: Service ob-watcher restarting too quickly; stopping.
[STOPPD] ob-watcher
^C[STOPPD] boot
[STOPPD] tor
[STOPPD] nginx

A clear and concise description of what the bug is and what actually happens.

Steps to reproduce the problem
tried to remove all docker files / image, rebooting, restart from scratch
-> still the same problem
maybe there is some kind of data left on my local storage that i cant find and thats messing with the installation?

Specifications

  • Version: jam-standalone:v0.2.0-clientserver-v0.9.11
  • Platform: Running kubuntu 22.04 with bitcoin core 26.0
  • Browser: Firefox (but problem lies within starting the program)

Additional context

Add any other context about the problem here to help explain your problem.
e.g. error logs or screenshots if applicable. Make sure to remove any confidential information before sharing screenshots or logs.

@m4v1-21 m4v1-21 added the bug Something isn't working label Mar 31, 2024
@theborakompanioni
Copy link
Collaborator

theborakompanioni commented Apr 1, 2024

Hey @m4v1-21!

Hmm.. it seems that your Bitcoin Core service is running, reachable and a wallet has been successfully created..
Bitcoin Core needs config deprecatedrpc=create_bdb (https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260), but it seems you already did that, right?

The logs of service jmwalletd would hopefully give more insight of what might the culprit here.
Can take a look into log file jmwalletd_stdout.log (e.g. by mapping the directory /var/log/jam)?

Thanks for trying out Jam 🙏

PS: If it is okay for you, I will transfer this issue to https://github.com/joinmarket-webui/jam-docker

@theborakompanioni theborakompanioni transferred this issue from joinmarket-webui/jam Apr 22, 2024
@theborakompanioni
Copy link
Collaborator

Hey @m4v1-21.. any update on this?

Bitcoin Core needs config deprecatedrpc=create_bdb (https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260), but it seems you already did that, right?

and

Can take a look into log file jmwalletd_stdout.log (e.g. by mapping the directory /var/log/jam)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants