[SOLVED] 5.019 to 6.03 Upgrade Ldap Admin password not verified

[mattvogt]

I'm attempting an upgrade (thankfully on my test server) from 5.019 to 6.03 on RHEL 5.3 and running into an error during the upgrade.

After everything gets upgraded (no issues) and it comes to the importing of the old configuration, I get prompted to complete some missing information (SMTP, Ldap root password, enable version update checks, etc.). All this is fine except for one item.

This is what I see

   1) Common Configuration:
         +Hostname:                                       server.my.co
         +Ldap master host:                               server.my.co
         +Ldap port:                                      389
*******  +Ldap Admin password:                            Not Verified
         +Secure interprocess communications:             no

When I choose (1) to edit the section, I see the same thing with line about the Ldap Admin password being #4, so I choose it to edit it. What it gives me as the default answer is the password it's supposed to be using. I've tried typing it in manually and just hitting enter, but it continues to be 'not verified'.

If I hit 'r' to return to the config menu, I see this in the upgrade log:

Fri Dec 11 09:08:40 2009 Checking ldap on server.my.co:389
Fri Dec 11 09:08:40 2009 failed: Unable to contact ldap at ldap://server.my.co:389: Connection refused
Fri Dec 11 09:08:40 2009 Couldn't bind to server.my.co as uid=zimbra,cn=admins,cn=zimbra
Fri Dec 11 09:08:40 2009 Checking ldap on server.my.co:389
Fri Dec 11 09:08:40 2009 failed: Unable to contact ldap at ldap://server.my.co:389: Connection refused
Fri Dec 11 09:08:40 2009 Couldn't bind to server.my.co as uid=zimbra,cn=admins,cn=zimbra
Fri Dec 11 09:08:40 2009 checking isEnabled zimbra-snmp
Fri Dec 11 09:08:40 2009 zimbra-snmp is enabled
Fri Dec 11 09:08:40 2009 Checking ldap on server.my.co:389
Fri Dec 11 09:08:40 2009 failed: Unable to contact ldap at ldap://server.my.co:389: Connection refused
Fri Dec 11 09:08:40 2009 Couldn't bind to server.my.co as uid=zimbra,cn=admins,cn=zimbra

Now of course it can't get to the ldap on server.my.co because the ldap is shut down for upgrading. I don't think it's a DNS issue because I can ping and dig the server and everything comes back fine.

I do also see a bunch of Java errors in the install log, along the lines of:

Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' referenced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)

I cannot get beyond this without quitting the installer, but it's only half installed at this point (upgraded but not configured).

Any thoughts? Any other info that would be useful?

Thanks so much.

[mattvogt]

Tried to upgrade to 5.0.20 first then to 6.0.3. The upgrade to 5.0.20 went fine, system came up normal, no errors. But I had the same issue going to 6.0.3.

[iway]

Have you checked the SSL certs? They can cause problems if old/invalid...

[LMStone]

I seem to recall many versions ago a manual procedure for older systems prior to an upgrade where you essentially had to set manually some passwords which in previous editions had not been set (or did not exist).

I'm not finding specific posts here in the forums at the moment, but you should feel free to open a support ticket with Zimbra on something like this.

Hope that helps,
Mark

[mattvogt]

Originally Posted by iway

Have you checked the SSL certs? They can cause problems if old/invalid...

Thanks for the reply. I've checked the certs, and they're valid and current.

[LMStone]

Anything in this post that might be applicable to your system?

6.0.3 Is Out & Recommended

Hope that helps,
Mark

[quanah]

LDAP should be running at the point you're at, so you need to figure out why LDAP isn't running. It's the first service that gets brought up as part of the upgrade process.

[mattvogt]

Originally Posted by quanah

LDAP should be running at the point you're at, so you need to figure out why LDAP isn't running. It's the first service that gets brought up as part of the upgrade process.

Thanks for the direction. I'm pouring through the logs, looking for any clues as to why the LDAP didn't start.

What I see, as it goes through its progressions of upgrade

5.0.20 --> 6.0.0_BETA1 - this goes without errors (updating schema, ldap [shutdowns, startups, checks, etc.])
6.0.0_BETA1 --> 6.0.0_BETA2 this completes without errors
6.0.0_BETA2 -->6.0.0_RC1 as soon as this starts, I get java errors with almost every command in the setup script:

Tue Dec 15 13:06:55 2009 Updating from 6.0.0_RC1
Tue Dec 15 13:06:55 2009 *** Running as zimbra user: zmjava com.zimbra.common.localconfig.LocalConfigUpgrade --bug 37842 --bug
 37844 --bug 37802 --tag .pre.6.0.3_GA
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more

these errors continue for a few pages then this:

Tue Dec 15 13:06:58 2009 *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -u soap_max_in_memory_buffer_size 2> /dev/n
ull
Tue Dec 15 13:06:58 2009 Updating from 6.0.0_RC2
Tue Dec 15 13:06:58 2009 Updating from 6.0.0_GA
Tue Dec 15 13:06:58 2009 Updating from 6.0.1_GA
Tue Dec 15 13:06:58 2009 Updating from 6.0.2_GA
Tue Dec 15 13:06:58 2009 *** Running as zimbra user: zmjava com.zimbra.cs.account.ldap.upgrade.LdapUpgrade -b 41000 -v
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more

Followed shortly by this:

Tue Dec 15 13:07:03 2009 Updating from 6.0.3_GA
Tue Dec 15 13:07:03 2009 Updating global config and COS's with attributes introduced after 5.0.20_GA...
Tue Dec 15 13:07:03 2009 *** Running as zimbra user: zmjava com.zimbra.cs.account.ldap.upgrade.LdapUpgrade -b 27075 -v 5.0.20_
GA
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more

which goes on for a bit and ends with this:

Tue Dec 15 13:07:06 2009 failed.
Tue Dec 15 13:07:06 2009 Stopping ldap...
Tue Dec 15 13:07:06 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap stop
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more
Caused by: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' referenced
        at com.zimbra.common.localconfig.LocalConfig.expandOnce(LocalConfig.java:105)
        at com.zimbra.common.localconfig.LocalConfig.expand(LocalConfig.java:118)
        at com.zimbra.common.localconfig.LocalConfig.expandAll(LocalConfig.java:333)
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:181)
        at com.zimbra.common.localconfig.LocalConfig.readConfig(LocalConfig.java:347)
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:352)
        ... 1 more
Killing slapd with pid 7826 done.
Tue Dec 15 13:07:11 2009 done.
Tue Dec 15 13:07:16 2009 Upgrade complete.

Tue Dec 15 13:07:16 2009 Getting installed packages
Tue Dec 15 13:07:17 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Tue Dec 15 13:07:17 2009 Checking ldap status....
Tue Dec 15 13:07:17 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more
Caused by: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' referenced
        at com.zimbra.common.localconfig.LocalConfig.expandOnce(LocalConfig.java:105)
        at com.zimbra.common.localconfig.LocalConfig.expand(LocalConfig.java:118)
        at com.zimbra.common.localconfig.LocalConfig.expandAll(LocalConfig.java:333)
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:181)
        at com.zimbra.common.localconfig.LocalConfig.readConfig(LocalConfig.java:347)
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:352)
        ... 1 more
Tue Dec 15 13:07:17 2009 not running.
Tue Dec 15 13:07:17 2009 Running bdb db_recover...
Tue Dec 15 13:07:17 2009 *** Running as zimbra user: /opt/zimbra/bdb/bin/db_recover -h /opt/zimbra/data/ldap/hdb/db
Tue Dec 15 13:07:17 2009 done.
Tue Dec 15 13:07:17 2009 Running zmldapapplyldif...
Tue Dec 15 13:07:17 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
mkdir : No such file or directory at /opt/zimbra/libexec/zmldapapplyldif line 42
Tue Dec 15 13:07:21 2009 failed.
Tue Dec 15 13:07:21 2009 Checking ldap status....
Tue Dec 15 13:07:21 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
Exception in thread "main" java.lang.ExceptionInInitializerError
        at com.zimbra.common.localconfig.Main.main(Main.java:106)
Caused by: java.lang.RuntimeException: com.zimbra.common.localconfig.ConfigException: null valued key 'postfix_version' refere
nced
        at com.zimbra.common.localconfig.LocalConfig.(LocalConfig.java:356)
        ... 1 more

The part that caught my eye (which may be a red herring) was:

Tue Dec 15 13:07:17 2009 Running zmldapapplyldif...
Tue Dec 15 13:07:17 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
mkdir : No such file or directory at /opt/zimbra/libexec/zmldapapplyldif line 42
Tue Dec 15 13:07:21 2009 failed.
Tue Dec 15 13:07:21 2009 Checking ldap status....

Line 42 of /opt/zimbra/libexec/zmldapapplyldif is:

if (!-d $zimbra_tmp_directory) {
  File::Path::mkpath("$zimbra_tmp_directory");
}

"FILE" refers to /opt/zimbra/zimbramon/lib/FILE, but there's no 'Path' file or folder, nor the 'mkpath' command.

I think I'll probably open a support ticket at this point. Thankfully it's VM on a test machine so I can rollback to a snapshot.

[quanah]

You need to fix your localconfig.xml to remove any references to postfix_version

[mattvogt]

Originally Posted by quanah

You need to fix your localconfig.xml to remove any references to postfix_version

I knew it was something simple. There were lots and lots of references to postfix_version. But they've been there for many an upgrade (we have postfix running on the backend Zimbra install), so why would this cause problems now? I noticed after the upgrade was completely done, all of those references were deleted. Is this a bug?

In any case, THANK YOU!