Bug 181336
Summary: | slapd won't start on new install even after hacking init script | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Uhl <bill> |
Component: | openldap | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | jfeeney |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-14 13:22:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Uhl
2006-02-13 15:56:48 UTC
I see that you're using a non-standard directory for the slapd database files. Do you have SELinux enabled? Ifso, have you made sure /srv/gln/ldap/root has the correct security context? SELinux is anabled. I am new to using it. Following one of the answers in the selinux faq, I was able to change the policy to permissive. (status after reboot) [root@buildme1 ~]# sestatus -v SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: permissive Policy version: 20 Policy from config file: targeted I ran service ldap start and still get the same thing. [root@buildme1 ~]# service ldap start + . /etc/init.d/functions ++ TEXTDOMAIN=initscripts ++ umask 022 ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin ++ export PATH ++ '[' -z '' ']' ++ COLUMNS=80 ++ '[' -z '' ']' +++ /sbin/consoletype ++ CONSOLETYPE=pty ++ '[' -f /etc/sysconfig/i18n -a -z '' ']' ++ . /etc/sysconfig/i18n +++ LANG=en_US.UTF-8 +++ SYSFONT=latarcyrheb-sun16 ++ '[' pty '!=' pty ']' ++ '[' -n '' ']' ++ export LANG ++ '[' -z '' ']' ++ '[' -f /etc/sysconfig/init ']' ++ . /etc/sysconfig/init +++ BOOTUP=color +++ GRAPHICAL=yes +++ RES_COL=60 +++ MOVE_TO_COL='echo -en \033[60G' +++ SETCOLOR_SUCCESS='echo -en \033[0;32m' +++ SETCOLOR_FAILURE='echo -en \033[0;31m' +++ SETCOLOR_WARNING='echo -en \033[0;33m' +++ SETCOLOR_NORMAL='echo -en \033[0;39m' +++ LOGLEVEL=3 +++ PROMPT=yes ++ '[' pty = serial ']' ++ '[' color '!=' verbose ']' ++ INITLOG_ARGS=-q + '[' -r /etc/sysconfig/network ']' + . /etc/sysconfig/network ++ NETWORKING=yes ++ HOSTNAME=buildme1.greenlightnet.gln + '[' yes = no ']' + '[' -r /etc/sysconfig/ldap ']' + slapd=/usr/sbin/slapd + slurpd=/usr/sbin/slurpd + slaptest=/usr/sbin/slaptest + '[' -x /usr/sbin/slapd ']' + '[' -x /usr/sbin/slurpd ']' + RETVAL=0 + case "$1" in + start + user=ldap ++ basename /usr/sbin/slapd + prog=slapd ++ mktemp /tmp/start-slapd.XXXXXX + wrapper=/tmp/start-slapd.Ps3085 + harg=ldap:/// + grep -q '^TLS' /etc/openldap/slapd.conf + test x = xyes + test x = xyes + test -z /tmp/start-slapd.Ps3085 + cat + chmod u+x /tmp/start-slapd.Ps3085 + trap 'rm -f /tmp/start-slapd.Ps3085' EXIT + echo -n 'Starting slapd: ' Starting slapd: + daemon --check=slapd /tmp/start-slapd.Ps3085 + local gotbase= force= + local base= user= nice= bg= pid= + nicelevel=0 + '[' --check=slapd '!=' -check=slapd ']' + case $1 in + base=slapd + gotbase=yes + shift + '[' /tmp/start-slapd.Ps3085 '!=' /tmp/start-slapd.Ps3085 ']' + '[' -z yes ']' + '[' -f /var/run/slapd.pid ']' + '[' -n '' -a -z '' ']' + ulimit -S -c 0 + '[' -n '' ']' + '[' color = verbose -a -z '' ']' + '[' -z '' ']' + /tmp/start-slapd.Ps3085 + '[' 1 -eq 0 ']' + failure 'slapd startup' + rc=1 + '[' color '!=' verbose -a -z '' ']' + echo_failure + '[' color = color ']' + echo -en '\033[60G' + echo -n '[' [+ '[' color = color ']' + echo -en '\033[0;31m' + echo -n FAILED FAILED+ '[' color = color ']' + echo -en '\033[0;39m' + echo -n ']' ]+ echo -ne '\r' + return 1 + '[' -x /usr/bin/rhgb-client ']' + /usr/bin/rhgb-client --details=yes + '[' -w /var/gdm/.gdmfifo ']' + return 1 + RETVAL=1 + echo + '[' 1 -eq 0 ']' + '[' 1 -eq 0 ']' + return 1 + exit 1 + rm -f /tmp/start-slapd.Ps3085 Is this permissive enough or do I need to make other changes to open it up further? I'm unable to reproduce the problem on my fc4 box using your slapd.conf, so I'm thinking it must be something unique to your setup. Have you added a line like local4.* /var/log/ldap.log to your /etc/syslog.conf created /var/log/ldap.log and reloaded syslog? This will make syslog keep any messages slapd logs when it starts up. You might also want to try starting slapd by hand with debugging to see what it says. try /usr/sbin/slapd -d 1 -u ldap and see what it says. Also, for program output and configuration files, it's much better to attach them to the bug using the "Create a new attachment" dialog below instead of pasting them inline. Ok. Rebuilt with old ldap. Changed selinux to permissive. rechecked file and directory permissions. slapd started w/o a problem. Rebuilt system with current ldap. Kept selinux at permissive. rechecked file and directory permissions. slapd started and runs. Still get the following messages in /var/log/messages... Feb 14 08:08:47 buildme1 slaptest: sql_select option missing Feb 14 08:08:47 buildme1 slaptest: auxpropfunc error no mechanism available Feb 14 08:08:47 buildme1 slapd[2428]: sql_select option missing Feb 14 08:08:47 buildme1 slapd[2428]: auxpropfunc error no mechanism available Assuming these are not to be worried about, ldap seems to be up and running. Did not have to make any changes to startup scripts this time. While I would like to know if the messages above represent a problem, the server seems to be working at this point so I'm moving on. Thanks for your help and suggestions. |