Add Sensei #9
Add Sensei #9
Conversation
| @@ -0,0 +1,264 @@ | |||
| package main | |||
There was a problem hiding this comment.
@johncantrell97 I might now be getting into a different class of hurdles:
node-start_1 | thread 'main' panicked at 'invalid bitcoind rpc config: Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }', src/main.rs:200:14
node-start_1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
node-start_1 | manage your sensei node at http://127.0.0.1:5401/admin/nodes
node-start_1 | starting 02482907cbfcfa4ec558978bf336203f4af7c010383134b705fa60ab1c687461c9@127.0.0.1:9735
node-start_1 | thread 'sensei' panicked at 'assertion failed: `(left == right)`
node-start_1 | left: `0c84467d65d0150756208a428f6a0cb281a7c1c9f594c8d7f556e8875a7f0fb7`,
node-start_1 | right: `6080f1f6eea2bf23c045f549de8ec109fa8cb6e3407fcb6f32ddc884d925a27e`: Blocks must be connected in chain-order - the connected header must build on the last connected header', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/lightning-0.0.108/src/ln/channelmanager.rs:5478:13
This should be reproducible by running ./run.sh sensei
There was a problem hiding this comment.
well the first panic indicates incorrect bitcoind rpc configuration.
the second one is saying that it tried to connect a block where the header.prev_blockhash did not match the best known blockhash. so for some reason it missed blocks.
it's odd that it even got that far or are these separate runs where you fixed rpc info?
I'd try blowing up your sensei db and try a fresh run
There was a problem hiding this comment.
Yes, the first one I think is when it starts a bit early and fails because bitcoind isn't running yet. Docker-compose will then restart, so yes, this could be considered separate runs. I believe it's unrelated to the second error.
The sensei db will be created new every time I run run.sh. But I did find out that the error isn't always happening. Appears to be timing-dependent. Perhaps because a whole bunch of blocks are generated in quick succession, something bad happens occasionally?
| panic("not implemented") | ||
| } | ||
|
|
||
| func (l *senseiConnection) SendPayment(invoice string, aliasMap map[string]string) error { |
There was a problem hiding this comment.
Test is still a bit flakey, but I did get to the point where the test payments are started. Only it seems that they all execute in parallel?
Is it possible to do a synchronous payment?
node-start_1 | 2022-06-14T07:04:36.291228969Z EVENT: initiated sending 25000000 msats to 02d191e330745d099741f73a1eccf9d1f8de4e97888f06f283f98dfe787bbb937b
node-start_1 | 2022-06-14T07:04:36.346061844Z EVENT: initiated sending 25000000 msats to 036ecb98c2fc0fa66086943e0d547cf996e9970503fc86001f1cf4c2ce0eda9039
node-start_1 | 2022-06-14T07:04:36.358378344Z EVENT: initiated sending 25000000 msats to 02d191e330745d099741f73a1eccf9d1f8de4e97888f06f283f98dfe787bbb937b
node-start_1 | 2022-06-14T07:04:36.386639761Z EVENT: initiated sending 25000000 msats to 036ecb98c2fc0fa66086943e0d547cf996e9970503fc86001f1cf4c2ce0eda9039
node-start_1 | 2022-06-14T07:04:36.506249761Z EVENT: initiated sending 80000000 msats to 030b59aec6963bf7ae3519e6ec88e7309ab03da11c0aae9776cb135634687f98d8
node-start_1 | 2022-06-14T07:04:36.528653969Z EVENT: initiated sending 20000000 msats to 034206515ac01a2dac35d14f31b4531f82e8ac154afd627c4290345222a98854ba
node-start_1 | 2022-06-14T07:04:36.550613428Z EVENT: initiated sending 20000000 msats to 0371b2ba5c50629bfd435d79d81071d0aa556e2d51222c7cd0b8b453c29f024e07
node-start_1 | 2022-06-14T07:04:36.645271011Z
node-start_1 | 2022-06-14T07:04:37.109017053Z EVENT: Failed to send payment to payment hash "fdd8ff6c01dce16021653a291bb82e59252671051982b0d7697953c5fb67e656": exhausted payment retry attempts
node-start_1 | 2022-06-14T07:04:37.499747386Z EVENT: Failed to send payment to payment hash "4ebcf0252ca8165191152e6dab2ad12409199365359bd0f61f8b3d398251bea5": exhausted payment retry attempts
node-start_1 | 2022-06-14T07:04:37.499757803Z EVENT: successfully sent payment of Some(20000000) millisatoshis (fee 0 msat) from payment hash "d2aa565120294b270d72816a40a2b789c257f4230bc575ac9db160a022fb35fe" with preimage "79899d82a7f080e88e4def0a2ec4e61671a2d5073ea685d973f3dd727617aa7b"
node-start_1 | 2022-06-14T07:04:38.217352012Z
node-start_1 | 2022-06-14T07:04:38.311052220Z EVENT: Failed to send payment to payment hash "2a92de7a41f1643ae3de4b1852fb70d0cea9524d9a5fd08c948265a122a30541": exhausted payment retry attempts
node-start_1 | 2022-06-14T07:04:38.331752678Z EVENT: Failed to send payment to payment hash "f3bd8383f12c96cd2d1ae5a0fa77c2b37f6e61deb33521c5b79c56d4a9b395f1": exhausted payment retry attempts
node-start_1 | 2022-06-14T07:04:38.348938595Z EVENT: Failed to send payment to payment hash "f9dff00f0f2cfe5b9193c44fd488634c8fd14756406f8a7d3524d2043f5703b6": exhausted payment retry attempts
No description provided.