Results 1 to 7 of 7

Thread: Migrate Zimbra 6.0.8 NE to a new Server Failed

Threaded View

  1. #1
    Join Date
    Sep 2009
    Posts
    9
    Rep Power
    6

    Default Migrate Zimbra 6.0.8 NE to a new Server Failed

    Hello ,

    My Zimbra install was running great during 10 month.
    I receive a new server to dissmis my old Zimbra Server an migrate to the new server.
    I use the method from this Zimbra Blog page :

    Moving ZCS to Another Server » Zimbra :: Blog

    I copy the same configuration than the OLD server

    Ubuntu LTS 8.04
    Bind9 (Split DNS)
    /etc/network/interface
    /etc/hostname
    /et/hosts
    /ets/resolv.conf

    But at the end of the procedure the server don't start and i had the next result :
    zmcontrol status
    Code:
    Host nxtview.loc
    	antispam                Running
    	antivirus               Running
    	convertd                Running
    	ldap                    Running
    	logger                  Running
    	mailbox                 Stopped
    		mysql.server is not running.
    	memcached               Running
    	mta                     Running
    	snmp                    Running
    	spell                   Running
    	stats                   Stopped

    He i am going to past all the config files and log message.

    su - zimbra

    Code:
    Release 6.0.8_GA_2661.UBUNTU8 UBUNTU8 NETWORK edition.
    cat /etc/hosts

    Code:
    127.0.0.1       localhost.localdomain   localhost
    192.168.1.12     mta.nxtview.loc       mta
    cat /etc/resolv.conf

    Code:
    search nxtview.loc
    nameserver 127.0.0.1
    dig nxtview.com mx
    Code:
    ; <<>> DiG 9.4.2-P2.1 <<>> nxtview.com mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63257
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;nxtview.com.			IN	MX
    
    ;; ANSWER SECTION:
    nxtview.com.		86400	IN	MX	10 mta.nxtview.com.
    
    ;; AUTHORITY SECTION:
    nxtview.com.		86400	IN	NS	mta.nxtview.com.
    
    ;; ADDITIONAL SECTION:
    mta.nxtview.com.	86400	IN	A	192.168.1.12
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Sat Nov 13 21:38:50 2010
    ;; MSG SIZE  rcvd: 79
    dig nxtview.com any

    Code:
    ; <<>> DiG 9.4.2-P2.1 <<>> nxtview.com any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3732
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;nxtview.com.			IN	ANY
    
    ;; ANSWER SECTION:
    nxtview.com.		86400	IN	SOA	mta.nxtview.com. dguevara.nxtview.com. 13112010 604800 86400 2419200 604800
    nxtview.com.		86400	IN	NS	mta.nxtview.com.
    nxtview.com.		86400	IN	MX	10 mta.nxtview.com.
    nxtview.com.		86400	IN	A	192.168.1.12
    
    ;; ADDITIONAL SECTION:
    mta.nxtview.com.	86400	IN	A	192.168.1.12
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Sat Nov 13 21:38:08 2010
    ;; MSG SIZE  rcvd: 140
    host `hostname`

    Code:
    mta.nxtview.loc has address 192.168.1.12
    Logs are :

    tail -f /opt/zimbra/log/zmmtaconfig.log
    Code:
    Sat Nov 13 21:40:07 2010  Watchdog: service antivirus status is OK.
    tail -f /opt/zimbra/log/clamd.log

    Code:
    Wed Nov 10 17:47:32 2010 -> SelfCheck: Database status OK.
    tail --line=400 /opt/zimbra/log/mailbox.log

    Code:
    java.net.ConnectException
    MESSAGE: Connection refused
    
    STACKTRACE:
    
    java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    	at java.net.Socket.connect(Socket.java:529)
    	at java.net.Socket.connect(Socket.java:478)
    	at java.net.Socket.<init>(Socket.java:375)
    	at java.net.Socket.<init>(Socket.java:218)
    	at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:256)
    	at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:271)
    	at com.mysql.jdbc.Connection.createNewIO(Connection.java:2921)
    	at com.mysql.jdbc.Connection.<init>(Connection.java:1555)
    	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)
    	at java.sql.DriverManager.getConnection(DriverManager.java:582)
    	at java.sql.DriverManager.getConnection(DriverManager.java:154)
    	at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)
    	at com.zimbra.cs.db.DbPool$ZimbraConnectionFactory.createConnection(DbPool.java:239)
    	at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
    	at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
    	at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
    	at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:309)
    	at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:293)
    	at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.java:198)
    	at com.zimbra.cs.db.DbPool.startup(DbPool.java:189)
    	at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:156)
    	at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:123)
    	at com.zimbra.soap.SoapServlet.init(SoapServlet.java:125)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    	at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
    	at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)
    	at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
    	at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
    	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
    	at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    	at org.mortbay.jetty.handler.DebugHandler.doStart(DebugHandler.java:127)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    	at org.mortbay.jetty.Server.doStart(Server.java:224)
    	at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServer.java:158)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at org.mortbay.start.Main.invokeMain(Main.java:194)
    	at org.mortbay.start.Main.start(Main.java:534)
    	at org.mortbay.start.Main.start(Main.java:441)
    	at org.mortbay.start.Main.main(Main.java:119)
    tail --line=400 /opt/zimbra/log/mysql_error.log

    Code:
    101113 21:32:41  mysqld started
    InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 18 row operations to undo
    InnoDB: Trx id counter is 0 6962176
    Error: rec is NULL pointer
    101113 21:32:41InnoDB: Assertion failure in thread 3082978992 in file rem0rec.c line 394
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
    InnoDB: about forcing recovery.
    101113 21:32:41 - mysqld got signal 11 ;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    We will try our best to scrape up some info that will hopefully help diagnose
    the problem, but since we have already crashed, something is definitely wrong
    and this may fail.
    
    key_buffer_size=0
    read_buffer_size=1048576
    max_used_connections=0
    max_connections=110
    threads_connected=0
    It is possible that mysqld could use up to 
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225280 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    
    thd=(nil)
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    Cannot determine thread, fp=0xbfb8a248, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    0x81a6088
    0x83ea5eb
    0x8315a26
    0x83013cb
    0x828a14c
    0x827e662
    0x81a54c8
    0x81aa667
    0xb7c40450
    0x8101e61
    New value of fp=(nil) failed sanity check, terminating stack trace!
    Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
    stack trace is much more helpful in diagnosing the problem, so please do 
    resolve it
    The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    information that should help you find out what is causing the crash.
    101113 21:32:41  mysqld ended
    tail --line=400 /opt/zimbra/log/myslow.log

    Code:
    /opt/zimbra/mysql/libexec/mysqld, Version: 5.0.90-log (Source distribution). started with:
    Tcp port: 7306  Unix socket: /opt/zimbra/db/mysql.sock
    Last edited by danisam; 11-14-2010 at 07:19 AM.

Similar Threads

  1. My Zimbra Server crashed this morning...
    By glitch23 in forum Administrators
    Replies: 3
    Last Post: 04-07-2008, 01:28 PM
  2. zmperditionctl start asking for password
    By k7sle in forum Administrators
    Replies: 32
    Last Post: 02-20-2008, 10:13 AM
  3. zmtlsctl give LDAP error
    By sourcehound in forum Administrators
    Replies: 5
    Last Post: 03-11-2007, 03:48 PM
  4. Replies: 8
    Last Post: 02-27-2007, 03:10 AM
  5. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 12:00 PM

Posting Permissions

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