[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#345168: marked as done (Sarge version of nscd is completely broken (Fails to cache any entry))

Your message dated Mon, 5 Feb 2007 18:04:51 +0100
with message-id <20070205170451.GA23615@mad.intersec.eu>
and subject line nscd in sarge creates sockets in wrong location
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: nscd
Version: 2.3.2.ds1-22
Severity: critical
Justification: breaks unrelated software


I'm using nscd (sarge version) with LDAP, and it is .... not working.

Attaching to it with strace -p $PID shows no activity while doing a
simple ls -al /home with a few directories in /home, making constant
LDAP lookups.

Upgrading nscd to the one in sid solves the problem......



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.15-rc7-dell520
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to fr_FR@euro)

Versions of packages nscd depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, Apr 27, 2006 at 08:31:08AM -0400, Jesse W. Hathaway wrote:
> # apt-get install nscd
> # ps -ef|grep nscd
> root      4603     1  0 08:25 ?        00:00:00 /usr/sbin/nscd
> root      4620  4418  0 08:27 pts/3    00:00:00 grep nscd
> 
> strace ping -c 1 www.google.com > /tmp/strace 2>&1
> 
> relevant portion of /tmp/strace:
> 
> connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> close(4)                                = 0
> socket(PF_FILE, SOCK_STREAM, 0)         = 4
> fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
> fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
> connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> close(4)                                = 0
> 
> nscd socket is created at /var/run/.nscd_socket rather
> than /var/run/nscd/socket
> 
> creating a symlink at /var/run/nscd/socket to /var/run/.nscd_socket
> resolves the problem
> 
> this issue is resolved in unstable, it should either be fixed 
> in stable or noted during the installation

  well, except that in my setup, when I do exactly the same as what you
do my strace has:

  connect(4, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = 0

  which obviously works. I suppose you have something unclean in your
environment somwhere, and there is absolutely nothing related to nscd
that changed since 2.3.2.ds1-22 until the -22sarge4 I tested.

  Moreover, looking at the libc sources, there is absolutely _no_
reference to a /var/run/nscd/socket whereas you find:
  nscd/nscd-client.h:35:#define _PATH_NSCDSOCKET "/var/run/.nscd_socket"

  That header beeing private, there is absolutely no chance anyone could
have built against an older version. To me it looks like you have a
"thing" on your system that is not up to date in your sarge. Given that
nss modules are often used through dlopen's I suppose that the problem
is that some things on your machine may have remained linked against an
earlier version of that or this nss module.

  E.g. you should check that if you have a libc6-$(arch) module that
module has been upgraded as well, and that you restarted every service
using the libc, your shell included.

  As nobody has followuped to that bug for more than a year, I'm closing
the bug.

  please mail control@bugs.debian.org with the stanza:
--8<-----
reopen 345168
thanks
-->8-----

  if you still have the problem.

Cheers,
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgppuFoQxRTI0.pgp
Description: PGP signature


--- End Message ---
Reply to: