Your message dated Wed, 9 Sep 2009 09:48:45 -0700
with message-id <20090909164845.ga17...@dario.dodds.net>
and subject line Re: Bug#545859: Fatal: not entropy gathering module detected
by /etc/init.d/slapd start
has caused the Debian Bug report #545859,
regarding Fatal: not entropy gathering module detected by /etc/init.d/slapd
start
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
545859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slapd
Version: 2.4.17-1
Severity: serious
Hello,
this worked a couple of weeks ago. I alread chmoded o+rw /dev/random, but this
has not helped.
$ ls -l /dev/random
crw-rw-rw- 1 root dialout 1, 8 9. Sep 11:36 /dev/random
$ sudo /etc/init.d/slapd start
Starting OpenLDAP: slapd - failed:
Fatal: no entropy gathering module detected
My hunch was that with my update of the sysv-rc bits something is no longer
detected/started that was started before.
Just while panicking around, /etc/init.d/urandom start does not make a
difference, the problem was
$ ls -l /dev/urandom
crw-rw---- 1 root dialout 1, 9 9. Sep 18:13 /dev/urandom
A chmod o+rw /dev/urandom fixed the problem, i.e. slapd then started.
I don't know what the problem is here. Somehow the group "dialout" for
/dev/urandom seems strange.
Cheers,
Steffen
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages slapd depends on:
ii adduser 3.110 add and remove users and groups
ii coreutils 7.5-1 GNU core utilities
ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libdb4.7 4.7.25-7 Berkeley v4.7 Database Libraries [
ii libgnutls26 2.8.3-2 the GNU TLS library - runtime libr
ii libldap-2.4-2 2.4.17-1 OpenLDAP libraries
ii libltdl7 2.2.6a-4 A system independent dlopen wrappe
ii libperl5.10 5.10.0-25 Shared Perl library
ii libsasl2-2 2.1.23.dfsg1-1.1 Cyrus SASL - authentication abstra
ii libslp1 1.2.1-7.6 OpenSLP libraries
ii libuuid1 2.16-3 Universally Unique ID library
ii libwrap0 7.6.q-18 Wietse Venema's TCP wrappers libra
ii perl [libmime-base64-pe 5.10.0-25 Larry Wall's Practical Extraction
ii psmisc 22.8-1 utilities that use the proc file s
ii unixodbc 2.2.11-20 ODBC tools libraries
Versions of packages slapd recommends:
ii libsasl2-modules 2.1.23.dfsg1-1.1 Cyrus SASL - pluggable authenticat
Versions of packages slapd suggests:
ii ldap-utils 2.4.17-1 OpenLDAP utilities
-- debconf information:
slapd/tlsciphersuite:
shared/organization: nodomain
slapd/upgrade_slapcat_failure:
slapd/backend: HDB
slapd/allow_ldap_v2: false
slapd/no_configuration: false
slapd/move_old_database: true
slapd/suffix_change: false
slapd/dump_database_destdir: /var/backups/slapd-VERSION
slapd/domain: nodomain
slapd/password_mismatch:
slapd/invalid_config: true
slapd/slurpd_obsolete:
slapd/dump_database: when needed
slapd/purge_database: false
--- End Message ---
--- Begin Message ---
On Wed, Sep 09, 2009 at 06:17:51PM +0200, Steffen Moeller wrote:
> this worked a couple of weeks ago. I alread chmoded o+rw /dev/random, but
> this has not helped.
> $ ls -l /dev/random
> crw-rw-rw- 1 root dialout 1, 8 9. Sep 11:36 /dev/random
> $ sudo /etc/init.d/slapd start
> Starting OpenLDAP: slapd - failed:
> Fatal: no entropy gathering module detected
> My hunch was that with my update of the sysv-rc bits something is no
> longer detected/started that was started before.
> Just while panicking around, /etc/init.d/urandom start does not make a
> difference, the problem was
> $ ls -l /dev/urandom
> crw-rw---- 1 root dialout 1, 9 9. Sep 18:13 /dev/urandom
> A chmod o+rw /dev/urandom fixed the problem, i.e. slapd then started.
> I don't know what the problem is here. Somehow the group "dialout" for
> /dev/urandom seems strange.
Yes, it is strange (and wrong). But the bug doesn't lie with slapd;
something else broke your /dev/urandom.
Closing this bug, since I have no idea where to reassign it. Feel free to
reopen / reassign if you can figure out which package broke your device.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
--- End Message ---