Bug 72384 - rpm --i segfaults
Summary: rpm --i segfaults
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: rpm
Version: null
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-23 11:35 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-23 11:35:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-08-23 11:35:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
rpm install of any package segfaults when nscd (name server caching daemon) is
installed but not running.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.install and/or stop nscd
2.try to install another package
3.watch rpm segfault
	

Actual Results:  rpm dies with segfault whilst installing a package

Expected Results:  rpm installs a package

Additional info:

socket(PF_UNIX, SOCK_STREAM, 0)         = 8
connect(8, {sin_family=AF_UNIX, path="/var/run/.nscd_socket"}, 110) = -1 ENOENT
(No such file or directory)
close(8)                                = 0
open("/etc/nsswitch.conf", O_RDONLY)    = 8
fstat64(8, {st_mode=S_IFREG|0644, st_size=1784, ...}) = 0
mmap2(NULL, 1784, PROT_READ, MAP_SHARED, 8, 0) = 0x40407000
_llseek(8, 1784, [1784], SEEK_SET)      = 0
fstat64(8, {st_mode=S_IFREG|0644, st_size=1784, ...}) = 0
munmap(0x40407000, 1784)                = 0
close(8)                                = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

Comment 1 Jeff Johnson 2002-08-23 12:55:19 UTC
Hmmm, are you using LDAP passwords? If so,
then you need to start nscd in order to avoid
a linkage problem in PAM that affects statically
linked binaries like rpm.

Please reopen this bug if LDAP was not the problem.


Note You need to log in before you can comment on or make changes to this bug.