Quote:
i get this when i configure
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException myhostname:389)
|
I've got this message once or two. when:
Installed zimbra N°1 lets name it
zimbra.zimbra.orgIP N°1
Then installed a "second zimbra install" for test again.
lets name it
brazim.brazim.orgIP N°2
different hostnames, differents domains, differents IPs.
different partitions but same computer and SAME MAC Adresses (buitl-in Ethernet).
I have DNS Servers (And AppleRemoteDesktop)
The pb - for me- was that in a way or another, my network was not happy and the way to solve this was :
Add a 5$ PCI NIC Card and reboot the zimbrabox install 2 using the second NIC card.
reboot My DNS Server, reboot my router, (in case - just to be sure)
No more "ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException myhostname:389)"
Another thing, when you are in DirectoryAccess.app is LDAP checked or not ?
If it is checked, does it point to the default of OsX (aka 127.0.0.1), then if so just uncheck everything (unless of course you do have CUSTOM LDAP settings for kerberos or other stuff).
If you do not use LDAP, then better uncheck it in DirectoryAccess soi there is no conflict with zimbra serving ldap.
You can also if checked, uncheck Netinfo as you may not need it either (it should be already unchecked).
Did Ldap worked once or did it never worked on your install?
To get JAVA 1.5:
Did you change the symlink for CurrentJDK to point to 1.5.0 ?
or
Did you change the /etc/profile and/or .bash - .bash_profile files ?