« RPM : Récupérer la base de données » : différence entre les versions
m Adadov a déplacé la page Récupérer la base de données RPM vers RPM : Récupérer la base de données |
Aucun résumé des modifications |
||
| Ligne 7 : | Ligne 7 : | ||
If an RPM command hangs, segfaults, or otherwise behaves abnormally during use then the first task is to check for stale lock files. This can be accomplished with -CA option to the rpmdb_stat command: | If an RPM command hangs, segfaults, or otherwise behaves abnormally during use then the first task is to check for stale lock files. This can be accomplished with -CA option to the rpmdb_stat command: | ||
{{LxTerm|user=root|cd /var/lib/rpm | |||
/usr/lib/rpm/rpmdb_stat -CA}} | |||
Look at the output under the sections headed 'Locks grouped by lockers' and 'Locks grouped by object'. If no RPM command is executing, then there should be no entries. The RPM DB format allows many processes to be concurrently reading *AND* writing to the DB, so there is no safe way for an RPM command to identify & remove a stale lock. Stale locks are typically a result of a process being killed in an abnormal manner (power loss, kernel crash, 'kill' from an impatient admin). The locks are maintained in a handful of files named with two initial underscores. | Look at the output under the sections headed 'Locks grouped by lockers' and 'Locks grouped by object'. If no RPM command is executing, then there should be no entries. The RPM DB format allows many processes to be concurrently reading *AND* writing to the DB, so there is no safe way for an RPM command to identify & remove a stale lock. Stale locks are typically a result of a process being killed in an abnormal manner (power loss, kernel crash, 'kill' from an impatient admin). The locks are maintained in a handful of files named with two initial underscores. | ||
| Ligne 14 : | Ligne 14 : | ||
Since there is generally no 100% reliable way to determine if an arbitrary application has a lock on the RPM db, the best time at which to clear the stale locks is while in single user mode. Thus to clean up stale lock files, the best course of action is to simply reboot the machine. If for some reason, it is not feasible to reboot the machine, then it is feasible to simply delete the files manually. Before doing this, one must ensure no application has any of the RPM database files open. This can be checked with the lsof command. For example, as root, ensure the following command shows no lines of output: | Since there is generally no 100% reliable way to determine if an arbitrary application has a lock on the RPM db, the best time at which to clear the stale locks is while in single user mode. Thus to clean up stale lock files, the best course of action is to simply reboot the machine. If for some reason, it is not feasible to reboot the machine, then it is feasible to simply delete the files manually. Before doing this, one must ensure no application has any of the RPM database files open. This can be checked with the lsof command. For example, as root, ensure the following command shows no lines of output: | ||
{{LxTerm|user=root|lsof | grep /var/lib/rpm}} | |||
== DB corruption recovery process == | == DB corruption recovery process == | ||
| Ligne 20 : | Ligne 20 : | ||
If after cleaning up stale lock files, problems are still experianced, then it is likely some level of database corruption is present. The file that usually requires rebuilding is master package metadata file /var/lib/rpm/Packages, and following that the indexes will also need to be re-generated. Before doing any potentially destructive action *ALWAYS* take a backup of the RPM DB. | If after cleaning up stale lock files, problems are still experianced, then it is likely some level of database corruption is present. The file that usually requires rebuilding is master package metadata file /var/lib/rpm/Packages, and following that the indexes will also need to be re-generated. Before doing any potentially destructive action *ALWAYS* take a backup of the RPM DB. | ||
{{LxTerm|user=root|cd /var/lib | |||
tar zcvf /var/preserve/rpmdb-`date +"%d%m%Y"`.tar.gz rpm}} | |||
Now verify the integrity of the Packages file: | Now verify the integrity of the Packages file: | ||
{{LxTerm|user=root|cd /var/lib/rpm | |||
rm -f __db* # to avoid stale locks | |||
/usr/lib/rpm/rpmdb_verify Packages}} | |||
If this reports any errors then a dump and load of the DB is required. After dumping, verify the integrity of the newly loaded Packages file: | If this reports any errors then a dump and load of the DB is required. After dumping, verify the integrity of the newly loaded Packages file: | ||
{{LxTerm|user=root|mv Packages Packages.orig | |||
/usr/lib/rpm/rpmdb_dump Packages.orig | /usr/lib/rpm/rpmdb_load Packages | |||
/usr/lib/rpm/rpmdb_verify Packages}} | |||
If the Packages file now passes the verify step, then as an additional sanity check query all headers in the DB by doing, and watch for any messages sent to standard error (it helps to discard standard out when looking for this): | If the Packages file now passes the verify step, then as an additional sanity check query all headers in the DB by doing, and watch for any messages sent to standard error (it helps to discard standard out when looking for this): | ||
{{LxTerm|user=root|rpm -qa 1> /dev/null}} | |||
If this query passes without generating any messages to standard error, then it is time to rebuild the indexes by invoking: | If this query passes without generating any messages to standard error, then it is time to rebuild the indexes by invoking: | ||
{{LxTerm|user=root|rpm -v --rebuilddb}} | |||
At this point you should have a functioning RPM database again. If any of the recovery steps failed, then a bug should be reported. When creating the report, provide the tar.gz backup of the RPM DB as an attachment, along with any daily package list log files named /var/log/rpm*. | At this point you should have a functioning RPM database again. If any of the recovery steps failed, then a bug should be reported. When creating the report, provide the tar.gz backup of the RPM DB as an attachment, along with any daily package list log files named /var/log/rpm*. | ||
Version du 14 août 2018 à 12:19
 |
