Bug 97589
Summary: | segfault when dependencies are met | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David Curtiss <bugzilla> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-29 13:14:02 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
David Curtiss
2003-06-18 01:33:18 UTC
Sanity check: Are you using LDAP passwords? If so than you need to insure that nscd is running (won't hurt no matter what) bash# service nscd start openldap is installed, but I don't know if we are using LDAP passwords. The main component we have that has a dependency on LDAP is sendmail, but I checked out sendmail's configuration file and the only line that refers to LDAP is commented out. If it takes a special effort to switch to using LDAP passwords, then chances are we aren't. Is there a way to find out? Running `/sbin/service nscd start` failed the first time I ran it. Running it again did't say whether it failed or succeeded. Stopping it failed every time. Trying again to start it still didn't say whether it failed or succeeded. Running `/sbin/service nscd status` says "nscd dead but pid file exists". After a reboot, nscd status is "stopped", starting nscd says "OK", but then nscd status becomes "dead but pid file exists", and rpm is still segfaulting. After that, nscd start still doesn't say whether it fails or succeeds, and nscd stop still fails. Can you provide a pointer (i.e. URL, attachments won't work) to the tarbball of your database? Sorry for the delayed response. You can get the tarball at http://www.dereinherjar.com/rpmdb.tar.gz Hmmm, nscd failing to start is not a good sign. I don't see anything wrong with your database, have done --rebuilddb just in case. Your rpm/Packages is at ftp://people.redhat.com/jbj/rpmdb-97589-FIX.tar.gz. Download and install by doing cd /var/lib mv rpm/Packages rpm/Packages-ORIG tar xzvf rpmdb-97589-FIX.tar.gz rpm --rebuilddb -vv Reopen this bug if the above doesn't fix. No luck. Running `rpm --rebuilddb -vv` still segfaults. Also tried rebooting and running it again; still segfaulted. I did some test runs trying to install different things with the updated database. It seems to be letting some packages through easier, and segfaults in some cases where it used to say I had dependencies to resolve. However, I can still get it to complain about package dependencies and not segfault (although nothing gets installed, of course). Does the database show any rpm/glibc/kernel incompatibility? i.e. could it be an NPTL transition issue? That still seems to be the most likely case to me, since we started with a previous installation of RedHat, and upgraded several packages to their RedHat 9 versions. I can't guess at incompatibilities. rpm is known to "work" (i.e. not segfault) with released versions of glibc/kernel. Mixing and matching versions of glibc/kernel/rpm is not advised because of NPTL. Or install rpm-4.1.1 from ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x which doesn't use posix mutexes (i.e. no NPTL). |