Results 1 to 2 of 2

Thread: error alert after upgrade from 4.5.10 to 5.01

  1. #1
    Join Date
    Oct 2007
    Location
    Massachusetts
    Posts
    76
    Rep Power
    8

    Default error alert after upgrade from 4.5.10 to 5.01

    Below is the alert. I'm checking to see if nothing was damaged but was this supposed to happen?

    Server: bet.norwoodma.gov

    Label: incr-20080123.060007.797
    Type: incremental
    Status: completed (with errors)
    Started: Wed, 2008/01/23 01:00:07.797 EST
    Ended: Wed, 2008/01/23 01:00:54.239 EST
    Redo log sequence range: 0 .. 14
    Number of accounts: 266
    Number of errors: 1


    ERRORS

    system: Detected possible redo log sequence reset; expected sequence 237, but found 0 through 14; To avoid future restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option
    com.zimbra.cs.backup.BackupServiceException: Detected possible redo log sequence reset; expected sequence 237, but found 0 through 14; To avoid future restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option
    Code:backup.REDOLOG_RESET_DETECTED
    at com.zimbra.cs.backup.BackupServiceException.REDOLO G_RESET_DETECTED(BackupServiceException.java:99)
    at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq (Utils.java:456)
    at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.backupRedoLogs(FileBackupTarget.java:1034)
    at com.zimbra.cs.backup.BackupSet.startIncrementalBac kup(BackupSet.java:698)
    at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.startIncrementalBackup(FileBackupTarget.java:837 )
    at com.zimbra.cs.backup.BackupManager.backupIncrement al(BackupManager.java:318)
    at com.zimbra.cs.service.backup.Backup.handleNetworkR equest(Backup.java:143)
    at com.zimbra.cs.service.NetworkDocumentHandler.handl e(Unknown Source)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:148)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
    at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
    at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.Server.handle(Server.java:313)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)

  2. #2
    Join Date
    Oct 2007
    Location
    Massachusetts
    Posts
    76
    Rep Power
    8

    Default found problem

    We use a non-default location for backups. The upgrade did not carry over that fact. In past 2 upgrades it did carry over this bit of configuration.

Similar Threads

  1. Replies: 4
    Last Post: 01-05-2008, 08:45 PM
  2. Where can I get 4.5.10? I need it to upgrade to 5.0
    By mdeneen in forum Administrators
    Replies: 2
    Last Post: 01-02-2008, 10:34 AM
  3. Replies: 5
    Last Post: 12-04-2007, 04:40 PM
  4. Replies: 7
    Last Post: 11-28-2007, 12:49 PM
  5. Zimlet disappear after upgrade to 4.5.10
    By Chadsel Chen in forum Installation
    Replies: 1
    Last Post: 11-26-2007, 06:42 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
  •