PDA

View Full Version : Missing Section Headers.



Irmis
25th July 2008, 09:37 PM
Until two days ago I was a Kubuntu user, I decided to give Fedora a whirl. And I came upon a problem, Yum won't update. After abusing the search tool I almost found a way to fix the fix the problem. Then I can across this error:

Loaded plugins: refresh-packagekit
rpmdb: Thread/process 9481/3087787712 failed: Thread died in Berkeley DB library
Config Error: File contains no section headers.
file: file://///etc/yum.repos.d/CentOS-Media.repo, line: 1
'enabled=0\n'


And I can't find a solution to that particular problem. Although I bet the solution will be annoyingly simple.

Hlingler
25th July 2008, 10:19 PM
Why is there a CentOS repo file on your Fedora OS? And pointing to a Live-CD/DVD to boot from the looks of it?? What release of Fedora did you install (looks like F9 if you got PackageChit)???

Suggest that you move that spurious repo file out of the way. As root user:
mv /etc/yum.repos.d/CentOS-Media.repo /etc/yum.repos.d/CentOS-Media.repo.goofiness

Then try again.

V

Irmis
25th July 2008, 11:12 PM
Good news is that it worked. The bad news


Loaded plugins: refresh-packagekit
rpmdb: Thread/process 9481/3087787712 failed: Thread died in Berkeley DB library
Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again


Hmm that's a bit of a bother.

Hlingler
26th July 2008, 12:22 AM
Try to clean the YUM caches first (as root user):
yum clean all

Also, verify that your Fedora repo files are pointing to the right places:
~]$ cat /etc/yum.repos.d/fedora.repo
[fedora]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEY
name=Fedora $releasever - $basearch
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
enabled=1
gpgcheck=1
[...]
~]$ cat /etc/yum.repos.d/fedora-updates.repo
[updates]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
name=Fedora $releasever - $basearch - Updates
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch
enabled=1
gpgcheck=1
[...]Then try again.

If that fails, post results:
yum repolist

V

Irmis
26th July 2008, 12:51 AM
cat /etc/yum.repos.d/fedora.repo



[fedora]
name=Fedora $releasever - $basearch
failovermethod=priority
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEY

[fedora-debuginfo]
name=Fedora $releasever - $basearch - Debug
failovermethod=priority
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-debug-$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEY

[fedora-source]
name=Fedora $releasever - Source
failovermethod=priority
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/source/SRPMS/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releasever&arch=$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEY


After yum repolist it does


Loaded plugins: refresh-packagekit
rpmdb: Thread/process 9481/3087787712 failed: Thread died in Berkeley DB library
Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again

Hlingler
26th July 2008, 04:17 AM
Yes, but both of the errors that you posted refer to the fedora updates repo, so that's the file that you really need to check closely: /etc/yum.repos.d/fedora-updates.repo. Note that each repo file may contain settings for more than one repo.

Also, the answers/advice/suggestions that you get here are likely to be just as accurate and helpful as the background information that you provide. It is still unclear why and how a CentOS repo file came to be on your Fedora OS. In addition, your last post indicates that the fedora-source repository is enabled. That particular repo should almost never be needed nor enabled. Suggest that you edit the file /etc/yum.repos.d/fedora.repo (as root user) to disable it:

[...]
[fedora-source]
name=Fedora $releasever - Source
failovermethod=priority
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/source/SRPMS/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEYFinally, the output of command: yum repolist was requested, so that we can see any potential problems/conflicts/etc., and so that we know which repositories and which repo files are likely to be in use. Please post those results.

V

Irmis
26th July 2008, 04:33 AM
I think I added that out of place repository by accident, while trying to "fix" the problem. I tend to use trial and error. Lots of the latter.

But each time I did yum repolist I got:


Loaded plugins: refresh-packagekit
rpmdb: Thread/process 9481/3087787712 failed: Thread died in Berkeley DB library
Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again

