Skip to content
This repository was archived by the owner on Oct 22, 2019. It is now read-only.
This repository was archived by the owner on Oct 22, 2019. It is now read-only.

LDAP Server: Stray Process Prevents Restart #22

@solaris007

Description

@solaris007

on Debian 7.1 / puppet standalone v3.3.0, puppet applying the following manifest:

class { 'ldap::server::master':
  suffix      => 'dc=sample,dc=example,dc=com',
  rootpw      => '{SSHA}pWaJbwn761ZvaPRJtLjmxGshy5ZL6svQmR',
  ssl         => true,
  ssl_ca      => 'ca.pem',
  ssl_cert    => 'ldap-server.pem',
  ssl_key     => 'ldap-server.key',
}

causes errors in the installation:

Debug: Executing '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install slapd'
Nov 13 20:15:30 oculist slapd[20332]: @(#) $OpenLDAP: slapd  (Apr 23 2013 12:16:04) $#012#011root@lupin:/tmp/buildd/openldap-2.4.31/debian/build/servers/slapd
Nov 13 20:15:30 oculist slapd[20333]: slapd starting
Notice: /Stage[main]/Ldap::Server::Master/Package[slapd]/ensure: ensure changed 'purged' to 'present'
Debug: /Stage[main]/Ldap::Server::Master/Package[slapd]: The container Class[Ldap::Server::Master] will propagate my refresh event
Notice: /Stage[main]/Ldap::Server::Master/File[/etc/ldap/slapd.conf]/ensure: created
Info: /Stage[main]/Ldap::Server::Master/File[/etc/ldap/slapd.conf]: Scheduling refresh of Service[slapd]
Debug: /Stage[main]/Ldap::Server::Master/File[/etc/ldap/slapd.conf]: The container Class[Ldap::Server::Master] will propagate my refresh event
Debug: Finishing transaction 29705600
Info: FileBucket got a duplicate file {md5}db241334782551b92b24f9313d85893a
Info: /Stage[main]/Ldap::Server::Debian/File[/etc/default/slapd]: Filebucketed /etc/default/slapd to puppet with sum db241334782551b92b24f9313d85893a
Notice: /Stage[main]/Ldap::Server::Debian/File[/etc/default/slapd]/content: content changed '{md5}db241334782551b92b24f9313d85893a' to '{md5}5541a553ccce1a1c593f20e7283b4faf'
Info: /Stage[main]/Ldap::Server::Debian/File[/etc/default/slapd]: Scheduling refresh of Service[slapd]
Debug: /Stage[main]/Ldap::Server::Debian/File[/etc/default/slapd]: The container Class[Ldap::Server::Debian] will propagate my refresh event
Debug: Class[Ldap::Server::Debian]: The container Stage[main] will propagate my refresh event
Debug: Executing '/etc/init.d/slapd status'
Debug: Executing '/etc/init.d/slapd start'
Nov 13 20:15:30 oculist slapd[20373]: @(#) $OpenLDAP: slapd  (Apr 23 2013 12:16:04) $#012#011root@lupin:/tmp/buildd/openldap-2.4.31/debian/build/servers/slapd
Nov 13 20:15:30 oculist slapd[20373]: daemon: bind(8) failed errno=98 (Address already in use)
Nov 13 20:15:30 oculist slapd[20373]: daemon: bind(8) failed errno=98 (Address already in use)
Nov 13 20:15:30 oculist slapd[20373]: slapd stopped.
Nov 13 20:15:30 oculist slapd[20373]: connections_destroy: nothing to destroy.
Error: Could not start Service[slapd]: Execution of '/etc/init.d/slapd start' returned 1:
Error: /Stage[main]/Ldap::Server::Master/Service[slapd]/ensure: change from stopped to running failed: Could not start Service[slapd]: Execution of '/etc/init.d/slapd start' returned 1:

it seems that after ensuring the slapd package is installed, slapd is started up. apparently the module tries to start up slapd again, which results in a "address in use" problem.

doing a "service restart slapd" fails.
*ps -fu openldap" shows a running slapd.
after "kill " the restart works fine.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions