ox-updates vs. mysql-replication (master-master)

[881822]

Hello,

our situation is, that we habe two instances of open-xchange, each using own hardware and mysql-dbs. These db’s are replicated by mysql master-master-replication. So far, so good.

The issue is, that in case of ox-updates the database of the first instance will be updated on first login. My understanding of the replication is, that this database-update will also be replicated to the other machine…

But on first login on the other ox-instance (after the same ox-update) the affected db will be updated again. This (second) update causes problems, that induce to the loss of replication. This behaviour is redroduceable. The mysqld.log on both machines say, that the replication stopped because of errors, which have to solved to be able to start replication again.

It seems, that the db-update on the second machine causes the problem. Is it possible to avoid this (unnecessary?) db-update? How is it triggered?

On does anyone have another suggestion?

[881822]

no Idea anyone?

[Martin Heiland]

Hi,

i'm not sure if i get it right, but if the database updates applied to Master A does not get replicated to Master B, why is this an OX problem? Of course those subsequent issues are not nice but triggered by the initial problem (imho).

The updatetasks lock a database schema and the groupware can only access it after the lock has been removed by finishing the update tasks.

Greetings

[881822]

After the update was made on the second server I get the following error-message while trying to login:

Fehlermeldung: Datenbank wird aktualisiert... Bitte später erneut versuchen. (CTX-0007, 2049174924-25)

Normaly it it's only shown once and then everything is allright, but in my case it's permanently there an the login fails ...

The output of open-xchange.log.0 is:

Mar 16, 2010 11:23:50 PM com.openexchange.authentication.imap.impl.IMAPAuthentication handleLoginInfo
INFO: Imap authentication for user david successful on host localhost:143
Mar 16, 2010 11:23:50 PM com.openexchange.login.internal.LoginPerformer logLoginRequest
INFO: Login:david IP:88.152.40.123 AuthID:3c8b0f28-d00d-4578-92ce-1a3b81c7547e Agent:Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2) Gecko/20100115 Fi
refox/3.6 Client:com.openexchange.ox6.gui.dhtml(6.16.0 Rev4) Interface:HTTP_JSON Failed.
Mar 16, 2010 11:23:50 PM com.openexchange.ajax.Login doLogin
SEVERE: CTX-0007 Category=4 Message=Updating database ... Try again later. exceptionID=2049174924-27
CTX-0007 Category=4 Message=Updating database ... Try again later. exceptionID=2049174924-27
        at com.openexchange.login.internal.LoginPerformer.doLogin(LoginPerformer.java:172)
        at com.openexchange.ajax.Login.doLogin(Login.java:340)
        at com.openexchange.ajax.Login.doGet(Login.java:138)
        at com.openexchange.ajax.Login.doPost(Login.java:318)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
        at com.openexchange.ajax.AJAXServlet.service(AJAXServlet.java:384)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
        at com.openexchange.ajp13.najp.AJPv13RequestHandlerImpl.doServletService(AJPv13RequestHandlerImpl.java:504)
        at com.openexchange.ajp13.AJPv13Request.response(AJPv13Request.java:129)
        at com.openexchange.ajp13.najp.AJPv13RequestHandlerImpl.createResponse(AJPv13RequestHandlerImpl.java:316)
        at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.createResponse(AJPv13ConnectionImpl.java:207)
        at com.openexchange.ajp13.najp.AJPv13Task.call(AJPv13Task.java:346)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.runTask(CustomThreadPoolExecutor.java:737)
        at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.run(CustomThreadPoolExecutor.java:763)
        at java.lang.Thread.run(Thread.java:636)
Caused by: CTX-0007 Category=4 Message=Updating database ... Try again later. exceptionID=2049174924-26
        at com.openexchange.groupware.contexts.impl.ContextStorage.getContext(ContextStorage.java:114)
        at com.openexchange.login.internal.LoginPerformer.findContext(LoginPerformer.java:190)
        at com.openexchange.login.internal.LoginPerformer.doLogin(LoginPerformer.java:116)
        ... 16 more

Any idea how to fix this error?

[Martin Heiland]

Hi,

please check the content of the "versions" table, if locked is "1", you could set it to "0" manually. Please make sure you have backups and no update task is currently running.

Greetings