Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CL run lightning-cli backup-compact regularly
See original GitHub issueThe CL database backup can fill up the SDcard, but compacting is efficient:
$ config.scripts/cl-plugin.backup.sh backup-compact
/home/bitcoin/.lightning/bitcoin/lightningd.sqlite3
# Running -cli backup-compact ...
{
"before": {
"backupsize": 1798100953,
"version_count": 198720
},
"after": {
"version_count": 2,
"backupsize": 130356568
}
}
Went from 1.7 GB to 130MB. the actual database on the same node:
$ sudo du -h /mnt/hdd/app-data/.lightning/bitcoin/lightningd.sqlite3
125M /mnt/hdd/app-data/.lightning/bitcoin/lightningd.sqlite3
Can use
config.scripts/cl-plugin.backup.sh backup-compact
or just:
lightning-cli backup-compact
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes. Complete with fb65c0e9b1f7d7e362503f8df020e05de3fc5c49 I am running with the settings since the commits, had no issues.
Since CL does not need to stop for this it could be a cronjob installed with the backup plugin.