backup: sqlite3 check in on_init can cause a hang at startup
See original GitHub issueThe call to listconfigs
inside the db_sync
hook can hang indefinitely in some circumstances. See https://github.com/ElementsProject/lightning/issues/4348#issuecomment-769449638
I think it would be good to move this check to a different hook. Or remove it.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Python SQLite: database is locked - Stack Overflow
Ask the database shell to check itself: $ sqlite3 cache.db "pragma integrity_check;"; Backup the database $ sqlite3 cache.db ".backup cache.db.bak" ...
Read more >How To Corrupt An SQLite Database File
The best approach to make reliable backup copies of an SQLite database is to make use of the backup API that is part...
Read more >Command Line Shell For SQLite
On startup, the sqlite3 program will show a brief banner message then prompt you to enter SQL. Type in SQL statements (terminated by...
Read more >Frequently Asked Questions - SQLite
Short answer: A column declared INTEGER PRIMARY KEY will autoincrement. Longer answer: If you declare a column of a table to be INTEGER ......
Read more >Backup via file system backup software - SQLite Forum
Can I assume the backup software will always snapshot a ... Crash Consistent backups depend on the ability of the filesystem to "fix...
Read more >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 FreeTop 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
Top GitHub Comments
Bet that’s why the CI often failed/timeout on the backup plugin lately. ( @gallizoltan ) Someone already some clues? I will try to reproduce / isolate this.
It would be possible to defer the check, but as I understand the nature of the check seems to be to want to fail quickly in the case of a wrong database kind.