Weird dnf problem... Fixed, but weird.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey all,

Background -- I run a cluster of x86_64, armfp, and aarch64 systems and
I use a shared cache on my 100TB NAS for dnf so a package (even if it's
a DRPM) only has to be downloaded once.  Works pretty damn well for me
and I know other people have tried to use (abuse) pkgcacher and socks
and straight nfs and others to do this.  The dnf maintainers should
take note of a need (I've browsed some of the bugzilla reports).  There
are a few of us out there that want to download rpm files ONCE and
avoid beating the sh*t out of the mirrors but don't want to build
entire mirror repositories.  But that wasn't the cause of this problem.
It merely tripped over it.

IAC, on a couple of my Raspberry Pi systems, I started getting this
weird error about an sqlite error in "Generating completion cache..."
during many operations.  Well, I'm pointed at an alternate cache
location but something was seriously wrong here.  Just plain dnf was
giving me the same error, ignoring the dnf-overlay front-end.  Tried
all the "dnf clean" options - no joy.  Tried "rpm --rebuilddb" - no
joy.

Finally chased down the error message in the code to this file...

/usr/lib/python3.7/site-packages/dnf-plugins/generate_completion_cache.py

And this line:

        self.cache_file = "/var/cache/dnf/packages.db"

Fancy that.  It apparently doesn't obey the caching options in dnf.conf
or from the command line.  It also doesn't get cleaned in the cleanup
operations.  Your only option really is to remove that db file and
rerun dnf update again to rebuild it and it's cool!

I've filed a bug report here:

https://bugzilla.redhat.com/show_bug.cgi?id=1807238

Mostly, it can be ignored.  I'm not sure WHY a bash completion database
should be in a hard coded location but I'm not sure what would be
better in the local system (maybe something in /var/lib) but it was
frustrating to have to chase this thing down in the code when that damn
database got corrupted and even worse that dbf could not clean it.

In case anyone else gets bit by this...

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  mhw@xxxxxxxxxxxx
   /\/\|=mhw=|\/\/          | (c) +1 678 463-0932 |  http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN       | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux