Your message dated Wed, 25 Apr 2007 22:47:05 +0200 with message-id <20070425204705.GA32625@.madism.org> and subject line Bug#383457: nscd dies with SIGABRT with an enabled hosts cache 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 ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nscd dies with SIGABRT with an enabled hosts cache
- From: Daniel Vetter <daniel.vetter@ffwll.ch>
- Date: Thu, 17 Aug 2006 14:19:39 +0200
- Message-id: <20060817121939.19931.25002.reportbug@localhost.localdomain>
Package: nscd Version: 2.3.6-19 Severity: normal nscd dies on the first reload of a hosts cache entry. Disabling the hosts cache in nscd.conf works around the problem. Relevant parts of a strace output: # strace nscd --debug ... epoll_wait(11, {{EPOLLRDNORM, {u32=12, u64=12}}}, 100, 29976) = 1 epoll_ctl(11, EPOLL_CTL_DEL, 12, {0, {u32=0, u64=0}}) = 0 futex(0x55555566c524, FUTEX_WAKE, 1) = 1 epoll_wait(11, 19924: handle_request: request received (Version = 2) from PID 19931 19924: GETAI (bugs.debian.org) 19924: Haven't found "bugs.debian.org" in hosts cache! 19924: Reloading "1000" in password cache! 19924: Reloading "www.google-analytics.com" in hosts cache! nscd: hstcache.c:364: cache_addhst: Assertion `hst->h_addr_list[1] == ((void *)0)' failed. 7fff3aa53950, 100, 29988) = -1 EINTR (Interrupted system call) +++ killed by SIGABRT +++ Process 19924 detached I'm using nscd to cache user/group from the ldap server - but turning off the ldap service in nssswitch.conf didn't help in any way. If there's something else I can provide or test, I'd be glad to do so. /Daniel -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-fs1 Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8) Versions of packages nscd depends on: ii libc6 2.3.6.ds1-1 GNU C Library: Shared libraries nscd recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Daniel Vetter <daniel.vetter@ffwll.ch>, 383457-done@bugs.debian.org
- Subject: Re: Bug#383457: nscd dies with SIGABRT with an enabled hosts cache
- From: Pierre HABOUZIT <madcoder@debian.org>
- Date: Wed, 25 Apr 2007 22:47:05 +0200
- Message-id: <20070425204705.GA32625@.madism.org>
- In-reply-to: <20060817121939.19931.25002.reportbug@localhost.localdomain>
- References: <20060817121939.19931.25002.reportbug@localhost.localdomain>
On Thu, Aug 17, 2006 at 02:19:39PM +0200, Daniel Vetter wrote: > Package: nscd > Version: 2.3.6-19 > Severity: normal > > > nscd dies on the first reload of a hosts cache entry. Disabling the hosts cache > in nscd.conf works around the problem. Relevant parts of a strace output: > > # strace nscd --debug > > ... > > epoll_wait(11, {{EPOLLRDNORM, {u32=12, u64=12}}}, 100, 29976) = 1 > epoll_ctl(11, EPOLL_CTL_DEL, 12, {0, {u32=0, u64=0}}) = 0 > futex(0x55555566c524, FUTEX_WAKE, 1) = 1 > epoll_wait(11, 19924: handle_request: request received (Version = 2) from PID > 19931 > 19924: GETAI (bugs.debian.org) > 19924: Haven't found "bugs.debian.org" in hosts cache! > 19924: Reloading "1000" in password cache! > 19924: Reloading "www.google-analytics.com" in hosts cache! > nscd: hstcache.c:364: cache_addhst: Assertion `hst->h_addr_list[1] == ((void > *)0)' failed. > 7fff3aa53950, 100, 29988) = -1 EINTR (Interrupted system call) > +++ killed by SIGABRT +++ > Process 19924 detached > > I'm using nscd to cache user/group from the ldap server - but turning off the > ldap service in nssswitch.conf didn't help in any way. > > If there's something else I can provide or test, I'd be glad to do so. > > /Daniel this is because of a corrupted (or too old) hosts database. purge it using nscd -i hosts, or doing rm -f /var/db/nscd/hosts (I think there has been a format change in old libc's that we never dealt with, and it's too late for that) Cheers, -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.orgAttachment: pgp6IsOFnh3Xy.pgp
Description: PGP signature
--- End Message ---