Results 1 to 10 of 10

Thread: LDAP error Message in server.log

  1. #1
    Junior Member
    Join Date
    Aug 2011
    Location
    Germany
    Posts
    14

    LDAP error Message in server.log

    Hello,

    after installing the new 7.1.13 i still have an ldap-error message in my server.log.

    Sat Jul 25 07:06:46 2015: Loading searchfolders
    Sat Jul 25 07:06:51 2015: Startup succeeded on pid 2041
    Sat Jul 25 07:31:24 2015: Disconnect from LDAP because search error Can't contact LDAP server

    This error occurred after upgrading to 7.1.12 while 7.1.11 was running fine. I am running a Ubuntu 14.04.2 VM samba 4 based AD with a SB 5 User ZCP installation. ZCP is on a seperat Ubuntu 14.04.02 VM.

    Any ideas what causes this ldap error?

    Michael

  2. #2
    Senior Member
    Join Date
    Dec 2012
    Posts
    267
    I have also seen similar issues on a 7.1.12 setup, although I did not assume that it got introduced in 7.1.12 until now. Also, haven't tried 7.1.13 there yet.

  3. #3
    Junior Member
    Join Date
    Aug 2014
    Location
    Pinneberg
    Posts
    23
    Same with 7.1.13

  4. #4
    Ahoi,
    after upgrading 7.1.10 to 7.1.13 the LDAP connection to our AD broke too.

    I figured out that I had defined two ldap_hosts in the ldap.cfg

    The documentation of Zarafa 7.0 says that only one host is allowed and multiple LDAP servers aren't supported. (someone might correct me if not)
    I've been overreading this all the time. But it also wasn't an issue 'till now.

    Hope this might help you
    Zarafa 7.1.10 Pro
    OS: Ubuntu 10.04 LTS x64
    MTA: Postfix 2.X / Procmail
    Database: MySQL 5.X
    Clients: Outlook 2k - 2013
    Mobile: Z-Push 2.1.2 final / BES 5

  5. #5
    Senior Member
    Join Date
    Dec 2012
    Posts
    267
    @KPaxx:
    Have you tried using instead of ldap_host (with ldap_protocol and ldap_port)? This seems to be the official way for configuring multiple LDAP servers. Besides that, this looks like a different problem than the others mentioned in this thread. I assume your server did not start at all until you changed your configuration, right?

    @mschindler, @thooge: I guess your servers started and you were seeing no problems besides these log messages, right?

    Maybe someone from Zarafa can comment on these issues.

  6. #6
    Oy thanks ldap_uri works great.
    Jepp the server didnt start up at all. (just thought this could be a hint)
    Zarafa 7.1.10 Pro
    OS: Ubuntu 10.04 LTS x64
    MTA: Postfix 2.X / Procmail
    Database: MySQL 5.X
    Clients: Outlook 2k - 2013
    Mobile: Z-Push 2.1.2 final / BES 5

  7. #7
    Oy thanks ldap_uri works great.
    Jepp the server didnt start up at all. (just thought this could be a hint)
    Zarafa 7.1.10 Pro
    OS: Ubuntu 10.04 LTS x64
    MTA: Postfix 2.X / Procmail
    Database: MySQL 5.X
    Clients: Outlook 2k - 2013
    Mobile: Z-Push 2.1.2 final / BES 5

  8. #8
    Zarafa

    Join Date
    Jan 2009
    Location
    Hanover, Germany
    Posts
    1,891
    We did some changes to the ldap plugin in 7.1.12. I think the error message is a bit misleading, but its not really an issue (without having investigated it much until now). The error "Can't contact LDAP server" comes from the ldap library, the reason this happens is simply because openldap closed the connection. If required zarafa-server will then initiate a new connection to openldap (only this new connection is not logged).
    Regards Felix

    How to get Kopano

    Zarafa ALPHA/BETA/RC feedback in BETA forum please.
    Zarafa IRC chat: irc.freenode.com > #zarafa
    Zarafa documentation: http://documentation.zarafa.com/

    No support via PM! Please contact our sales team for an offer if you want my full attention.

  9. #9
    Junior Member
    Join Date
    Oct 2015
    Posts
    3
    We are seeing similar errors with 7.1.13. We can also relate some of them to users losing their session in the WebApp. So it seems to be a problem of sorts.
    Here is a log snippet with log level 0x00020007 (including debug of the LDAP plugin). No reconnect is done after the failure.

    We are seeing two kinds of log messages. These might or might not be caused by the same problem:
    These messages starting occuring after upgrading from 7.1.11 to 7.1.13. We see them on several servers, some of which have OpenLDAP as backend, some of which have Samba 4 AD as backend.

  10. #10
    Junior Member
    Join Date
    Oct 2015
    Posts
    3

    Found workaround

    It seems a workaround is to specify your ldap server twice, like this:

    Now, when the connect fails, Zarafa retries with the second ldap host (which is the same). For us, this works:

    So you'll still get the "Can't contact LDAP server" message, but the connection no longer fails.

Similar Threads

  1. Error Message in /var/log/zarafa/server.log
    By comfreak in forum Installation, Configuration and Maintenance
    Replies: 6
    Last Post: 11-05-2015, 09:25 AM
  2. Cannot connect to the Zarafa server error message on logon
    By rafigh82 in forum Installation, Configuration and Maintenance
    Replies: 2
    Last Post: 20-06-2012, 11:54 AM
  3. Strange error message in server.log
    By draft in forum Installation, Configuration and Maintenance
    Replies: 2
    Last Post: 15-06-2011, 07:21 AM
  4. plugin error message after upgrading multi-server to 6.40
    By isol in forum Installation and Configuration Archives
    Replies: 0
    Last Post: 31-08-2010, 12:23 PM
  5. SQL and other error message in Zarafa Server Log
    By modir in forum Administration and Integration Archives
    Replies: 2
    Last Post: 30-11-2009, 12:51 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •