Results 1 to 2 of 2

Thread: Debian - Upgrade from 4.5.6

Threaded View

  1. #1
    Join Date
    Sep 2007
    Posts
    13
    Rep Power
    8

    Default Debian - Upgrade from 4.5.6 to 5.0.1

    Hello,

    I am having some issues trying to upgrade from 4.5.6 to the current 5.0.1. I am using the open source version. I am running debian etch. Here's my log files from the first attempted upgrade:

    Code:
    Operations logged to /tmp/zmsetup.01192008-000557.log
    Getting installed packages
    Getting local config zimbra_server_hostname
    Getting local config ldap_url
    zimbra_server_hostname contained in ldap_url checking ldap status
    Checking ldap status.
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    Starting ldap...
    *** Running as zimbra user: /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data
    *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    slapd running pid: 8289
    done.
    Getting installed services from ldap
    checking isEnabled zimbra-core
    zimbra-core not in enabled cache
    enabled packages 
    zimbra_server_hostname contained in ldap_url checking ldap status
    Checking ldap status.
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    slapd running pid: 8289
    slapd already running.
    Getting enabled services from ldap
    Marking zimbra-core as installed. Services for zimbra-core will be enabled.
    Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
    Setting defaults...
    Setting local config zimbra_java_home to /opt/zimbra/java
    *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_java_home='/opt/zimbra/java' 2> /dev/null
    checking isEnabled zimbra-cluster
    zimbra-cluster not in enabled cache
    enabled packages zimbra-logger zimbra-store zimbra-mta zimbra-core zimbra-apache zimbra-snmp zimbra-ldap zimbra-spell
    zimbra_server_hostname contained in ldap_url checking ldap status
    Checking ldap status.
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    slapd running pid: 8289
    slapd already running.
    Getting enabled services from ldap
    Marking zimbra-core as installed. Services for zimbra-core will be enabled.
    Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
    checking isEnabled zimbra-store
    zimbra-store is enabled
    checking isEnabled zimbra-ldap
    zimbra-ldap is enabled
    checking isEnabled zimbra-store
    zimbra-store is enabled
    checking isEnabled zimbra-mta
    zimbra-mta is enabled
    done.
    Upgrading from 4.5.6_GA_1044 to 5.0.1_GA_1902
    Stopping zimbra services
    Verifying /opt/zimbra/conf/my.cnf
    Starting mysql
    Starting logger mysql
    This appears to be 4.5.6_GA
    Redolog Version: 1.12 New Redolog Version: 1.21
    Schema upgrade required
    Running /opt/zimbra/libexec/scripts/migrate20070306-Pop3MessageUid.pl
    Sat Jan 19 00:07:00 2008: Verified schema version 36.
    Sat Jan 19 00:07:06 2008: Verified schema version 36.
    Sat Jan 19 00:07:06 2008: Updating DB schema version from 36 to 37.
    Running /opt/zimbra/libexec/scripts/migrate20070606-WidenMetadata.pl
    Sat Jan 19 00:07:10 2008: Verified schema version 37.
    ............
    Sat Jan 19 00:07:27 2008: Verified schema version 37.
    Sat Jan 19 00:07:27 2008: Updating DB schema version from 37 to 38.
    Running /opt/zimbra/libexec/scripts/migrate20070614-BriefcaseFolder.pl
    Sat Jan 19 00:07:29 2008: Verified schema version 38.
    .
    .
    Sat Jan 19 00:07:35 2008: Verified schema version 38.
    Sat Jan 19 00:07:35 2008: Updating DB schema version from 38 to 39.
    Running /opt/zimbra/libexec/scripts/migrate20070627-BackupTime.pl
    Sat Jan 19 00:07:37 2008: Verified schema version 39.
    .
    Sat Jan 19 00:07:39 2008: Verified schema version 39.
    Sat Jan 19 00:07:39 2008: Updating DB schema version from 39 to 40.
    Running /opt/zimbra/libexec/scripts/migrate20070629-IMTables.pl
    Sat Jan 19 00:07:42 2008: Verified schema version 40.
    Sat Jan 19 00:07:43 2008: Verified schema version 40.
    Sat Jan 19 00:07:43 2008: Updating DB schema version from 40 to 41.
    Running /opt/zimbra/libexec/scripts/migrate20070630-LastSoapAccess.pl
    Sat Jan 19 00:07:45 2008: Verified schema version 41.
    Sat Jan 19 00:07:46 2008: Verified schema version 41.
    Sat Jan 19 00:07:46 2008: Updating DB schema version from 41 to 42.
    Running /opt/zimbra/libexec/scripts/migrate20070703-ScheduledTask.pl
    Sat Jan 19 00:07:48 2008: Verified schema version 42.
    Sat Jan 19 00:07:49 2008: Verified schema version 42.
    Sat Jan 19 00:07:49 2008: Updating DB schema version from 42 to 43.
    Running /opt/zimbra/libexec/scripts/migrate20070706-DeletedAccount.pl
    Sat Jan 19 00:07:51 2008: Verified schema version 43.
    Sat Jan 19 00:07:51 2008: Verified schema version 43.
    Sat Jan 19 00:07:51 2008: Updating DB schema version from 43 to 44.
    Running /opt/zimbra/libexec/scripts/migrate20070725-CreateRevisionTable.pl
    Sat Jan 19 00:07:53 2008: Verified schema version 44.
    Sat Jan 19 00:08:00 2008: Verified schema version 44.
    Sat Jan 19 00:08:00 2008: Updating DB schema version from 44 to 45.
    Running /opt/zimbra/libexec/scripts/migrate20070726-ImapDataSource.pl
    Sat Jan 19 00:08:03 2008: Verified schema version 45.
    Sat Jan 19 00:08:11 2008: Verified schema version 45.
    Sat Jan 19 00:08:11 2008: Updating DB schema version from 45 to 46.
    Running /opt/zimbra/libexec/scripts/migrate20070921-ImapDataSourceUidValidity.pl
    Sat Jan 19 00:08:13 2008: Verified schema version 46.
    Sat Jan 19 00:08:20 2008: Verified schema version 46.
    Sat Jan 19 00:08:20 2008: Updating DB schema version from 46 to 47.
    Running /opt/zimbra/libexec/scripts/migrate20070928-ScheduledTaskIndex.pl
    Sat Jan 19 00:08:22 2008: Verified schema version 47.
    Sat Jan 19 00:08:23 2008: Verified schema version 47.
    Sat Jan 19 00:08:23 2008: Updating DB schema version from 47 to 48.
    Running /opt/zimbra/libexec/scripts/migrate20071128-AccountId.pl
    Sat Jan 19 00:08:25 2008: Verified schema version 48.
    Sat Jan 19 00:08:26 2008: Verified schema version 48.
    Sat Jan 19 00:08:26 2008: Updating DB schema version from 48 to 49.
    Running /opt/zimbra/libexec/scripts/migrate20071206-WidenSizeColumns.pl
    Sat Jan 19 00:08:28 2008: Verified schema version 49.
    Sat Jan 19 00:08:42 2008: Verified schema version 49.
    Sat Jan 19 00:08:42 2008: Updating DB schema version from 49 to 50.
    Stopping mysql
    Stopping logger mysql
    Checking ldap status
    Starting ldap
    Checking 3.0.M1
    Checking 3.0.0_M2
    Checking 3.0.0_M3
    Checking 3.0.0_M4
    Checking 3.0.0_GA
    Checking 3.0.1_GA
    Checking 3.1.0_GA
    Checking 3.1.1_GA
    Checking 3.1.2_GA
    Checking 3.1.3_GA
    Checking 3.1.4_GA
    Checking 3.2.0_M1
    Checking 3.2.0_M2
    Checking 4.0.0_RC1
    Checking 4.0.0_GA
    Checking 4.0.1_GA
    Checking 4.0.2_GA
    Checking 4.0.3_GA
    Checking 4.0.4_GA
    Checking 4.0.5_GA
    Checking 4.1.0_BETA1
    Checking 4.5.0_BETA1
    Checking 4.5.0_BETA2
    Checking 4.5.0_RC1
    Checking 4.5.0_RC2
    Checking 4.5.0_GA
    Checking 4.5.1_GA
    Checking 4.5.2_GA
    Checking 4.5.3_GA
    Checking 4.5.4_GA
    Checking 4.5.5_GA
    Checking 4.5.6_GA
    Updating from 4.5.6_GA
    Setting local config upgrade_dummy to 1
    *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e upgrade_dummy='1' 2> /dev/null
    Deleting local config upgrade_dummy
    Getting local config mysql_pidfile
    Checking 4.5.7_GA
    Updating from 4.5.7_GA
    *** Running as zimbra user: /opt/zimbra/bin/zmprov -l -- mcf zimbraHttpNumThreads 100
    [] WARN: local config file `/opt/zimbra/conf/localconfig.xml' is not readable
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    *** Running as zimbra user: /opt/zimbra/bin/zmprov -l -- mcf zimbraHttpSSLNumThreads 50
    [] WARN: local config file `/opt/zimbra/conf/localconfig.xml' is not readable
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    *** Running as zimbra user: /opt/zimbra/bin/zmprov -l -- mcf zimbraMtaMyDestination localhost
    [] WARN: local config file `/opt/zimbra/conf/localconfig.xml' is not readable
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    Migrating amavisd-new to version 2.5.2
    Checking /opt/zimbra/amavisd-new-2.4.3/db
    Migrating amavis-new db from version 2.4.3 to 2.5.2
    Checking /opt/zimbra/amavisd-new-2.4.3/.spamassassin
    Migrating amavis-new .spamassassin from version 2.4.3 to 2.5.2
    Checking /opt/zimbra/amavisd-new-2.4.1/db
    Checking /opt/zimbra/amavisd-new-2.4.1/.spamassassin
    Checking /opt/zimbra/amavisd-new-2.3.3/db
    Checking /opt/zimbra/amavisd-new-2.3.3/.spamassassin
    Checking /opt/zimbra/amavisd-new-2.3.1/db
    Checking /opt/zimbra/amavisd-new-2.3.1/.spamassassin
    Starting mysql
    After that one failed i started reading around on the forums trying to get a fix. In most posts i saw that slapd was still running. So, i checked and indeed it still was running. I killed the process and tryed the upgrade again. Upon trying a second time, i received a totally different error talking about the zimbra hostname not being in ldap_url. Here's the log file from that attempt:

    Code:
    Operations logged to /tmp/zmsetup.01192008-001848.log
    Getting installed packages
    Getting local config zimbra_server_hostname
    Getting local config ldap_url
    zimbra_server_hostname not in ldap_url not starting slapd
    Getting installed services from ldap
    checking isEnabled zimbra-core
    zimbra-core not in enabled cache
    enabled packages 
    zimbra_server_hostname not in ldap_url not starting slapd
    Getting enabled services from ldap
    Marking zimbra-core as installed. Services for zimbra-core will be enabled.
    Marking zimbra-ldap as installed. Services for zimbra-ldap will be enabled.
    Marking zimbra-store as installed. Services for zimbra-store will be enabled.
    Marking zimbra-mta as installed. Services for zimbra-mta will be enabled.
    Marking zimbra-snmp as installed. Services for zimbra-snmp will be enabled.
    Marking zimbra-logger as installed. Services for zimbra-logger will be enabled.
    Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
    Marking zimbra-spell as installed. Services for zimbra-spell will be enabled.
    Setting defaults...
    Setting local config zimbra_java_home to /opt/zimbra/java
    *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_java_home='/opt/zimbra/java' 2> /dev/null
    checking isEnabled zimbra-cluster
    zimbra-cluster not in enabled cache
    enabled packages zimbra-logger zimbra-store zimbra-mta zimbra-core zimbra-apache zimbra-snmp zimbra-ldap zimbra-spell
    zimbra_server_hostname not in ldap_url not starting slapd
    Getting enabled services from ldap
    Marking zimbra-core as installed. Services for zimbra-core will be enabled.
    Marking zimbra-ldap as installed. Services for zimbra-ldap will be enabled.
    Marking zimbra-store as installed. Services for zimbra-store will be enabled.
    Marking zimbra-mta as installed. Services for zimbra-mta will be enabled.
    Marking zimbra-snmp as installed. Services for zimbra-snmp will be enabled.
    Marking zimbra-logger as installed. Services for zimbra-logger will be enabled.
    Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
    Marking zimbra-spell as installed. Services for zimbra-spell will be enabled.
    checking isEnabled zimbra-store
    zimbra-store is enabled
    checking isEnabled zimbra-ldap
    zimbra-ldap is enabled
    checking isEnabled zimbra-store
    zimbra-store is enabled
    checking isEnabled zimbra-mta
    zimbra-mta is enabled
    done.
    Upgrading from 4.5.6_GA_1044 to 5.0.1_GA_1902
    Stopping zimbra services
    Stop failed - exiting
    UPGRADE FAILED - exiting
    I tried several time after this to rerun the upgrade, but i receive the exact same error every time i run it.

    How can i rectify this issue? What should i set the ldap_url to to get past this?

    Thanks!!
    Last edited by magikman; 01-19-2008 at 07:41 AM.

Similar Threads

  1. Replies: 5
    Last Post: 12-04-2007, 04:40 PM
  2. Replies: 7
    Last Post: 11-02-2007, 11:30 PM
  3. Trying to upgrade 4.5.6 to 4.5.7 and bombing completely
    By dwmtractor in forum Installation
    Replies: 2
    Last Post: 10-08-2007, 07:41 PM
  4. Replies: 6
    Last Post: 07-04-2007, 08:36 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •