Hello
Am 2014-11-11 um 08:21 schrieb Sigurd Holter:
>
> Thank you for your patience and tips.
>
>> 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 rest
Hi !
Thank you for your patience and tips.
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 webint
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]>
> NAME:LDAPException REASON:operation bind failed: Can't contact LDAP
> serv
Hi !
Thank you for your follow-up.
> Nov 09 11:30:01 sogod [41436]:|SOGo| starting method 'POST' on uri
'/SOGo/connect' Nov 09 11:30:01 sogod [41436]:
<0x0x7f6a9cfe20b0[LDAPSource]>
NAME:LDAPException REASON:operation bind failed: Can't contact LDAP
server >(0x) INFO:{login = "cn=xx
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]: <0x0x7f
Hi !
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]> NAME:LDAPException REASON:operation bind failed: Can'
Hi !
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
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, S
Hi Sigurd,
can you reach your LDAP server with telnet (on the used port) if your
SOGo server hangs?
Stefan
Am 27.10.2014 11:39, schrieb Sigurd Holter:
> Hi !
>
> Thank you for your suggestions.
>
> I'm afraid that none of these suggestions are appropriate to the
> current situation.
> This is no
Hi !
Thank you for your suggestions.
I'm afraid that none of these suggestions are appropriate to the current
situation.
This is no cluster installation, it is a single instance of a VM running
on the same physical machine as SOGo.
There are no other services running on this machine.
The mach
Hello Sigurd Holter
Am 2014-10-26 um 09:02 schrieb sig...@westaudio.no:
>
> The past few days we are seeing this in our logs :
>
> NAME:LDAPException REASON:operation bind failed: Can't contact LDAP server
> (0x)
>
> Our users cannot log on to the web interface.
>
> Restarting the SOGo
Hi !
The past few days we are seeing this in our logs :
NAME:LDAPException REASON:operation bind failed: Can't contact LDAP server
(0x)
Our users cannot log on to the web interface.
Restarting the SOGo daemon makes everything work again.
The LDAP server in this case is a Windows 2012 R
12 matches
Mail list logo
