Hello Sigurd Holter
Am 2014-11-10 um 12:44 schrieb Sigurd Holter:
>
> This problem seems to persist.
> We are now on SOGo nightly build 141107.
>
> sogo.log shows :
>
> Nov 09 11:30:01 sogod [41436]:|SOGo| starting method 'POST' on uri
> '/SOGo/connect'
> Nov 09 11:30:01 sogod [41436]: <0x0x7f6a9cfe20b0[LDAPSource]>
> <NSException: 0x7f6a9f17b5e0> NAME:LDAPException REASON:operation bind
> failed: Can't contact LDAP server (0xFFFFFFFF) INFO:{login =
> "cn=xxx,cn=xxx,dc=xxx,dc=xxx"; }Is the above entry just a typo? Normally this should be something like cn=xxxx,ou=yyy,dc=zzz,dc=tld. > Nov 09 11:30:01 sogod [41436]: SOGoRootPage Login from 'xxx' for user > 'xxx' might not have worked - password policy: 65535 grace: -1 expire: > -1 bound: 0 > Nov 09 11:30:01 sogod [41436]:|SOGo| request took 0.005003 seconds to > execute > xxx - - [09/Nov/2014:11:30:01 GMT] "POST /SOGo/connect HTTP/1.1" 403 > 34/60 0.006 - - 0 > > I can connect to the LDAP server from the SOGo machine using ldapsearch > and the same bind credentials as SOGo uses. > > To make clear - SOGo works fine for a while/some days, then suddenly > this error occurs. > So it is not a SOGo configuration error as far as I can see. > > Is the LDAP connection from SOGo persistent, or is a new connection made > for each request ? > They are opend when needed. Is a logrotate or backup running at these times? Perhaps it closes down the ldap server for that only for some seconds? > Den 28.10.2014 12:05, skrev Sigurd Holter: >> >> Thank you for your suggestions. >> >> There is no Samba running on this machine. >> >> The Windows AD running in a VM has it's own IP on it's own physical >> network card in bridged mode. >> Since the mail server (on a different machine on the same network) can >> access the Windows AD and use LDAP, it doesn't seem as this is a port >> problem. >> >> I can reach (connect) to the LDAP (Windows) server with telnet from >> the SOGo machine. >> I can run ldapsearch and get correct results from the SOGo machine. >> I can ping the LDAP (Windows) serve from the SOGo machine. >> >> So it seems to be a local SOGo problem I'm afraid. >> >> >> Den 27.10.2014 23:01, skrev Steve Ankeny: >>> >>> Do you have a collision between ports on the server? >>> >>> LDAP will use port 389, but Samba wants that port also. >>> >>> When I installed Samba, I had to change my LDAP port so it wouldn't >>> collide with Samba >>> >>> Do you have a process that's grabbing the port before LDAP can use it? >>> >>> On 10/27/2014 10:25 AM, Stefan Klatt wrote: >>>> >>>> can you reach your LDAP server with telnet (on the used port) if your >>>> SOGo server hangs? >>>> >>> > -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
