Zimbra LDAP problem - Unable to determine enabled services from ldap

[balaceo]

Release 6.0.5_GA_2213.RHEL5_64_20100202214931 CentOS5_64 NETWORK edition.

[phoenix]

Originally Posted by balaceo

Release 6.0.5_GA_2213.RHEL5_64_20100202214931 CentOS5_64 NETWORK edition.

That needs to go in your forum profile, not in this thread otherwise we have to keep asking you which version is installed.

[balaceo]

Hello,

The server was working fine till night.
It all started with an 'Network Issue' alert on webmail and admin logins.

I tried to restart services with zmcontrol stop, followed by zmcontrol start
LDAP, Mail, Logger and Stats reported down after restart.

Following to this, we reinstalled the SSL certificate to see if that fixed the issue.

Further, we have not checked to the DNS and host file yet.
Can you help me on this?

[balaceo]

Hello,

This is what i get on checking the service status.
The restart attempts for Mail and Postfix fails.

[zimbra@zcs1 root]$ zmcontrol status
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Host zcs1.ishtamail.com
antispam Running
antivirus Running
ldap Running
logger Stopped
zmlogswatchctl is not running
mailbox Stopped
zmmtaconfig is running.
mailboxd is not running.
zmmailboxdctl is not running
mta Stopped
postfix is not running
snmp Running
spell Running
stats Running

[balaceo]

Hello,

I just tried this one, posted by pankaj_garg and it worked for me.

Try the following steps as root:

1) Stop the zimbra service:
su - zimbra -c "/opt/zimbra/bin/zmcontrol stop"

2) Delete the contents of the redolog directory:
rm -rf /opt/zimbra/redolog/*

3)Fix zimbra permissions using the following command:
/opt/zimbra/libexec/zmfixperms -verbose -extended

4)Start the zimbra service again:
su - zimbra -c "/opt/zimbra/bin/zmcontrol start"

[mrcoffee11]

Does this article help?

Zimbra: Problem after upgrading from 5.0.10 to 5.0.14

Good luck,
Roderick

[jktarus]

Am also experienceing the same error. On trying to login to zimbra, it complained of "Network error". On restarting the services, I got the error below. Please help.
========================================
Starting ldap...Done.
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure:
ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException
sun.security.validator.ValidatorException: PKIX path validation
failed: java.security.cert.CertPathValidatorException: timestamp check
failed)
zimbra logger service is not enabled! failed.


Starting mailbox...Done.
Starting memcached...Done.
Starting imapproxy...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
=================================================

[phoenix]

Originally Posted by jktarus

Am also experienceing the same error. On trying to login to zimbra, it complained of "Network error". On restarting the services, I got the error below. Please help.
========================================
Starting ldap...Done.
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure:
ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException
sun.security.validator.ValidatorException: PKIX path validation
failed: java.security.cert.CertPathValidatorException: timestamp check
failed)
zimbra logger service is not enabled! failed.


Starting mailbox...Done.
Starting memcached...Done.
Starting imapproxy...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
=================================================

The highlighted services should not be installed on a single server, search the forums for details of how to disable and remove them plus setting the ports back to their default. When you've done that restart zimbra and see what happens, if it still fails then search the forums for details on how to fix it.