| Le présent article est actuellement en cours de rédaction ou de modification. Adressez-vous à la personne en charge pour toute proposition ou modification. |
| Auteur / Editeur : Adadov |
| Dernière édition : 14/08/2018 |
This document provides an overview of how to deal with RPM database corruption.
Removing stale locks
If an RPM command hangs, segfaults, or otherwise behaves abnormally during use then the first task is to check for stale lock files. This can be accomplished with -CA option to the rpmdb_stat command:
| [root@linux] # | cd /var/lib/rpm | dblclick to copy |
| [root@linux] # | /usr/lib/rpm/rpmdb_stat -CA | |
Look at the output under the sections headed 'Locks grouped by lockers' and 'Locks grouped by object'. If no RPM command is executing, then there should be no entries. The RPM DB format allows many processes to be concurrently reading *AND* writing to the DB, so there is no safe way for an RPM command to identify & remove a stale lock. Stale locks are typically a result of a process being killed in an abnormal manner (power loss, kernel crash, 'kill' from an impatient admin). The locks are maintained in a handful of files named with two initial underscores.
Since there is generally no 100% reliable way to determine if an arbitrary application has a lock on the RPM db, the best time at which to clear the stale locks is while in single user mode. Thus to clean up stale lock files, the best course of action is to simply reboot the machine. If for some reason, it is not feasible to reboot the machine, then it is feasible to simply delete the files manually. Before doing this, one must ensure no application has any of the RPM database files open. This can be checked with the lsof command. For example, as root, ensure the following command shows no lines of output:
| [root@linux] # | lsof | dblclick to copy |
DB corruption recovery process
If after cleaning up stale lock files, problems are still experianced, then it is likely some level of database corruption is present. The file that usually requires rebuilding is master package metadata file /var/lib/rpm/Packages, and following that the indexes will also need to be re-generated. Before doing any potentially destructive action *ALWAYS* take a backup of the RPM DB.
| [root@linux] # | cd /var/lib | dblclick to copy |
| [root@linux] # | tar zcvf /var/preserve/rpmdb-`date +"%d%m%Y"`.tar.gz rpm | |
Now verify the integrity of the Packages file:
| [root@linux] # | cd /var/lib/rpm | dblclick to copy |
| [root@linux] # | rm -f __db* # to avoid stale locks | |
| [root@linux] # | /usr/lib/rpm/rpmdb_verify Packages | |
If this reports any errors then a dump and load of the DB is required. After dumping, verify the integrity of the newly loaded Packages file:
| [root@linux] # | mv Packages Packages.orig | dblclick to copy |
| [root@linux] # | /usr/lib/rpm/rpmdb_dump Packages.orig | |
If the Packages file now passes the verify step, then as an additional sanity check query all headers in the DB by doing, and watch for any messages sent to standard error (it helps to discard standard out when looking for this):
| [root@linux] # | rpm -qa 1> /dev/null | dblclick to copy |
If this query passes without generating any messages to standard error, then it is time to rebuild the indexes by invoking:
| [root@linux] # | rpm -v --rebuilddb | dblclick to copy |
At this point you should have a functioning RPM database again. If any of the recovery steps failed, then a bug should be reported. When creating the report, provide the tar.gz backup of the RPM DB as an attachment, along with any daily package list log files named /var/log/rpm*.