Re: DNF error, but it looks like everything's OK

[YOUNG, MICHAEL A.]

On Mon, 14 Jan 2019, SternData wrote:

>  Just to record that this happened:
>
>  Ran a DNF update. All the normal stuff appeared, plus
>
>  Complete!
>  Exception ignored in: <function SwdbInterface.__del__ at 0x7f22c9e07488>
>  Traceback (most recent call last):
>   File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 262,
>  in __del__
>     self.close()
>   File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 305,
>  in close
>     self.swdb.closeTransaction()
>   File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291,
>  in swdb
>     self._swdb = libdnf.transaction.Swdb(self.dbpath)
>   File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line
>  729, in __init__
>     this = _transaction.new_Swdb(*args)
>  RuntimeError: Exec failed: database is locked 
I think this is a known issue. If I remember rightly it occurs when the 
sqlite database in /var/lib/dnf/history has got into a strange state and 
running
sqlite3 /var/lib/dnf/history/*.sqlite vacuum
should fix it.

 	Michael Young