Closed carlaKC closed 6 months ago
Docker running everything correctly:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a138268ab5b6 lightninglabs/lnd:v0.17.0-beta "lnd --noseedbackup …" About a minute ago Up About a minute 9735/tcp, 10009/tcp ln_ln_000000
12487b8bd5d9 lightninglabs/lnd:v0.17.0-beta "lnd --noseedbackup …" About a minute ago Up About a minute 9735/tcp, 10009/tcp ln_ln_000001
9f3a0faecb81 lightninglabs/lnd:v0.17.0-beta "lnd --noseedbackup …" About a minute ago Up About a minute 9735/tcp, 10009/tcp ln_ln_000002
6ac3596457e4 bitcoindevproject/bitcoin-core:25.1 "/entrypoint.sh bitc…" About a minute ago Up About a minute (healthy) 8332-8333/tcp, 18332-18333/tcp, 18443-18444/tcp, 38332-38333/tcp ln_tank_000003
47d2e56bd572 bitcoindevproject/bitcoin-core:25.1 "/entrypoint.sh bitc…" About a minute ago Up About a minute (healthy) 8332-8333/tcp, 18332-18333/tcp, 18443-18444/tcp, 38332-38333/tcp ln_tank_000001
2acedce1ea0d bitcoindevproject/bitcoin-core:25.1 "/entrypoint.sh bitc…" About a minute ago Up About a minute (healthy) 8332-8333/tcp, 18332-18333/tcp, 18443-18444/tcp, 38332-38333/tcp ln_tank_000002
5fff4a53f530 bitcoindevproject/bitcoin-core:25.1 "/entrypoint.sh bitc…" About a minute ago Up About a minute (healthy) 8332-8333/tcp, 18332-18333/tcp, 18443-18444/tcp, 38332-38333/tcp ln_tank_000000
29c51222caeb prom/prometheus:latest "/bin/prometheus --c…" 15 minutes ago Up 15 minutes 0.0.0.0:9090->9090/tcp ln_prometheus
8aa1d29222eb grafana/grafana:latest "/run.sh" 15 minutes ago Up 15 minutes 0.0.0.0:3000->3000/tcp ln_grafana
8b8999c498f6 gcr.io/cadvisor/cadvisor:v0.47.2 "/usr/bin/cadvisor -…" 15 minutes ago Up 15 minutes (healthy) 0.0.0.0:8080->8080/tcp ln_cadvisor
280a252ac4e9 b10c/fork-observer:latest "/bin/sh -c /usr/loc…" 15 minutes ago Up 15 minutes 0.0.0.0:12323->2323/tcp ln_fork-observer
But all of the lightning nodes are stuck on syncing to chain - docker logs ln_ln_000001
has repeated:
2023-11-21 19:12:31.938 [DBG] LTND: Syncing to block timestamp: 2011-02-02 23:16:42 +0000 UTC, is synced=false
(and thus unable to open channels, I imagine)
That first log line appears to show network=warnet, when you used ln
earlier.
The test added 10 nodes, but in the demo graph it should be 3 or 4 IIRC
Perhaps reset and try the test command like this, if you change the network name:
warcli scenarios run ln_init --network=ln
.
If afk right now but this might work
I think Will is right. Probably easiest is just to never use --network=
and let warnet use its default ("warnet"). We don't even really support running more than one network at a time anyway 😬
On our end, @willcl-ark any RPC that accepts a network parameter like scenarios run
should check to see if that network exists and is running first! If we threw a "unknown network" error here I think that would help
warcli scenarios run ln_init --network=ln.
doh, yeah that's it!
Running warnet at 5535564 (Python 3.11.4):
Steps to Reproduce
Start network and check status:
Output:
Run scenario:
Logs
Full warnet.log.