giftjoin.blogg.se

1. #Attempt to write a readonly database db sqlite install
2. #Attempt to write a readonly database db sqlite update

At that time this bug will be closed as EOL if it remains open with a It is Fedora's policy to close all bug reports from releases that are no longer This message is a reminder that Fedora 32 is nearing its end of life.įedora will stop maintaining and issuing updates for Fedora 32 on. # sqlite3 /var/lib/dnf/history.sqlite < /tmp/history.sqlĪfter this, dnf history works with older items and my database was repaired. I have a copy of this broken sqlite file, if someone needs more testing.Īs a workaround, I can recover my history.sqlite file with these commands: I don't know, what's wrong on this i.name column. SELECT i.name FROM trans_item ti JOIN trans t ON ti.trans_id = t.id JOIN rpm i USING (item_id) SELECT 1 FROM trans_item ti JOIN trans t ON ti.trans_id = t.id JOIN rpm i USING (item_id) I am trying to run this SELECT partially in sqlite with curious results (passes, returns some rows without error): * see comment in TransactionItem.hpp - TransactionItemAction */Įrror: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row failed: data

#Attempt to write a readonly database db sqlite update

Same problem here and I didn't do any system-upgrade, just normal dnf update on my f32 system. Certainly it's beyond my abilities to debug it any further. I'll upload the sql dump as an attachment in case it's of use.

#Attempt to write a readonly database db sqlite install

I was running some commands to search for and install packages, some without sudo, some with, which I realise is vague, but beyond that I cannot think of anything that was even slightly untoward or unusual about what I was doing. I can't imagine what would have caused this problem. Then I replaced history.sqlite with history2.sqlite, and now dnf is working again. I deleted one of the rows from the sql and ran:

$ sqlite3 history.sqlite ".dump" |sqlite3 history-new.sqliteĮrror: near line 8859: UNIQUE constraint failed: trans_item.id On tree page 236 cell 57: Rowid 4840 out of orderįollowing the dump/restore test in #1669824, sqlite complained that my problem was a duplicate transaction. $ echo 'PRAGMA integrity_check ' | sqlite3 /var/lib/dnf/history.sqlite However, the ways that a database can be corrupt are legion. Somehow I've reproduced this problem, or a variant thereof, without either a crash or running out of disk space. also reported a while back on the fedora-users mailing list SQLite know that there's something wrong:Įcho 'PRAGMA integrity_check ' | sudo sqlite3 /var/lib/dnf/history.sqliteįragmentation of 5 bytes reported as 0 on page 1092Įrror: near line 1: database disk image is malformed It turns out that I can fix the problem with: Without intervention, this error persists. Version-Release number of selected component (if applicable): Broken version of /var/lib/dnf/history.sqliteĮrror: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row failed: database disk image is malformed