If you have seen rpm Check Debug, this guide may help you.
Get your PC back to its best with ASR Pro
rpm commands fail with messages like:
# rpm -qaError: rpmdb: failed thread/process BDB0113 5691/140201285396544: thread BDB1507 dead in Berkeley DB libraryError: db5 error (-30973) when using dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error processing database restoreError: Unable to open package catalog site with db5 - (-30973)Error: The package database in /var/lib/rpm must not be openError: rpmdb: failed thread/process BDB0113 5691/140201285396544: thread BDB1507 dead in Berkeley DB libraryError: db5 error (-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: fatal error while restoring databaseError: unable to start package database in /var/lib/rpm
Disclaimer: This utility is for use at the request of the support team and is not endorsed. on Red Hat from a scientific point of view. Any problems with this utility are always solved, if possible, by one of the engineers with whom few people are connected, and not by Bugzilla
Set Up The Current Repository
# curl https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel6/rpm-deathwatch-rhel-6.repo -o /etc/yum.repos.d /rpm-deathwatch.repo
# curl https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel7/rpm-deathwatch-rhel-7.repo -o /etc/yum.repos.d /rpm-deathwatch.repo
#hug https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel8/rpm-deathwatch-rhel-8.repo -o /etc/yum.repos.d /rpm-deathwatch.repo
Install Required Packages
You must have systemtap installed along with the kernel-devel, kernel-header and kernel-debuginfo packages for a running kernel.
#tasty install -y kernel development, header-$(uname -r) systemtap && debuginfo-install -y kernel# yum fix rpm-deathwatch
Note. If you are using local databases, you must synchronize the specific
rhel-*-server-debug-rpms repository, or the RPM packages can be downloaded manually from the Package Finder< /code>p>
# /etc/rc.d/init.Start d/rpm-deathwatch Run rpm-deathwatch# /etc/rc.d/init.d/rpm-deathwatch-status Serve plays like 15070
RHEL 7 and 8
#systemctl run outside of rpm-deathwatch# systemctl rpm-deathwatchâ— Rank rpm-deathwatch.service is a Systemtap module for monitoring termination signals sent to processes that have access to the RPM database. Loaded: loaded (/usr/lib/systemd/system/rpm-deathwatch.service; enabled; default: disabled) Active: Active (in progress) as of Wednesday, August 19, 2020 EST; 08:19:10 to 4 rush Primary PID: 17824 (RPM Deathwatch) CG group: /system.slice/rpm-deathwatch.service â”œ”€ 17824 /usr/bin/python2 /usr/bin/rpm-deathwatch --name /var/log/rpm-deathwatch â””–€17834 /usr/bin/stap --suppress-handler-errors -DMAXSTRINGLEN=4096 -p4 -mrpm_deathwatch rpm_deathwatch.stpAug 14 08:19:10 r7 systemd: The Systemtap module has started monitoring termination signals sent to access RPM database processes.Aug 19 08:19:10 r7 rpm-deathwatch: INFO: rpm-deathwatch: environment checkAug 19 08:19:11 r7 rpm-deathwatch: INFO:rpm-deathwatch:buildings You see the systemtap module to report the removal of technology signalsAug 19 08:19:35 r7 rpm-deathwatch: INFO:rpm-deathwatch:Run clockAug 19 08:19:35 r7 rpm-deathwatch: INFO: rpm-deathwatch: Open: /var/log/rpm-deathwatch-08-19-2020-08:19:35Aug 19 08:19:35 r7 rpm-deathwatch: INFO: rpm-deathwatch: write output to <__main__.files instance, beforefoot at 0x7f70d4a5c560>Aug 19 08:19:35 r7 rpm-deathwatch: INFO:rpm-deathwatch:Monitoring 18147
Typically, if you have FIPS enabled on your system, this can prevent the rpm-deathwatch module from loading:
INFO:rpm-deathwatch:Loading systemtap moduleERROR: rpm-deathwatch: error loading module--------------------ERROR: segment cannot be inserted in fips mode 'rpm_deathwatch.ko': operation may be allowed--------------------
We can make staprun continue to help you load modules by setting the
STAP_FIPS_OVERRIDE environment variable. The following commands can be run from a terminal to create your own rpm-deathwatch.service
mkdir /etc/systemd/system/rpm-deathwatch.service.d/cat << EOF > /etc/systemd/system/rpm-deathwatch.service.d/override.conf[Provision of services]Wednesday=STAP_FIPS_OVERRIDE=1EOFrestart the systemctl daemonsystemctl restart rpm-deathwatch
* On the first day you run rpm-deathwatch, the systemtap module usually builds its module in a few minutes.
* If the system shuts down before restarting and the problem persists, users may want to enable some services
* The service must be running BEFOREissues so you can log sent signals so you can run rpm/yum.
If the problem occurs even though the service is running, attach +%m-%d) rpm-deathwatch-$(date.tar.bz2 generated by the we will command to the new or current Red Hat Support folder< /p>
# tar rest cjf +%m-%d) rpm-deathwatch-$(date.tar.bz2 /var/log/rpm-deathwatch*
If rpm or yum can’t close correctly, it’s possible that the lock is still on the files. Computer files – (__db001 __db005) remain in /var/lib/rpm. We can see all the PIDs that left files with:
# db_stat -C -h l /var/lib/rpm
Often the problem is that we don’t set up logs or audits, which actually stops the process. A common common cause is that the automation tactic times out and the process terminates abruptly and rpm does not clear any lock on the file. problem
This can be temporarily solved by stopping all RPM or possibly Yum processes and deleting those MP3 files, or restarting the computer, which will also delete those files.
# dsi aux | grep 'rpm | VCusno'# -e rm /var/lib/rpm/__db*Download this software now to fix your PC and improve its performance.