LDAP issues again

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
glennbtn
Advanced member
Advanced member
Posts: 108
Joined: Sat Sep 13, 2014 12:56 am

LDAP issues again

Post by glennbtn »

Hi All
Had ldap issues on a customer machine when it was running 8.0.3. Was advised by many that it needed to go up to 8.0.4 to resolve the issue. We have had no issues for months until yesterday. The server keeps becoming unavailable again, nothing has changed on the box since it's updated approx 2 months ago to 8.0.4. Checked all certificates and dns etc which are all fine but still getting this issue as below. Have to say that never had any of these issues on v7 and have quite a few boxes still running that version.
Any help her would be great, thanks
Glenn
Oct 25 07:39:47 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:39:47 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-transport.cf lookup error for "*"

Oct 25 07:40:01 server51 zimbramon[13196]: 13196:info: 2013-10-25 07:40:01, QUEUE: 15 2

Oct 25 07:40:17 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:40:17 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem

Oct 25 07:40:17 server51 postfix/trivial-rewrite[13085]: warning: virtual_alias_domains lookup failure

Oct 25 07:40:47 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:40:47 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem

Oct 25 07:40:47 server51 postfix/trivial-rewrite[13085]: warning: virtual_alias_domains lookup failure

Oct 25 07:41:02 server51 postfix/master[3417]: warning: unix_trigger_event: read timeout for service public/qmgr

Oct 25 07:41:17 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:41:17 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem
umarzuki
Advanced member
Advanced member
Posts: 97
Joined: Sat Sep 13, 2014 12:46 am

LDAP issues again

Post by umarzuki »

[quote user="glennbtn"]Hi All
Had ldap issues on a customer machine when it was running 8.0.3. Was advised by many that it needed to go up to 8.0.4 to resolve the issue. We have had no issues for months until yesterday. The server keeps becoming unavailable again, nothing has changed on the box since it's updated approx 2 months ago to 8.0.4. Checked all certificates and dns etc which are all fine but still getting this issue as below. Have to say that never had any of these issues on v7 and have quite a few boxes still running that version.
Any help her would be great, thanks
Glenn
Oct 25 07:39:47 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:39:47 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-transport.cf lookup error for "*"

Oct 25 07:40:01 server51 zimbramon[13196]: 13196:info: 2013-10-25 07:40:01, QUEUE: 15 2

Oct 25 07:40:17 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:40:17 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem

Oct 25 07:40:17 server51 postfix/trivial-rewrite[13085]: warning: virtual_alias_domains lookup failure

Oct 25 07:40:47 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:40:47 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem

Oct 25 07:40:47 server51 postfix/trivial-rewrite[13085]: warning: virtual_alias_domains lookup failure

Oct 25 07:41:02 server51 postfix/master[3417]: warning: unix_trigger_event: read timeout for service public/qmgr

Oct 25 07:41:17 server51 postfix/proxymap[13081]: error: dict_ldap_connect: Unable to set STARTTLS: -1: Can't contact LDAP server

Oct 25 07:41:17 server51 postfix/trivial-rewrite[13085]: warning: proxy:ldap:/opt/zimbra/conf/ldap-vad.cf: table lookup problem[/QUOTE]
zimbra-ldap is running currently?
# su - zimbra

$ zmcontrol status
glennbtn
Advanced member
Advanced member
Posts: 108
Joined: Sat Sep 13, 2014 12:56 am

LDAP issues again

Post by glennbtn »

Hi
When we get this error it's hard to eve get ssh access so I end up bouncing the box. I will check the next time it happens if I can get in
uxbod
Ambassador
Ambassador
Posts: 7811
Joined: Fri Sep 12, 2014 10:21 pm

LDAP issues again

Post by uxbod »

Do you eventually get a login prompt from SSH ? It could be that your DNS settings on the server are wrong. When connecting to an SSH server it does perform a rDNS check.
glennbtn
Advanced member
Advanced member
Posts: 108
Joined: Sat Sep 13, 2014 12:56 am

LDAP issues again

Post by glennbtn »

Hi
I do eventually but something slows the box down so much when this issue happens so I bounce it quick to keep the customers off my back. The dns settings are correct and ssh normally is fine. Have double checked DNS with my other Zimbra boxes and all good.
umarzuki
Advanced member
Advanced member
Posts: 97
Joined: Sat Sep 13, 2014 12:46 am

LDAP issues again

Post by umarzuki »

[quote user="glennbtn"]Hi
I do eventually but something slows the box down so much when this issue happens so I bounce it quick to keep the customers off my back. The dns settings are correct and ssh normally is fine. Have double checked DNS with my other Zimbra boxes and all good.[/QUOTE]
This might not be related but I had a ZCS 8 on CentOS 6 with similar problem but no error on logs. Mailbox server suddenly hanged, but I can successfully ssh to it to restart its services (zmcontrol restart). Was too advised to patch it, but to 8.0.2.
Fixes advised did not solve it until I have configured it to be able to do full backup successfully.
Post Reply