Bug 90957
Summary: | rpm --rebuilddb doew not work | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Irina Kaliman <irina> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 9 | CC: | barryn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-05-22 00:13:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Irina Kaliman
2003-05-15 19:20:43 UTC
This is a dupe of I-don't-know-how-many other bugs. It's a harmless error, just ignore it. Yup. Error message is harmless, ignore, as it says in countless other reports. HOw could this bug be harmless if I do not get a prompt back??? How do I know if rpm databased was rebuilt or not? [root@potomac irina]# rpm --rebuilddb No prompt back! ^C does not work, window is frozen! NO way it is a hramless bug Irina Kaliman, System and Network Administrator University of Miami, Computer Science department In that situation, use another terminal (for example, another ssh session or another X terminal window) to run "top" and see if rpm --rebuilddb is using tons of CPU time. If it's using lots of CPU it's almost certainly rebuilding the database. If it's not using CPU time but it's not returning to the prompt either, then that's a problem. The "harmless bug" is the db4 error that gets displayed. That error should appear very near the end of the rebuild, and the prompt should then come back almost immediately after the error (or at least within several seconds of the error). Are you saying that you don't get the prompt back after the db4 error shows up? That would be a different problem or bug than the "harmless" one Jeff and I are talking about. |