Results 1 to 10 of 10

Thread: Migrating from NE to NE

  1. #1
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default Migrating from NE to NE

    Helloo,

    Since we have encountered some harware problems with our server, we plan to move our mail server to another machine. The only procedure I found for moving from one mailserver to another is the one for opensource -> NE. We are currently running a RHEL5 server and ZCS 4.5.9 NE. The new environmemnt will be similar (RHEL5/ZCS 4.5.9). Is it safe to apply the same procedure for moving from NE to NE??

    Thank you.

    The procedure for moving from open source to NE:

    Network Edition Moving from Open Source to Network Edition ZCS - Zimbra :: Wiki

  2. #2
    Klug's Avatar
    Klug is offline Moderator
    Join Date
    Mar 2006
    Location
    Beaucaire, France
    Posts
    2,292
    Rep Power
    13

  3. #3
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default

    Thanks!! I'll give it a try today.

  4. #4
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default

    Not good...

    here's what i get when trying to run the setup on the new machine (i ran zmfixperms prior to that):


    Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
    HOSTNAME=zimbra.pentalog.fr
    LDAPHOST=
    LDAPPORT=
    SNMPTRAPHOST=
    SMTPSOURCE=
    SMTPDEST=
    SNMPNOTIFY=0
    SMTPNOTIFY=0
    LDAPROOTPW=zimbra
    LDAPZIMBRAPW=zimbra
    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...Restoring backup schedule...done
    Operations logged to /tmp/zmsetup.log.8887
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    Setting defaults...Done
    Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
    Checking for port conflicts
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    Done

    Main menu


    1) Hostname: zimbra.pentalog.fr
    2) Ldap master host: zimbra.pentalog.fr
    3) Ldap port: 389
    4) Ldap password: set
    ** 5) TimeZone: UNSET
    6) zimbra-ldap: Enabled
    7) zimbra-store: Enabled
    +Create Admin User: no
    +Enable automated spam training: yes
    ******* +Spam training user: UNSET
    ******* +Non-spam(Ham) training user: UNSET
    +Global Documents Account: wiki@zimbra.pentalog.fr
    +SMTP host: zimbra.pentalog.fr
    ******* +Web server HTTP port: UNSET
    ******* +Web server HTTPS port: UNSET
    +Web server mode: mixed
    +Enable POP/IMAP proxy: no
    ******* +IMAP server port: UNSET
    ******* +IMAP server SSL port: UNSET
    ******* +POP server port: UNSET
    ******* +POP server SSL port: UNSET
    +Use spell check server: yes
    +Spell server URL: http://zimbra.pentalog.fr:7780/aspell.php

    8) zimbra-mta: Enabled
    9) zimbra-snmp: Enabled
    10) zimbra-logger: Enabled
    11) zimbra-spell: Enabled
    12) Enable default backup schedule: yes
    r) Start servers after configuration yes
    s) Save config to file
    x) Expand menu
    q) Quit


    after configuring everything:


    Main menu

    1) Hostname: zimbra.pentalog.fr
    2) Ldap master host: zimbra.pentalog.fr
    3) Ldap port: 389
    4) Ldap password: set
    5) TimeZone: (GMT+01.00) Brussels / Copenhagen / Madrid / Paris
    6) zimbra-ldap: Enabled
    +Create Domain: no

    7) zimbra-store: Enabled
    +Create Admin User: no
    +Enable automated spam training: yes
    +Spam training user: spam.xjooz.tx@zimbra.pentalog.fr
    +Non-spam(Ham) training user: ham.tbgouq7uk@zimbra.pentalog.fr
    +Global Documents Account: wiki@zimbra.pentalog.fr
    +SMTP host: zimbra.pentalog.fr
    +Web server HTTP port: 80
    +Web server HTTPS port: 443
    +Web server mode: mixed
    +Enable POP/IMAP proxy: no
    +IMAP server port: 143
    +IMAP server SSL port: 993
    +POP server port: 110
    +POP server SSL port: 995
    +Use spell check server: yes
    +Spell server URL: http://zimbra.pentalog.fr:7780/aspell.php

    8) zimbra-mta: Enabled
    +MTA Auth host: zimbra.pentalog.fr
    +Enable Spamassassin: yes
    +Enable Clam AV: yes
    +Notification address for AV alerts: admin@zimbra.pentalog.fr

    9) zimbra-snmp: Enabled
    +Enable SNMP notifications: yes
    +SNMP Trap hostname: zimbra.pentalog.fr
    +Enable SMTP notifications: yes
    +SMTP Source email address: admin@zimbra.pentalog.fr
    +SMTP Destination email address: admin@zimbra.pentalog.fr

    10) zimbra-logger: Enabled
    11) zimbra-spell: Enabled

    12) Enable default backup schedule: yes
    c) Collapse menu
    r) Start servers after configuration yes
    s) Save config to file
    q) Quit

    Address unconfigured (**) items or correct ldap configuration (? - help)

    No "a" for apply. What's to be done??

    If needed, i can post the installation log.

  5. #5
    Klug's Avatar
    Klug is offline Moderator
    Join Date
    Mar 2006
    Location
    Beaucaire, France
    Posts
    2,292
    Rep Power
    13

    Default

    Are your host file and IP address correctly setup ?
    (DNS should not have changed).

  6. #6
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default

    yes, both of them are.

    Here's something strange that i found in the installation log:

    Preparing packages for installation...
    zimbra-ldap-4.5.9_GA_1454.RHEL5-20071016194233
    find: /opt/zimbra/lib/ext-common: No such file or directory
    find: /opt/zimbra/lib/ext-common: No such file or directory
    chown: cannot access `/opt/zimbra/dspam-*': No such file or directory
    chown: cannot access `/opt/zimbra/dspam/*': No such file or directory
    chown: cannot access `/opt/zimbra/httpd-*': No such file or directory
    chown: cannot access `/opt/zimbra/httpd/*': No such file or directory
    chown: cannot access `/opt/zimbra/logger/mysql-*': No such file or directory
    chown: cannot access `/opt/zimbra/logger/mysql/*': No such file or directory
    chown: cannot access `/opt/zimbra/mysql-*': No such file or directory
    chown: cannot access `/opt/zimbra/mysql/*': No such file or directory
    chown: cannot access `/opt/zimbra/net-snmp-*': No such file or directory
    chown: cannot access `/opt/zimbra/snmp/*': No such file or directory
    chown: cannot access `/opt/zimbra/amavisd/sbin': No such file or directory
    chown: cannot access `/opt/zimbra/tomcat/bin': No such file or directory
    chmod: cannot access `/opt/zimbra/postfix/conf/postfix-script': No such file or directory
    chmod: cannot access `/opt/zimbra/postfix/conf/post-install': No such file or directory

    COMMAND: cat /opt/zimbra/.saveconfig/backup.save | xargs zmschedulebackup -R

    ERROR: Invalid schedule: -a

    Schedule regular backups

    Usage: zmshedulebackup [-q|-s|-A|-R|-F|-D] [-t <target>] [-z] [schedule] [schedule...]
    -q: query (default command) - prints existing schedule
    -s: save schedule (format applicable for restoring)
    -F: flush - remove current schedule (cancel all scheduled backups)
    -A: append - adds specified backup to current schedule
    -R: replace - replace current schedule with specified schedule
    -D: Default - replace current schedule with DEFAULT schedule
    -z: compress - compress email blobs with zip
    -t: target - backup target location (default is /opt/zimbra/backup)
    -a: account - account specific (default is all)


    schedule: <i|f|d arg> <time specifier>
    i: incremental backup (not needed in Auto-Grouped backup mode)
    f: full backup
    d <arg>: delete backups. <arg> is n{d|m|y}
    time specifier: crontab style time specifier, QUOTED. See crontab(5)
    Fields are:
    minute 0-59
    hour 0-23
    day of month 1-31
    month 1-12
    day of week 0-7 (0 or 7 is Sun, or use names)

    Default schedule in Standard backup mode is:
    f 0 1 * * 6
    i 0 1 * * 0-5
    d 1m 0 0 * * *

    Default schedule in Auto-Grouped backup mode is:
    f 0 1 * * 0-6
    d 1m 0 0 * * *


    The specified directories exists and have the appropiate permissions. Haven't got a clue of what's happening.

    Inside /etc/sudousers i have

    #
    # Disable "ssh hostname sudo <cmd>", because it will show the password in clear.
    # You have to run "ssh -t hostname sudo <cmd>".
    #
    #Defaults requiretty

  7. #7
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    20

    Default

    I've seen this before if the installer can't verify the ldap_url, by attempting to bind. So I think either the ldap server, port, or password might not be configured correctly - or something else is on the ldap port.
    As also exhibited by your:
    Quote Originally Posted by mannes
    ldap startup failed with exit code 256
    Setting defaults from ldap...ERROR: service.FAILURE (system failure:getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
    on this 2nd/new box:
    ps aux | grep zimbra
    ps auxww | grep zimbra
    ps auxww | grep slapd
    kill -9 pid# any remaining
    lsof -i :389
    netstat -a
    Anything on it?

    If you think it's the password - you can try:
    zmldappasswd --root newpass
    zmldappasswd newpass

  8. #8
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default

    Still no luck whatsoever. I'll give it a try with the OSS-NE procedure for a NE to a NE.

  9. #9
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    20

    Default

    That procedure is a little different.

    You can use the disaster recovery changing server method etc: /docs/ne/latest/administration_guide/10_Backup_Restore.13.1.html

    Feel free to open a support ticket and someone can give you a hand.

  10. #10
    mannes is offline Active Member
    Join Date
    Sep 2007
    Posts
    36
    Rep Power
    7

    Default

    Ok, I managed to recover the backups from the old server and I used them to get the new box up and running. But I encountered a few problems:

    - the COSs were not rebuilt
    - none of the distribution lists was recreated
    - none of the domain aliases was recreated

    Is this normal?? What's to be done to get them back??

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Migrating domain issue
    By albanach in forum Installation
    Replies: 1
    Last Post: 01-18-2008, 10:35 AM
  2. Migrating from/to Zimbra
    By hardaur in forum Migration
    Replies: 1
    Last Post: 01-17-2008, 10:17 AM
  3. Migrating from sendmail
    By Nutz in forum Migration
    Replies: 2
    Last Post: 04-10-2007, 05:18 AM
  4. Migrating from Communigate Pro?
    By jordandeamattson in forum Administrators
    Replies: 9
    Last Post: 01-25-2007, 04:17 PM
  5. Migrating accounts with zmprov
    By Alfspace in forum Administrators
    Replies: 2
    Last Post: 10-19-2005, 10:41 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
  •