Bug 5605 - Ldap wont start
Summary: Ldap wont start
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Daniel Lucio
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-25 10:44 CEST by Andres Kaaber
Modified: 2012-07-09 17:11 CEST (History)
1 user (show)

See Also:
Source RPM: openldap
CVE:
Status comment:


Attachments

Description Andres Kaaber 2012-04-25 10:44:13 CEST
After installing openldap-servers ldap wont start
2/3: openldap-servers      ########################################################################################
Stopping ldap (via systemctl):                                  [  OK   ]
awk: cmd. line:1: warning: regexp component `[:space:]' should probably be `[[:space:]]'
Starting ldap (via systemctl):  Failed to issue method call: Unit ldap.service failed to load: No such file or directory. See system logs and 'systemctl status ldap.service' for details.
                                                                [FAILED]
ldap.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig ldap on

[root@web ~]# systemctl status ldap.service
ldap.service - LSB: LDAP servers (slapd)
          Loaded: loaded (/etc/rc.d/init.d/ldap)
          Active: inactive (dead)
          CGroup: name=systemd:/system/ldap.service

[root@web ~]#

Problem lies in /etc/rc.d/init.d/ldap line 194
after fixing these problems ldap comes up.
Manuel Hiebel 2012-04-25 11:48:37 CEST

Assignee: bugsquad => dlucio
Source RPM: (none) => openldap

Comment 1 Daniel Lucio 2012-04-28 06:26:21 CEST
fixed,

please push it. I have problems with email.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Buchan Milne 2012-07-09 17:11:06 CEST
A similar problem existed in the pre/post scripts which wasn't caught, affecting Mageia 2.

I have just fixed in cauldron r269073

CC: (none) => bgmilne


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