Hlingler
26th July 2008, 04:48 AM
Ah, I read you now: it's choking even on the query for a repolist.

Oof. Looks like things are pretty well hosed then. Before getting radical, try:

> Run the command with that packagechit plugin disabled:
[sudo] yum --noplugins repolist
See if that gets better results.

> As root user, surf to folder /var/cache/yum and start cleaning out stuff manually, especially from the folder: /var/cache/yum/updates. Remove any and all files from that folder and sub-folders (it's OK to do so - that's what 'yum clean all' is supposed to do...). Do not remove any folders, just files.

> If those things fail to produce acceptable results, you'll probably need to re-create the RPM database. Only if the easier stuff above doesn't work though....

V

Irmis
26th July 2008, 05:32 AM
I looked in all those folders, they are all empty. I wager those folders should have something in them. I installed from a DVD ,iso file I got from a torrent from http://fedoraproject.org/get-fedora. Wow I really screwed the pooch on this one.

Hlingler
26th July 2008, 05:58 AM
Well, poo.

No, those folders should be empty, because that's what 'yum clean all' is supposed to do, but I thought that maybe it left some garbage laying around because of that message you are getting.

Yes, I think you need to re-build the RPM database. I'm only guessing, but it looks from the output like maybe that rogue repo file left some poison in there. This takes a little time (<30 minutes or so), but isn't all that difficult. I've had to do it more than once. :rolleyes: Follow the instructions here: http://www.rpm.org/hintskinks/repairdb/. NOTE what he says about backing up: if for any reason (power failure, X11/Xorg crash takes out GUI, some other app eating HDD space, whatever) RPM is interrupted and/or cannot complete it's rebuild, then you really are screwed without a back-up, because there's nothing left to try to recover/rebuild.

Otherwise, this procedure usually fixes everything. If it doesn't... well, we'll think up some other tricks to try.

Good Luck,
V

marcrblevins
26th July 2008, 06:12 AM
Try:


su -
yum clean all
yum makecache
rpm --rebuilddb
yum repolist

Irmis
27th July 2008, 03:53 AM
Try:


su -
yum clean all
yum makecache
rpm --rebuilddb
yum repolist


I tried that but after makecache and repolist it returns both times:


Loaded plugins: refresh-packagekit
Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again

I guess I'll just have to find that DVD I made and reinstall, but this came up after the first update happened. Wonder if that means something.

Hlingler
27th July 2008, 04:05 AM
Or, you could try rebuilding the rpm database first as per the instructions on the rpm.org website. Your call.

Good Luck,
V

Irmis
27th July 2008, 05:02 AM
Or, you could try rebuilding the rpm database first as per the instructions on the rpm.org website. Your call.

Good Luck,
V

:( It didn't work. Wow I really slayed Fedora. I am invincible!! I've had to reinstall Ubuntu several times during my time with it. Seems I am consistent.

Hlingler
27th July 2008, 05:15 AM
LOL! :D

The design philosophy of Linux in general makes it really rather easy to wreck things, since there are few "fail-safes", cautions, warnings or such to tell you that you're about to do something... unwise. Most users seem to prefer this over some "other" OSs which seem to constantly "second-guess" almost every administrative action a user might take. The price is: often learning the hard way.

While I've managed not to ever have to re-install, I spend roughly 1/3 of my time fixing my mistakes, 1/3 of the time fixing the software's mistakes, and the other 1/3 using the system. OK, maybe that's an exaggeration, but you get the idea. :)

Good Luck,
V

Irmis
27th July 2008, 06:35 PM
Funny I spent all this time unknowingly using Fedora Core 10. There should be a label or something on here.Oh well none of the fixy stuff worked for the correct OS either.. I lost the first disk. Nautilus only returns an unknown error when I try to create another image disk and K3B didn't download.. Looks like I'll have to return to Kubuntu just to take another step forward. :eek: