Checking ldap on localhost:389...FAILED ( ldap_bind: Can't contact LDAP server (-1) )

[rmvg]

I get this error message when upgrading from m2 to GA tried resetting the lapd password but to no avial. Please i am in the middle of an upgrade here and i think the server is down. Cannot continue upgrade only option is to leave without writing changes.


ps have been getting this error for awhile when zimbra is shut down and ask for zmcontrol status also during upgrade
Tue Feb 21 15:40:57 2006: Starting mysql

Tue Feb 21 15:41:54 2006: Stopping mysql

Tue Feb 21 15:41:59 2006: Updating ldap domain admin attributes

Checking 3.0.0_M4
Tue Feb 21 15:42:15 2006: Updating from 3.0.0_M4

Checking 3.0.0_GA
Tue Feb 21 15:42:28 2006: Updating from 3.0.0_GA

Tue Feb 21 15:42:28 2006: Stopping ldap

Upgrade complete

Checking for port conflicts

Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException shoemasters.com:389)

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException shoemasters.com:389)

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException shoemasters.com:389)

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException shoemasters.com:389)

Done

Checking ldap on localhost:389...FAILED ( ldap_bind: Can't contact LDAP server (-1) )
HERE ARE THE ERRORS WHEN I TRY TO START ZIMBRA GA
Quit without applying changes? [No] yes

[root@shoemasters zcs]# su zimbra

[zimbra@shoemasters zcs]$ zmcontrol

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException shoemasters.com:389)


Release 3.0.0_GA_156.FC3_20060206123229 FC3 FOSS edition
/opt/zimbra/bin/zmcontrol [-v -h -H ] command [args]
-v: display version

-h: print usage statement

-H: Host name (localhost)
Command in:

maintenance Toggle maintenance mode

shutdown Stop services

start Start services

startup Start services

status Display service status

stop Stop services
[zimbra@shoemasters zcs]$ zmcontrol status

Cannot determine services - exiting[zimbra@shoemasters zcs]$ zmcontrol stop

Host shoemasters.com

Stopping antispam...Done

Stopping antivirus...Done

Stopping ldap...Done

Stopping logger...Done

Stopping mailbox...Done

Stopping mta...Done

Stopping snmp...Done

Stopping spell...Done

[zimbra@shoemasters zcs]$ zmcontrol start

Host shoemasters.com

Starting ldap...Done.

Starting antispam...Done.

Starting antivirus...Done.

Starting logger...Done.

Starting mailbox...Done.

Starting mta...FAILED

getService: sasl

getService: webxml

getService: perdition

DO: /opt/zimbra/postfix/sbin/postconf -e content_filter='smtp-amavis:[127.0.0.1]:10024'

DO: /opt/zimbra/postfix/sbin/postconf -e myhostname='shoemasters.com'

DO: /opt/zimbra/postfix/sbin/postconf -e recipient_delimiter=''

DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_sasl_auth_enable='yes'

DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_tls_auth_only='yes'

DO: /opt/zimbra/postfix/sbin/postconf -e disable_dns_lookups='no'

DO: /opt/zimbra/postfix/sbin/postconf -e message_size_limit='10240000'

DO: /opt/zimbra/postfix/sbin/postconf -e relayhost=''

DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_recipient_restrictions='reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_destination, permit'

saslauthd[8734] :set_auth_mech : failed to initialize mechanism zimbra


Starting snmp...Done.

Starting spell...Done.


[zimbra@shoemasters zcs]$

[zimbra@shoemasters zcs]$ zmcontrol status

Host shoemasters.com

antispam Running

antivirus Running

ldap Running

logger Running

mailbox Running

mta Stopped

snmp Running

spell Running

[zimbra@shoemasters zcs]$

[marcmac]

looks like ldap failed to stop before the upgrade.
Try the sasl fix you talked about in the other thread (3 posts on one error - I'm impressed).