Open
Description
When updating from v24.05 to v24.08.2, the update fails with the following logs:
Core-Lightning starting
2024-10-22T17:12:18.465Z INFO lightningd: v24.08.2
...
2024-10-22T17:12:19.422Z UNUSUAL plugin-bookkeeper: topic 'utxo_deposit' is not a known notification topic
2024-10-22T17:12:19.422Z UNUSUAL plugin-bookkeeper: topic 'utxo_spend' is not a known notification topic
2024-10-22T17:12:25.445Z DEBUG plugin-clnrest: REST Server is starting at https://0.0.0.0:3010
2024-10-22T17:12:25.446Z DEBUG plugin-clnrest: Certs Path: /root/.lightning/bitcoin
2024-10-22T17:12:25.455Z DEBUG lightningd: Looking for [autoclean,failedforwards,num]
2024-10-22T17:12:25.460Z INFO plugin-clnrest: REST server running at https://0.0.0.0:3010
2024-10-22T17:12:25.464Z DEBUG lightningd: Looking for [autoclean,succeededpays,num]
Error executing statement: ERROR: current transaction is aborted, commands ignored until end of transaction block
bookkeeper: Outstanding taken pointers: 0x5606eceb0a88
2024-10-22T17:12:25.483Z DEBUG lightningd: Looking for [autoclean,failedpays,num]
2024-10-22T17:12:25.484Z DEBUG hsmd: Client: Received message 27 from client
2024-10-22T17:12:25.492Z INFO plugin-bookkeeper: Killing plugin: exited before replying to init
2024-10-22T17:12:25.492Z **BROKEN** plugin-bookkeeper: Plugin marked as important, shutting down lightningd!
2024-10-22T17:12:25.492Z DEBUG lightningd: io_break: lightningd_exit
2024-10-22T17:12:25.501Z DEBUG plugin-recover: Recover Plugin Initialised!
...
2024-10-22T17:12:25.573Z DEBUG lightningd: Looking for [autoclean,expiredinvoices,num]
2024-10-22T17:12:55.528Z DEBUG lightningd: clnrest: failed to self-terminate in time, killing.
2024-10-22T17:12:55.528Z DEBUG lightningd: io_break: destroy_plugin
2024-10-22T17:12:55.528Z DEBUG connectd: Shutting down
2024-10-22T17:12:55.529Z DEBUG gossipd: Shutting down
2024-10-22T17:12:55.531Z DEBUG hsmd: Shutting down
Reading JSON input: Connection reset by peerReading JSON input: Connection reset by peerReading JSON input: Connection reset by peerReading JSON input: Connection reset by peerReading JSON input: Connection reset by peerReading JSON input: Connection reset by peer
We somewhat have a special config as we are using Postgres as DB. Any idea what might be the issue ?
Reverting to v24.05(-modded) makes it work again so it's not a question of permissions to access the DB I think.
Metadata
Metadata
Assignees
Labels
No labels