CentOS - Apr 2015 - [SOLVED] Re: CentOS 6.6 x86_64, rpm error: rpmdbNextIterator: skipping h# ...

Hi All,

I had some health issues for a few months and I barely recall dealing
with Heartbleed ... it's all just a blur. Now I'm getting back up to
speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL
servers which no longer seem to be picking up available updates.

'yum check' ran for about 25 minutes this evening on one of them and
returned nothing useful.

rpm -qa --last is returning this (lines intentionally split):

error: rpmdbNextIterator: skipping h#     259 Header V3 RSA/SHA256 \
Signature, key ID c105b9de: BAD

error: rpmdbNextIterator: skipping h#       4 Header V3 RSA/SHA256 \
Signature, key ID c105b9de: BAD

error: rpmdbNextIterator: skipping h#    1028 Header V3 RSA/SHA1 \
Signature, key ID c105b9de: BAD

- - - - 8< snipped for brevity, continuing to end - - - - ->8 - - - -

error: rpmdbNextIterator: skipping h#    1019 Header V3 RSA/SHA1 \
Signature, key ID c105b9de: BAD

gpg-pubkey-fe837f6f-4e0fd77e            Thu 17 Jul 2014 12:00:11 AM EDT
gpg-pubkey-ef1d6db8-4e0fd7f0            Thu 17 Jul 2014 12:00:11 AM EDT
gpg-pubkey-d0ff3d16-4e0fd442            Thu 17 Jul 2014 12:00:11 AM EDT
gpg-pubkey-a0bdbcf9-42d1d837            Thu 17 Jul 2014 12:00:11 AM EDT
gpg-pubkey-11f63c51-3c7dc11d            Thu 17 Jul 2014 12:00:11 AM EDT
gpg-pubkey-c105b9de-4e0fd3a3            Tue 15 Jul 2014 02:32:15 AM EDT
gpg-pubkey-0608b895-4bd22942            Mon 14 Jul 2014 07:59:25 PM EDT
gpg-pubkey-6b8d79e6-3f49313d            Mon 14 Jul 2014 07:57:56 PM EDT

I'd be extremely grateful for any guidance or ideas you may wish to
share.

TIA & regards,

Carl

Hi,


On Tue, Apr 28, 2015 at 10:37 AM, <carlh04426 at gmail.com> wrote:
> Hi All,
>
> I had some health issues for a few months and I barely recall dealing
> with Heartbleed ... it's all just a blur. Now I'm getting back up
to
> speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL
> servers which no longer seem to be picking up available updates.
>
> 'yum check' ran for about 25 minutes this evening on one of them
and
> returned nothing useful.
>
> rpm -qa --last is returning this (lines intentionally split):
>
> error: rpmdbNextIterator: skipping h#     259 Header V3 RSA/SHA256 \
> Signature, key ID c105b9de: BAD
>
> error: rpmdbNextIterator: skipping h#       4 Header V3 RSA/SHA256 \
> Signature, key ID c105b9de: BAD
>
> error: rpmdbNextIterator: skipping h#    1028 Header V3 RSA/SHA1 \
> Signature, key ID c105b9de: BAD
>
> - - - - 8< snipped for brevity, continuing to end - - - - ->8 - - - -
>
> error: rpmdbNextIterator: skipping h#    1019 Header V3 RSA/SHA1 \
> Signature, key ID c105b9de: BAD
>
> gpg-pubkey-fe837f6f-4e0fd77e            Thu 17 Jul 2014 12:00:11 AM EDT
> gpg-pubkey-ef1d6db8-4e0fd7f0            Thu 17 Jul 2014 12:00:11 AM EDT
> gpg-pubkey-d0ff3d16-4e0fd442            Thu 17 Jul 2014 12:00:11 AM EDT
> gpg-pubkey-a0bdbcf9-42d1d837            Thu 17 Jul 2014 12:00:11 AM EDT
> gpg-pubkey-11f63c51-3c7dc11d            Thu 17 Jul 2014 12:00:11 AM EDT
> gpg-pubkey-c105b9de-4e0fd3a3            Tue 15 Jul 2014 02:32:15 AM EDT
> gpg-pubkey-0608b895-4bd22942            Mon 14 Jul 2014 07:59:25 PM EDT
> gpg-pubkey-6b8d79e6-3f49313d            Mon 14 Jul 2014 07:57:56 PM EDT
>
> I'd be extremely grateful for any guidance or ideas you may wish to
> share.
>
have you tried to rebuild the RPM database using below command,

# rpm --rebuilddb


--Regards
Ashishkumar S. Yadav

On Tue, 28 Apr 2015 10:47:32 +0530
Ashish Yadav wrote:
> have you tried to rebuild the RPM database using below command,
> 
> # rpm --rebuilddb
Hi Ashish, and thank you for your reply. I contemplated doing that but
felt I needed to better understand the problem, first. As it happens, I
refined my search phrase a few more times and ultimately discovered the
problem ... and the fix:

<http://kiteplans.info/2015/01/15/solved-bug-centos-yum-rpm-broken-by-nss-softokn-3-14-3-19-el6_6-update-error-rpmts_hdrfromfdno-error-rpmdbnextiterator-header-v3-rsasha1-signature-key-id-bad/>

Both servers are behaving properly now. Thanks again for your kind
reply & regards,

Carl