cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Witwicki <>
Subject Database/Cloudstack management cluster issue?
Date Thu, 03 May 2018 15:16:43 GMT

When there is a DB node failure and the database briefly disconnects, the following entry
keeps appearing in the cloudstack-management.log until the management service is restarted.
All Cloudstack operations still function - starting and stopping an instance for example

Centos 7

3 CS management servers
3 active/active mariadb galera cluster - loadbalanced 1 active 2 standby

2018-05-02 09:27:40,685 ERROR [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-64ee96a9)
(logid:d15e998c) Unexpected exception in cluster heartbeat
java.lang.RuntimeException: No database selected for the transaction
        at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
        at com.sun.proxy.$Proxy202.update(Unknown Source)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable$
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask.runAndReset(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: No database selected for the transaction
        ... 26 more

Kind Regards,

[Oakford Internet Services]<>
Adam Witwicki | Hosted Systems Specialist
01380 710278 /<>
Oakford Internet Services Office: 01380 888088
10 Prince Maurice Court, Devizes, Wiltshire. SN10 2RT<><>

Disclaimer Notice:
This email has been sent by Oakford Technology Limited, while we have checked this e-mail
and any attachments for viruses, we can not guarantee that they are virus-free. You must therefore
take full responsibility for virus checking.
This message and any attachments are confidential and should only be read by those to whom
they are addressed. If you are not the intended recipient, please contact us, delete the message
from your computer and destroy any copies. Any distribution or copying without our prior permission
is prohibited.
Internet communications are not always secure and therefore Oakford Technology Limited does
not accept legal responsibility for this message. The recipient is responsible for verifying
its authenticity before acting on the contents. Any views or opinions presented are solely
those of the author and do not necessarily represent those of Oakford Technology Limited.
Registered address: Oakford Technology Limited, 10 Prince Maurice Court, Devizes, Wiltshire.
SN10 2RT.
Registered in England and Wales No. 5971519

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message