Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Migration to 64bit failed - Ubuntu 8.04.4

  1. #1
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default Migration to 64bit failed - Ubuntu 8.04.4

    Started with Ubuntu 8.04.4 x32 NE6.0.8, went to Ubuntu 8.04.4 x64 NE6.0.8, using the instructions at Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki

    First deviation from instructions involves SSL certificates:
    even though this is a 6.0.8, and this server has commercial certificates installed, /opt/zimbra/tomcat/conf/keystore didn't exist. It was upgrade from a 5.x install at least 6 months ago, but it looks like /opt/zimbra/mailboxd/etc/keystore was still in use. I copied it to the same place (/opt/zimbra/mailboxd/etc/keystore) on the new install. Biggest reason was that/opt/zimbra/tomcat doesn't even exist on either box. Hrmm?

    I'm also concerned that this instuction is insufficiently specific - in other words, I'm afraid I've missed something here:

    The postfix certificates (smtp) are /opt/zimbra/conf/smtpd.crt and smtpd.key. If you are using the certificates for nginx, perdition, or ldap (slapd) they are also in /opt/zimbra/conf/; they should normally be identical to the postfix certificate files.
    Here are the errors I get during startup

    Code:
    zimbra@zimbra:/root$ zmcontrol start
    Host zimbra.{mydomain}.com
    	Starting ldap...Done.
    	Starting logger...Failed.
    Starting logswatch...failed.
    
    
    	Starting convertd...Done.
    	Starting mailbox...Failed.
    
    
    	Starting memcached...Done.
    	Starting imapproxy...Done.
    	Starting antispam...Done.
    	Starting antivirus...Done.
    	Starting archiving...Done.
    	Starting snmp...Done.
    	Starting spell...Done.
    	Starting mta...Failed.
    Starting zmmtaconfig...zmmtaconfig is already running.
    postalias: fatal: bad string length 0 < 1: mail_owner = 
    postfix failed to start
    Starting saslauthd...done.
    
    
    	Starting stats...Done.
    So - lets look at mailbox.log

    I think the key piece here is

    Code:
    2010-11-06 21:38:55,841 WARN  [main] [] misc - Could not establish a connection to the database.  Retrying in 5 seconds.
    com.zimbra.common.service.ServiceException: system failure: getting database connection
    ExceptionId:main:1289093935841:c902435d5e8597f5
    Code:service.FAILURE
    so - lets look at zmmysqlstatus

    Code:
    zimbra@zimbra:~/mysql/share/mysql$ zmmysqlstatus 
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock' (2)
    Error while running 'mysql --user=zimbra --password={my mysql password} --database=zimbra --batch --skip-column-names'. at /opt/zimbra/bin/zmmysqlstatus line 248.
    looks related - so now I'll check the mysql password on the old server and make sure it matches this one.

    Interestingly, "zmlocalconfig -s | grep mysql" reveals that they're set to use the same passwords, but that there are some somewhat major differences in the configs.

    OLD 32bit SERVER
    Code:
    zimbra@zimbra-old:/root$ zmlocalconfig  -s | grep mysql
    logger_mysql_bind_address = 
    logger_mysql_data_directory = 
    logger_mysql_directory = 
    logger_mysql_errlogfile = 
    logger_mysql_mycnf = 
    logger_mysql_pidfile = 
    logger_mysql_port = 
    logger_mysql_socket = 
    mysql_bind_address = localhost
    mysql_data_directory = ${zimbra_db_directory}/data
    mysql_directory = ${zimbra_home}/mysql
    mysql_errlogfile = ${zimbra_home}/log/mysql_error.log
    mysql_mycnf = ${zimbra_home}/conf/my.cnf
    mysql_pidfile = ${zimbra_db_directory}/mysql.pid
    mysql_port = 7306
    mysql_root_password = {password}
    mysql_socket = ${zimbra_db_directory}/mysql.sock
    zimbra_logger_mysql_password = 
    zimbra_mysql_connector_maxActive = 100
    zimbra_mysql_password = {password}
    zimbra_mysql_user = zimbra
    NEW 64bit SERVER
    Code:
    zimbra@zimbra:/root$ zmlocalconfig -s | grep mysql
    logger_mysql_bind_address = localhost
    logger_mysql_data_directory = ${zimbra_home}/logger/db/data
    logger_mysql_directory = ${zimbra_home}/logger/mysql
    logger_mysql_errlogfile = ${zimbra_home}/log/logger_mysql_error.log
    logger_mysql_mycnf = ${zimbra_home}/conf/my.logger.cnf
    logger_mysql_pidfile = ${zimbra_home}/logger/db/mysql.pid
    logger_mysql_port = 7307
    logger_mysql_socket = ${zimbra_home}/logger/db/mysql.sock
    mysql_bind_address = localhost
    mysql_data_directory = ${zimbra_db_directory}/data
    mysql_directory = ${zimbra_home}/mysql
    mysql_errlogfile = ${zimbra_home}/log/mysql_error.log
    mysql_mycnf = ${zimbra_home}/conf/my.cnf
    mysql_pidfile = ${zimbra_db_directory}/mysql.pid
    mysql_port = 7306
    mysql_root_password = {password}
    mysql_socket = ${zimbra_db_directory}/mysql.sock
    zimbra_logger_mysql_password = 
    zimbra_mysql_password = {password}
    zimbra_mysql_user = zimbra
    So, in digging around for logs for mysql (something I had a hard time doing since there were none created BECAUSE) I found that i didn't have a my.cnf. Not sure how I made it through a successful installation from scratch without one being created, but I did.

    I've copied it over from the old 32bit machine and things look slightly better. Mailbox started, but mta still hasn't (because its already running? 0^o) - and neither has logger.

    Code:
    zimbra@zimbra:~/log$ zmcontrol start
    Host zimbra.{my domain}.com
    	Starting logger...Failed.
    Starting logswatch...failed.
    
    
    	Starting convertd...Done.
    	Starting mailbox...Done.
    	Starting memcached...Done.
    	Starting imapproxy...Done.
    	Starting antispam...Done.
    	Starting antivirus...Done.
    	Starting archiving...Done.
    	Starting snmp...Done.
    	Starting spell...Done.
    	Starting mta...Failed.
    Starting zmmtaconfig...zmmtaconfig is already running.
    postalias: fatal: bad string length 0 < 1: mail_owner = 
    postfix failed to start
    Starting saslauthd...already running.
    
    
    	Starting stats...Done.
    The UI is accessible and the system apparently working (though who knows how well) so I'm going to post this, but will continue to dig around at why logger won't start, and why the mta would already be running.

    If you have any light to shed on either of these issues (or anything you've seen above that is obviously a problem) please chime in. I'm running out of steam here...

    Best to all and thanks,
    Andy

  2. #2
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    So - localsettings.xml wasn't not entirely populated. I made sure it had the items required in the documentation, but it was missing other things. I backed it up and copied the one over from the old server and postfix became much happier, but zimbra still isn't running right. Once I put my finger on what the problem is even related to, I'll post it. Right now, all I have is this:

    postfix appears to start (and be happy) but when you go to send a message, you get this

    Code:
    com.zimbra.common.service.ServiceException: system failure: Unable to get SMTP session for [com.zimbra.cs.account.ldap.LdapAccount alauppe@{my domain}.com]
    then, just to see if postfix was running right i tried to telnet to port 25 on localhost without luck.

    Code:
    root@zimbra:/opt/zimbra/log# telnet localhost 25
    Trying 127.0.0.1...
    telnet: Unable to connect to remote host: Connection refused
    weird.

  3. #3
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    Looks like a lot of my problem was caused by transport.db being non-existant. I ran postmap on /opt/zimbra/postfix/conf/transport (which contains a whole lot of nothing really...) and it generated transport.db making postfix much happier.

    Then, to fix the logger issue, I actually just had to create /var/log/zimbra-stats.log and give the ownership to zimbra:zimbra.

    Now everything seems to work, but I'm getting the notorious and unfulfilling red "X"'s on the main page in the admin portal. After all this work, I'd like to see green checkboxes.

    In fact, while clicking around to gather data for this post I find that the admin portal isn't particularly usable. Clicking on the server under "Servers" gives me this error - http://j.mp/9fgoX5.

    note, also, that there is no "backups" section in the navbar. Whats going on here do you think? - http://j.mp/bsxWjz

    Since I've got most of the other problems in-hand, I'm going to reboot the server and see how it comes up. Not sure what else to try really...

  4. #4
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    Oh - zmcontrol status gives this

    Code:
    zimbra@zimbra:/root$ zmcontrol status
    Host zimbra.{my domain}.com
    	antispam                Running
    	antivirus               Running
    	archiving               Running
    	convertd                Running
    	imapproxy               Running
    	ldap                    Running
    	logger                  Running
    	mailbox                 Running
    	memcached               Running
    	mta                     Running
    	snmp                    Stopped
    		zmswatch is not running.
    	spell                   Running
    	stats                   Running
    I guess that explains the red X's.

    It appears that there is nothing in localconfig.xml to define the mysql credentials etc for the logger. I'd love some assistance setting this up properly. Also, the Admin UI continutes to run at <100%. In fact, I can't get it to load at all in firefox - it comes up working poorly in Chrome. In FF, I login and I get this - http://j.mp/cvLvXU

    I'm going to bed. Thanks in advance to anyone that is able to help!

    Andy
    Last edited by alauppe; 11-06-2010 at 10:20 PM. Reason: added info

  5. #5
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    A reboot restored stability to the Admin UI, but there is still no backup section in the UI - something I find quite strange.

    I'd love some insight - either from the community or Zimbra; it seems like this migration isn't 100% complete, yet I need to either bring the old system back online or cut over to the new one by the end of today. I'd hate to have to do all this work again a second time, but I'd hate more to have to cut back after new mail has been flowing to the new server.

    What logs and/or configs should I post to give a better idea of whats going on?

    Andy

  6. #6
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    Ok - the Admin UI is not actually stable, it just didn't fail in the same place as last time. This time when I click the name of the server under "Servers" I get this.

    http://j.mp/ahoKNZ

    So I'm going to copy that zimbra_identity file over. Will report back.

    Andy

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,504
    Rep Power
    57

    Default

    Quote Originally Posted by alauppe View Post
    Ok - the Admin UI is not actually stable, it just didn't fail in the same place as last time. This time when I click the name of the server under "Servers" I get this.

    http://j.mp/ahoKNZ
    You've most likely not copied over all the files/folders from your 'old' installation.

    Quote Originally Posted by alauppe View Post
    So I'm going to copy that zimbra_identity file over. Will report back.
    Sounds like a plan.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    After copying the contents of /opt/zimbra/.ssh/ from the old server to the new one, and also /opt/zimbra/ssl/commercial, the Admin UI no longer fails when I click on the server-name under "Servers" but insteads, in "Server Statistics" - http://j.mp/cYIPHu

    Andy

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,504
    Rep Power
    57

    Default

    In Step 3 item 6 of the migration article, did you run the zmfixperms command? I'd suggest you shut-down Zimbra, run that command again and restart the server.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    alauppe is offline Active Member
    Join Date
    Jan 2009
    Posts
    27
    Rep Power
    6

    Default

    Phoenix,

    Thanks for your advice. I did follow Step 3 number 6 when it was called, and again after every other quirk and problem I ran across. I also did it again just now, as you suggested. There is no change in the system's behavior. zmswatch is still not running, and under "Tools" in the Admin UI "Mail Queues" is the only item listed.

    What more information can I provide to paint a fuller picture?

    Thanks for your reply,
    Andy

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 7
    Last Post: 02-13-2013, 02:36 AM
  2. Install Zimbra 6.0.8 x64 on Debian Lenny Fail
    By Titi974 in forum Installation
    Replies: 6
    Last Post: 10-21-2010, 05:47 AM
  3. HOWTO: Ubuntu 64bit Install
    By dijichi2 in forum Installation
    Replies: 12
    Last Post: 07-23-2008, 03:33 PM
  4. Problem with Mail Server - Need help!
    By joeleo in forum Installation
    Replies: 2
    Last Post: 03-04-2008, 12:03 PM
  5. My Zimbra server down ... please help :)
    By frankb in forum Administrators
    Replies: 2
    Last Post: 12-12-2007, 11:29 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
  •