Forums

Resolved
0 votes
As per the title, the only difference I can see before and after doing slapd restart from the output of service slapd status -l is:

BEFORE RESTART
Main PID: 1179 (slapd)
CGroup: /system.slice/slapd.service
└─1179 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/

AFTER RESTART of slapd:
Main PID: 4151 (slapd)
CGroup: /system.slice/slapd.service
└─4151 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/ ldaps://192.168.1.250/

192.168.1.250 being the static IP of server in question which is configured as Standalone without firewall.

So for some reason the local ip is not being picked up initially but restarting ldap does pick up the ip.


Where do I start looking?
:
Sunday, June 19 2016, 09:24 AM
Share this post:
Responses (24)
  • Accepted Answer

    Tuesday, October 18 2016, 05:50 PM - #Permalink
    Resolved
    0 votes
    Malcolm Warwick wrote:

    Just applied all the latest updates and still having the same problem. Did you still want to do remote session?


    Hi,

    Is there some solution for this problem.
    I've setup a new server for our community and i'm seeing the same erros in the log.
    Starting OpenLDAP Server Daemon...
    Oct 18 19:41:31 ioch prestart.sh: Configuration directory '/etc/openldap/slapd.d' does not exist.
    Oct 18 19:41:31 ioch prestart.sh: Warning: Usage of a configuration file is obsolete!
    Oct 18 19:41:31 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> ldap_result() failed: Can't contact LDAP server
    Oct 18 19:41:31 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> ldap_abandon() failed to abandon search: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:31 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:31 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:32 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:32 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:33 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:33 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:34 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:34 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:35 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:35 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:36 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:36 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:36 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:36 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:37 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:37 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:37 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:37 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:38 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:38 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:38 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:38 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:39 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:39 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:39 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:39 ioch nslcd[12486]: [946b0d] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 18 19:41:40 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:40 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> no available LDAP server found: Can't contact LDAP server: Transport endpoint is not connected
    Oct 18 19:41:40 ioch nslcd[12486]: [384b63] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected


    Somwhow the system s running, but don't know is this gives us errors on the long term.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2016, 11:35 PM - #Permalink
    Resolved
    0 votes
    Just applied all the latest updates and still having the same problem. Did you still want to do remote session?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 06 2016, 05:08 PM - #Permalink
    Resolved
    0 votes
    Frank Horsfall wrote:

    Hello Newbie Frank here

    I am encountering the same problem. It was working last week, but I performed and update/restart and now I'm stuck back in the situation where the account manager and directory services will not come up.

    Frank

    Frank,
    try a configuration restore earlier then the update (1-2 days before).

    https://SERVER-IP:81/app/configuration_backup
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 06 2016, 12:15 AM - #Permalink
    Resolved
    0 votes
    Hello Newbie Frank here

    I am encountering the same problem. It was working last week, but I performed and update/restart and now I'm stuck back in the situation where the account manager and directory services will not come up.

    Frank
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 06 2016, 12:06 AM - #Permalink
    Resolved
    0 votes
    Thank you for posting this. I am encountering the same problem. I have reviewed similar posts and tried out the suggested steps but seem to at a stalemate.

    I'm running Community edition 7 2.2.4-1


    Any ideas?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, July 05 2016, 09:24 PM - #Permalink
    Resolved
    0 votes
    Hi Peter

    I clicked on the link and loggged on to Clear Centre, submitted the details and got an "Invalid Ticket" response :(

    Please advise
    Malcolm
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, July 05 2016, 12:40 PM - #Permalink
    Resolved
    0 votes
    Malcolm Warwick wrote:

    FWIW the latest batch of updates hasn't fixed this issue :(


    Doh! Time to escalate this to our systemd guru - Darryl. Could we get that remote access to look around? You can submit your credentials via your ClearCenter account - https://secure.clearcenter.com/portal/system_password.jsp
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, July 05 2016, 03:16 AM - #Permalink
    Resolved
    0 votes
    FWIW the latest batch of updates hasn't fixed this issue :(
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 27 2016, 07:11 PM - #Permalink
    Resolved
    0 votes
    Doh. I'll re-investigate.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 22 2016, 09:09 PM - #Permalink
    Resolved
    0 votes
    The ONLY reference to slapd in cat /var/log/messages |grep is

    Jun 23 06:57:27 tester prestart.sh: Configuration directory '/etc/openldap/slap .d' does not exist.

    The 2 prestart messages are visible when running status thus:

    [root@tester ~]# service slapd status -l
    Redirecting to /bin/systemctl status -l slapd.service
    ● slapd.service - OpenLDAP Server Daemon
    Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled)
    Active: active (running) since Thu 2016-06-23 07:04:52 AEST; 53s ago
    Docs: man:slapd
    man:slapd-config
    man:slapd-hdb
    man:slapd-mdb
    file:///usr/share/doc/openldap-servers/guide.html
    Process: 1578 ExecStart=/usr/sbin/slapd -u ldap -h ${SLAPD_URLS} $SLAPD_OPTIONS (code=exited, status=0/SUCCESS)
    Process: 1048 ExecStartPre=/usr/libexec/openldap/prestart.sh (code=exited, status=0/SUCCESS)
    Main PID: 1590 (slapd)
    CGroup: /system.slice/slapd.service
    └─1590 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/

    Jun 23 07:04:50 tester.example.com systemd[1]: Starting OpenLDAP Server Daemon...
    Jun 23 07:04:50 tester.example.com prestart.sh[1048]: Configuration directory '/etc/openldap/slapd.d' does not exist.
    Jun 23 07:04:50 tester.example.com prestart.sh[1048]: Warning: Usage of a configuration file is obsolete!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 22 2016, 05:02 PM - #Permalink
    Resolved
    0 votes
    At what point does the network-online.target get achieved? Could it be a self-inflicted injury caused by making slapd wait until the network comes on line?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 22 2016, 03:55 PM - #Permalink
    Resolved
    0 votes
    It looks like LDAP is not coming up at all. Are there any references to "slapd" in /var/log/messages on a reboot? You should see:


    Jun 22 11:40:38 clear7 prestart.sh: Configuration directory '/etc/openldap/slapd.d' does not exist.
    Jun 22 11:40:38 clear7 prestart.sh: Warning: Usage of a configuration file is obsolete!


    BTW, the "new" slapd.d configuration style referenced in the above warning message is ridiculous. Yes, there are some advantages to slapd.d over the slapd.conf, but it's still ridiculous.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 22 2016, 07:02 AM - #Permalink
    Resolved
    0 votes
    Hi Peter

    This is output /var/log/messages immediately after a reboot, of this helps?

    [root@tester ~]# tail /var/log/messages -n 100
    Jun 22 16:58:42 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:42 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:43 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:43 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:43 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:43 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:43 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:43 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:43 tester systemd: Started ClamAV daemon.
    Jun 22 16:58:43 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:43 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:44 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:44 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:44 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:44 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:44 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:44 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:44 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:44 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:45 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:45 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:45 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:45 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:45 tester nslcd[1608]: [e8944a] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:45 tester nslcd[1608]: [e8944a] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:45 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:45 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:45 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:45 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:46 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:46 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:46 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:46 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:46 tester nslcd[1608]: [e8944a] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:46 tester nslcd[1608]: [e8944a] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:46 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:46 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:46 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:46 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:47 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:47 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:47 tester nslcd[1608]: [e8944a] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [e8944a] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:47 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:47 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:47 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:48 tester nslcd[1608]: [8b4567] <group/member="nslcd"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:48 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:48 tester nslcd[1608]: [e8944a] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [e8944a] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:48 tester nslcd[1608]: [495cff] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:48 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:48 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found, sleeping 1 seconds
    Jun 22 16:58:49 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Jun 22 16:58:49 tester nslcd[1608]: [3c9869] <group/member="clearconsole"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:49 tester nslcd[1608]: [8b4567] <group/member="nslcd"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:49 tester systemd: Created slice user-0.slice.
    Jun 22 16:58:49 tester systemd: Starting user-0.slice.
    Jun 22 16:58:49 tester systemd: Started Session 1 of user root.
    Jun 22 16:58:49 tester systemd-logind: New session 1 of user root.
    Jun 22 16:58:49 tester systemd: Starting Session 1 of user root.
    Jun 22 16:58:49 tester nslcd[1608]: [e8944a] <passwd="guest"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:49 tester nslcd[1608]: [e87ccd] <passwd="GUEST"> no available LDAP server found: Server is unavailable
    Jun 22 16:58:49 tester nslcd[1608]: [495cff] <passwd="guest"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:49 tester systemd: smb.service: main process exited, code=exited, status=255/n/a
    Jun 22 16:58:49 tester systemd: Failed to start Samba SMB Daemon.
    Jun 22 16:58:49 tester systemd: Unit smb.service entered failed state.
    Jun 22 16:58:49 tester systemd: smb.service failed.
    Jun 22 16:58:49 tester systemd: Reached target Multi-User System.
    Jun 22 16:58:49 tester systemd: Starting Multi-User System.
    Jun 22 16:58:49 tester systemd: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
    Jun 22 16:58:49 tester systemd: Starting Update UTMP about System Runlevel Changes...
    Jun 22 16:58:49 tester systemd: Started Update UTMP about System Runlevel Changes.
    Jun 22 16:58:49 tester systemd: Startup finished in 462ms (kernel) + 1.624s (initrd) + 24.346s (userspace) = 26.433s.
    Jun 22 16:58:49 tester nslcd[1608]: [b0dc51] <group/member="clearconsole"> no available LDAP server found: Can't contact LDAP server
    Jun 22 16:58:50 tester systemd: Created slice user-991.slice.
    Jun 22 16:58:50 tester systemd: Starting user-991.slice.
    Jun 22 16:58:50 tester systemd: Started Session 2 of user clearconsole.
    Jun 22 16:58:50 tester systemd-logind: New session 2 of user clearconsole.
    Jun 22 16:58:50 tester systemd: Starting Session 2 of user clearconsole.
    Jun 22 16:58:51 tester systemd: Stopping SYSV: ClearOS firewall...
    Jun 22 16:58:51 tester firewall: nat mangle filter
    Jun 22 16:58:51 tester firewall: [ OK ]#015[ OK ]#015Resetting built-in chains to the default ACCEPT policy:[ OK ]
    Jun 22 16:58:51 tester systemd: Starting SYSV: ClearOS firewall...
    Jun 22 16:58:51 tester clearsyncd[663]: System Events: Socket hang-up: 29
    Jun 22 16:58:51 tester firewall: Starting firewall: [ OK ]
    Jun 22 16:58:51 tester systemd: Started SYSV: ClearOS firewall.
    Jun 22 16:59:02 tester chronyd[616]: Selected source 192.189.54.17
    [root@tester ~]#
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 21 2016, 10:20 PM - #Permalink
    Resolved
    0 votes
    If you want to remote into my VM just say the word :)
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 21 2016, 09:53 PM - #Permalink
    Resolved
    0 votes
    Malcolm Warwick wrote:

    Bump!
    Malcolm Warwick wrote:

    Hello Peter

    I've just tried this change and it doesn't seem to have effect on my system, system status slapd -l does not show the local IP after a reboot.

    If it helps I have Publish Policy set to Local Network.

    Restarting slapd and the local IP appears, as before.

    TIA
    Malcolm


    Hmmm... I am unable to duplicate the issue. Will investigate.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 21 2016, 08:40 PM - #Permalink
    Resolved
    0 votes
    Bump!
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 10:02 PM - #Permalink
    Resolved
    0 votes
    Hello Peter

    I've just tried this change and it doesn't seem to have effect on my system, system status slapd -l does not show the local IP after a reboot.

    If it helps I have Publish Policy set to Local Network.

    Restarting slapd and the local IP appears, as before.

    TIA
    Malcolm
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 09:54 PM - #Permalink
    Resolved
    0 votes
    We're rolling out an update, but you can also make the change on your own. In the /usr/lib/systemd/system/slapd.service file, change the line starting with After from:

    After=syslog.target NetworkManager-wait-online.service


    To:

    After=syslog.target network-online.target NetworkManager-wait-online.service


    After making the change, run:

    systemctl daemon-reload
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 09:49 PM - #Permalink
    Resolved
    0 votes
    Thank you Nick and Peter for your responses :)

    Not sure what is meant by "kitchen sink"?

    Dumb question - which file is it that I need to change or is there going to be an update rolled out?

    TIA
    Malcolm
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 08:00 PM - #Permalink
    Resolved
    0 votes
    Yes, it's a timing issue and it looks like a straightforward fix.

    Gory details:

    In the OpenLDAP systemd startup script, it is configured to wait for the following services:

    After=syslog.target NetworkManager-wait-online.service


    ClearOS does not use the NetworkManager stuff, and OpenLDAP is the only service on my "kitchen sink" box that has a reference to it. Changing the reference from NetworkManager-wait-online.service to network-online.target seems to resolve the issue.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 05:25 PM - #Permalink
    Resolved
    0 votes
    It definitely sounds like a timing issue. I'm going to try to duplicate the issue.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 07:18 AM - #Permalink
    Resolved
    0 votes
    At a guess, ldap is starting early in the boot process before something like networking as started. Because of this it has not determined your LAN IP (perhaps a script which should be in prestart.sh). I have not investigates this, I'm just going off you report. I'd suggest you file a bug. In systemd it is possible to make ldap wait until lots of different events have happened including networking starting. Alternatively they may have to trigger a reload after networking has started. This thread may be a little relevant.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 20 2016, 05:07 AM - #Permalink
    Resolved
    0 votes
    So I've just built a clean install of 7.2 configured as private standalone and configured the directory. Straightaway I can connect using Windows ldapadmin.

    Reboot and unable to connect as the server IP address is missing here:
    Main PID: 965 (slapd)
    CGroup: /system.slice/slapd.service
    └─965 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/

    Restart ldap and bingo!

    Main PID: 3879 (slapd)
    CGroup: /system.slice/slapd.service
    └─3879 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/ ldaps://192.168.1.248

    Is this a bug or am I missing something?

    TIA :)
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, June 19 2016, 09:37 PM - #Permalink
    Resolved
    0 votes
    UPDATE:

    When restarting ldap this error is displayed:

    Jun 19 18:46:54 server.example.com prestart.sh[4087]: Configuration directory '/etc/openldap/slapd.d' does not exist.
    Jun 19 18:46:54 server.example.com prestart.sh[4087]: Warning: Usage of a configuration file is obsolete!
    The reply is currently minimized Show
Your Reply