The command "spacewalk-data-fsck --remove" prints "File path mismatch" and "File missing in db" messages

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

Environment

SUSE Manager 4.3

Situation

When executing the command "spacewalk-data-fsck --remove" to cleanup redundant database entries, the command prints the following messages, for example:

.log('File missing in db: /var/spacewalk/packages/1/stage/644fb97daaa2c690cc70f7d6348e3a1776345cb5655889e81ac52014502ed480/thunderbird-locale-fy_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb',)
File path mismatch: /var/spacewalk/packages/NULL/0b7/go1.20/1.20.7-150000.1.20.1/x86_64/0b74ae9ec8ca37451976b05847707e25cbaf922c7edf579bf78de6c7b01e9480/go1.20-1.20.7-150000.1.20.1.x86_64.rpm (org_id: 1 vs. NULL)

Reposync at some point in time reported out of space errors (/var/log/rhn/reposync/<channel>.log):

"OSError: [Errno 28] No space left on device:"

Resolution

Execute the following commands:

spacewalk-data-fsck --remove

Resolves files downloaded but not stored in the Database (DB) or linked to a channel, resulting in "File is missing in db" messages. This can possibly free up some space.

spacewalk-data-fsck -F

Resolves the path mismatch messages, but will leave the related RPMs in the database.

spacecmd package_removeorphans

Which will remove all orphaned RPMs from the database.

Cause

Orphaned RPMs and inconsistent database entries, likely caused by the server (at some point) running out of disk space during reposync.

Note: This likely has no impact on SUSE Managers functionality. The main impact is orphaned packages that will likely consume some additional memory.

Additional Information

Running out of disk space can result in reposync not being able to link the packages to the correct channels, which can cause the following potential issues:

- Package is downloaded, but not placed into the database at all - this is signified by "File is missing in DB" errors.
- Package is downloaded and placed into the database, but not linked to any channels.

In the above cases, the vendor packages will have their org set to NULL (and so use the path with "NULL").

There however is a Taskomatic job, that periodically modifies packages with "NULL" org to "org_id=1". This means that the package's "org_id" and its path do not match anymore.

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.