Hi people.
I have a zimbra installation running on Fedora Core 5 (zcs 4.5.0_GA_612.FC5). Just this afternoon I ran a repair (upgrade) for some reason or other using the same zimbra version and I got into some real trouble.
Errors began when setting defaults from and existing config: see below-
------
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.log.27863
Setting defaults...Setting defaults from existing config...Warning: null valued key
'mysql_logger_root_password'
Done
Checking for port conflicts
Starting ldap...Done
Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause:
javax.naming.CommunicationException localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException
localhost:389)
Done
Main menu
1) Hostname: xxxx.or.ke
2) Ldap master host: xxxx.or.ke
3) Ldap port: 389
4) Ldap password: set
5) zimbra-ldap: Enabled
6) zimbra-store: Enabled
+Create Admin User: no
+Enable automated spam training: yes
******* +Spam training user: UNSET
******* +Non-spam(Ham) training user: UNSET
+Global Documents Account:
wiki@xxxx.or.ke
+SMTP host: xxxx.or.ke
******* +Web server HTTP port: UNSET
******* +Web server HTTPS port: UNSET
+Web server mode: mixed
+Enable POP/IMAP proxy: no
******* +IMAP server port: UNSET
******* +IMAP server SSL port: UNSET
******* +POP server port: UNSET
******* +POP server SSL port: UNSET
+Use spell check server: yes
+Spell server URL:
http://xxxx.or.ke:7780/aspell.php
7) zimbra-mta: Enabled
8) zimbra-snmp: Enabled
9) zimbra-logger: Enabled
10) zimbra-spell: Enabled
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit
It appears the installer is unable to read the ldap file. Why is this?
I had (happily) just done a complete backup of my zimbra folder and also tried to recover using that and advice from this link
Moving ZCS to Another Server » Zimbra :: Blog but there is no change.
Help!