Hello Sigurd Holter
Am 2014-11-10 um 16:14 schrieb Sigurd Holter:
>
>> 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.
>>
>
> This is just an example of what is logged with information excluded
> (changed to 'xxx') as I do not want to advertise our information for the
> whole world.
> As mentioned, this does not seem to be a SOGo configuration error as the
> setup works fine for several days before suddenly stopping.
> So the information in the logs is correct, and the information in the
> logs is the same as is entered in sogo.conf - and therefore the same
> that is used for the whole time SOGo works correctly.
>
> OK, so it is not the SOGo config. (BTW: I didn't mean the 'xxx' parts, but the double cn= parts in the above ldap name.) >>> 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? >> > > The LDAP server is as mentioned a Windows AD server which is never > closed down. > Other services authenticate towards the same server (i.e. postfix, > dovecot etc.) and they have not complained about missing connection. > > Backup/logrotate is not running at the time the connection is lost. > If, as you say, SOGo makes a new connetion for each request - this > shouldn't matter as SOGo should pick up a new connection if one is lost. > But - if SOGo makes a persistent connection it would be understandable > that the connection at some time might be lost. > I imagine that SOGo then should find out and reconnect by itslf. > > This is not a problem that appears and then disappears. > If SOGo starts complaining about not being able to contact the LDAP > server at 02:00, it still complains about this at 08:00. > But all other services connection to the Windows AD/LDAP-server work > fine from 02:00 to 08:00. > It is therefore a purely SOGo problem as far as I can see. > > But I cannot understand why SOGo works fine for a couple of days, and > then suddenly says it can't find the server. > As mentioned before, a "service sogo restart" makes everything work again. > I do not have to restart the LDAP/Windows AD at any time, the problem is > not with the LDAP/Windows AD server. > Strange. The only thing causing this I can think of is, that your SOGo server gets a new IP via DHCP and SOGo is still using the old IP-Address, which doesn't work anymore, till it is restarted. But then you shouldn't be able to contact SOGo via webinterface too. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
