Announcement

Collapse
No announcement yet.

database upgrade problem when going from OX 6.8 to 6.10

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    database upgrade problem when going from OX 6.8 to 6.10

    Hello,

    I'm upgrading OX on a Debian Etch system and once I have upgraded all OX packages, the system fails to start with the following error:

    WARNING: DBP-0012 Category=5 Message=Connection used for 2001 milliseconds. exceptionID=187223021-1
    DBP-0012 Category=5 Message=Connection used for 2001 milliseconds. exceptionID=187223021-1
    at com.openexchange.database.internal.DBPoolingExcept ionFactory.createException(DBPoolingExceptionFacto ry.java:76)
    at com.openexchange.database.internal.DBPoolingExcept ionFactory.createException(DBPoolingExceptionFacto ry.java:62)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:139)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:143)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:155)
    at com.openexchange.database.DBPoolingExceptionCodes. create(DBPoolingExceptionCodes.java:186)
    at com.openexchange.database.internal.ConnectionPool$ ConnectionLifecycle.validate(ConnectionPool.java:3 21)
    at com.openexchange.pooling.ReentrantLockPool.back(Re entrantLockPool.java:256)
    at com.openexchange.pooling.ReentrantLockPool.back(Re entrantLockPool.java:222)
    at com.openexchange.database.internal.DatabaseService Impl.back(DatabaseServiceImpl.java:222)
    at com.openexchange.database.internal.DatabaseService Impl.back(DatabaseServiceImpl.java:356)
    at com.openexchange.databaseold.Database.back(Databas e.java:225)
    at com.openexchange.groupware.update.SchemaStoreImpl. loadSchema(SchemaStoreImpl.java:423)
    at com.openexchange.groupware.update.SchemaStoreImpl. getSchema(SchemaStoreImpl.java:125)
    at com.openexchange.groupware.update.SchemaStore.getS chema(SchemaStore.java:142)
    at com.openexchange.groupware.update.UpdaterImpl.getS chema(UpdaterImpl.java:135)
    at com.openexchange.groupware.update.UpdaterImpl.isLo cked(UpdaterImpl.java:90)
    at com.openexchange.groupware.contexts.impl.CachingCo ntextStorage$1.load(CachingContextStorage.java:159 )
    at com.openexchange.groupware.contexts.impl.CachingCo ntextStorage$1.load(CachingContextStorage.java:167 )
    at com.openexchange.cache.dynamic.impl.Refresher.refr esh(Refresher.java:162)
    at com.openexchange.groupware.contexts.impl.ContextRe loader.<init>(ContextReloader.java:79)
    at com.openexchange.groupware.contexts.impl.CachingCo ntextStorage.loadContext(CachingContextStorage.jav a:172)
    at com.openexchange.groupware.contexts.impl.ContextSt orage.getContext(ContextStorage.java:115)
    at com.openexchange.tools.webdav.OXServlet.addSession (OXServlet.java:342)
    at com.openexchange.tools.webdav.OXServlet.doAuth(OXS ervlet.java:189)
    at com.openexchange.webdav.PermissionServlet.service( PermissionServlet.java:86)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.doServletService(AJPv13RequestHandlerImpl.java: 429)
    at com.openexchange.ajp13.AJPv13Request.response(AJPv 13Request.java:128)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.createResponse(AJPv13RequestHandlerImpl.java:28 2)
    at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.c reateResponse(AJPv13ConnectionImpl.java:189)
    at com.openexchange.ajp13.najp.AJPv13Task.run(AJPv13T ask.java:258)
    at java.util.concurrent.Executors$RunnableAdapter.cal l(Executors.java:417)
    at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:269)
    at java.util.concurrent.FutureTask.run(FutureTask.jav a:123)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)
    Sep 9, 2009 10:04:30 AM com.openexchange.tools.webdav.OXServlet doAuth
    SEVERE: CTX-0007 Category=4 Message=Updating database ... Try again later. exceptionID=187223021-2
    CTX-0007 Category=4 Message=Updating database ... Try again later. exceptionID=187223021-2
    at com.openexchange.groupware.contexts.impl.ContextSt orage.getContext(ContextStorage.java:117)
    at com.openexchange.tools.webdav.OXServlet.addSession (OXServlet.java:342)
    at com.openexchange.tools.webdav.OXServlet.doAuth(OXS ervlet.java:189)
    at com.openexchange.webdav.PermissionServlet.service( PermissionServlet.java:86)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.doServletService(AJPv13RequestHandlerImpl.java: 429)
    at com.openexchange.ajp13.AJPv13Request.response(AJPv 13Request.java:128)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.createResponse(AJPv13RequestHandlerImpl.java:28 2)
    at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.c reateResponse(AJPv13ConnectionImpl.java:189)
    at com.openexchange.ajp13.najp.AJPv13Task.run(AJPv13T ask.java:258)
    at java.util.concurrent.Executors$RunnableAdapter.cal l(Executors.java:417)
    at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:269)
    at java.util.concurrent.FutureTask.run(FutureTask.jav a:123)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)



    Any idea on the cause of this problem?

    Thank you in advance for your help.

    Michaël

    PS: whole log is attached
    Attached Files
    Tags: None
  • #2
    Just read the error within the stacktrace:

    Code:
    [...] Updating database ... Try again later. [...]
    The new version requires some database updates which will be done with the first access to the database.

    Comment

    • #3
      Dear Carsten,

      I appreciate your quick reply. I am a bit surprised though that the update would take more than 20 minutes. Is such a long time really expected, knowing that under the /varl/lib/mysql directory there are only 48MB of data?

      Kind regards,

      Michaël

      Comment

      • #4
        That update should take some milliseconds on such a small installation.

        Does that mean, that this error comes with every try to login?
        It's quite likely _not_ related to the server startup.

        What exactly does not work - if at all -?

        Comment

        • #5
          This is correct. I get the error for every login, which means that I cannot login on the server.

          I get the OX landing page though, with the right login banner and the proper OX version displayed.

          Is there any log that would help determine where the problem is coming from?

          Michaël

          Comment

          • #6
            Hi,

            could you please post the result of the following mysql query at your ox database?

            Code:
            SELECT * FROM version;
            Thanks

            Comment

            • #7
              Sure, here you are:

              mysql> SELECT * FROM version;
              +---------+--------+---------------+------------------+----------+
              | version | locked | gw_compatible | admin_compatible | server |
              +---------+--------+---------------+------------------+----------+
              | 34 | 1 | 1 | 1 | oxserver |
              +---------+--------+---------------+------------------+----------+

              Michaël

              Comment

              • #8
                Seems like the database has been locked and is still version 34 which is 6.8. Have you restarted the groupware after the error message occured? To try again, please enter

                Code:
                UPDATE version SET locked=0;
                After that, try to login again and please keep an eye on the logfile if they contain any severe error message.

                Greetings

                Comment

                • #9
                  ... and that works just great

                  Thank you for your very efficient and appreciated support!

                  Kind regards,

                  Michaël

                  Comment

                  • #10
                    Not a problem, but we're interested in the initial cause of this problem. Do you still have log files from your first upgrade try?

                    Comment

                    Previous template Next
                    Working...
                    X