SUSE Support

Here When You Need Us

Sync of channels finishes with the message "DB_PAGE_NOTFOUND: Requested page not found"

This document (000020422) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.1 Server
SUSE Manager 4.2 Server

 

Situation

Sync of product channels on top of SUSE Manager Server finishes with following messages:
spacewalk-repo-sync --channel sle-product-sles15-sp3-pool-x86_64   
14:11:59 ======================================
14:11:59 | Channel: sle-product-sles15-sp3-pool-x86_64
14:11:59 ======================================
14:11:59 Sync of channel started.
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "gpg-pubkey" records from Name index: DB_PAGE_NOTFOUND: Requested page not found
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "gpg-pubkey" records from Name index: DB_PAGE_NOTFOUND: Requested page not found
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "gpg-pubkey" records from Name index: DB_PAGE_NOTFOUND: Requested page not found
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "gpg-pubkey" records from Name index: DB_PAGE_NOTFOUND: Requested page not found
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "Public Keys" records from Group index: DB_PAGE_NOTFOUND: Requested page not found
error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30986) getting "gpg(SuSE Package Signing Key <build@suse.de>)" records from Providename index: DB_PAGE_NOTFOUND: Requested page not found

There is an option to accept the key to be trusted. When the option "always" is selected, the key is not properly imported and the error message persists.

Resolution

Option 1: Repairing the custom RPM DB:

1. Run a backup of the "/var/lib/spacewalk/reposync/root/var/lib/rpm/" directory
2. Install "db48-utils" package
3. Run:
# db_verify /var/lib/spacewalk/reposync/root/var/lib/rpm/Packages
# rpm --rebuilddb --dbpath /var/lib/spacewalk/reposync/root/var/lib/rpm/
 4. Run "spacewalk-repo-sync" again and check if the issue reoccurs

Option 2: Remove the custom RPM DB:

NOTE: this will remove any GPG key that was manually accepted for a custom/3rd party repositories. Keys would need to be accepted manually again:

1. Remove the content in "/var/lib/spacewalk/reposync/root/var/lib/rpm/"
2. Re-run "spacewalk-repo-sync"

Cause

Corrupted custom RPM database. It may happen when filesystem runs out of the disk space.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000020422
  • Creation Date: 01-Nov-2021
  • Modified Date:01-Nov-2021
    • SUSE Manager Server
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.