Quote:
Originally Posted by phoenix  ..... and does your hosts file contain the correct information? Do you have DNS A & MX records pointing to your Zimbra server? |
Ok, I/ve changed this and now i didn't receive the hostname error but I have another :S
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
