Had the same problem on a Zimbra 4.55 to 4.56 upgrade on a Red Hat 5 server today. The solution was simply to:
vi /etc/sudoers
comment out: #Default requiretty
Run the install.sh again or if the install is still running just wait till the LDAP start command is called again and it should all just start working.
Checking the /tmp/install.log.2309 (Zimbra install / upgrade log) provided the vital information to work out what to do.
(Might be useful if the Zimbra installer did a check for this requirement).
Quote:
Originally Posted by gbajczman  Hi! Again here because now I have this error message and the installation cannot continue because this error don't stop.
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
chown: cannot access `/opt/zimbra/tomcat/conf/keystore': No such file or directory
chown: cannot access `/opt/zimbra/conf/smtpd.key': No such file or directory
chown: cannot access `/opt/zimbra/conf/smtpd.crt': No such file or directory
chown: cannot access `/opt/zimbra/conf/slapd.crt': No such file or directory
chown: cannot access `/opt/zimbra/conf/perdition.pem': No such file or directory
chown: cannot access `/opt/zimbra/conf/perdition.key': No such file or directory
Operations logged to /tmp/zmsetup.log.27145
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Setting defaults...Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Done
Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking for port conflicts
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Checking ldap status
Starting ldap
ldap startup failed with exit code 256
Thx |