Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
> On May 24, 2017, at 6:25 AM, supp...@jac-properties.com wrote: > > Which makes sense seeing as that's what Red Hat officially supports. It just > made sense for our infrastructure to put it on our postgres cluster that is > running 9.5.x. Unfortunately things like this happen sometimes when running > a slightly unsupported infrastructure. We have done the same thing. Be aware that it makes upgrades a PITA - the installer is picky about the version, as well as various PG config options and refuses to run if you don't satisfy it. I hacked the installer, because that was easier than standing up an ancient Postgres just for the upgrade in our environment; YMMV. -j ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
> > Le 24 mai 2017 à 16:26, Yedidyah Bar David a écrit : >> >> A good solution usually used by java app is to provide the need jars. That >> the purpose of maven like tools. >> > > We can also simply add to the spec file '< 9.3' or something like that, > until we fix the code to support newer. > > You are more than welcome to open a bug for this! Done: https://bugzilla.redhat.com/show_bug.cgi?id=1455262 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
On Wed, May 24, 2017 at 5:04 PM, Fabrice Bacchella wrote: > > Le 24 mai 2017 à 15:25, supp...@jac-properties.com a écrit : > > Which makes sense seeing as that's what Red Hat officially supports. It > just made sense for our infrastructure to put it on our postgres cluster > that is running 9.5.x. Unfortunately things like this happen sometimes when > running a slightly unsupported infrastructure. > > > Is this worth putting in an RFE? Support for postgresql-jdbc 42+ and > postgresql 9.5+ Martin is already working on 9.5 support for oVirt 4.2. No idea about jdbc. > > A good solution usually used by java app is to provide the need jars. That > the purpose of maven like tools. > We can also simply add to the spec file '< 9.3' or something like that, until we fix the code to support newer. You are more than welcome to open a bug for this! Best, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
> Le 24 mai 2017 à 15:25, supp...@jac-properties.com a écrit : > > Which makes sense seeing as that's what Red Hat officially supports. It just > made sense for our infrastructure to put it on our postgres cluster that is > running 9.5.x. Unfortunately things like this happen sometimes when running > a slightly unsupported infrastructure. > > > > Is this worth putting in an RFE? Support for postgresql-jdbc 42+ and > postgresql 9.5+ > A good solution usually used by java app is to provide the need jars. That the purpose of maven like tools. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
Which makes sense seeing as that's what Red Hat officially supports. It just made sense for our infrastructure to put it on our postgres cluster that is running 9.5.x. Unfortunately things like this happen sometimes when running a slightly unsupported infrastructure. Is this worth putting in an RFE? Support for postgresql-jdbc 42+ and postgresql 9.5+ Logan > On May 24, 2017 at 5:24 AM Martin Perina wrote: > > Yes, postgresql 9.2 JDBC drivers are the only working and supported JDBC > drivers. Also please be aware that we test and only PostgreSQL 9.2 for > oVirt, so there may be other issues with newer versions. > > On Tue, May 23, 2017 at 11:15 PM, Yedidyah Bar David mailto:d...@redhat.com > wrote: > > > > On Wed, May 24, 2017 at 12:06 AM, mailto:supp...@jac-properties.com > wrote: > > > Wow, that looks almost exactly like what we're seeing. > > > > > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, > > restarting ovirt-engine and rerunning engine-setup produces the same error > > messages. > > > > > > > Please try 9.2. Thanks! > > > > > Logan > > > > > >> On May 23, 2017 at 3:39 PM Yedidyah Bar David > mailto:d...@redhat.com > wrote: > > >> > > >> > > >> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn > > mailto:supp...@jac-properties.com > wrote: > > >> > Hi > > >> > > > >> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to > > 9.5.7. We > > >> > restarted ovirt-engine between 9.5.4 and it worked as > > expected. After we > > >> > updated to 9.5.7 we have started to get postgres errors in > > engine.log and a > > >> > 404 error in the browser when we try to start ovirt-engine. > > >> > > > >> > Updates were done on client and server to keep them in sync. > > >> > > > >> > The error is complaining about a missing function, but we can > > verify that > > >> > the function exists in the database. We've also restored > > engine and > > >> > ovirt_engine_history from a backup at 8am this morning when it > > was working > > >> > and before we upgraded to 9.5.7 with no apparent help and run > > engine-setup > > >> > afterwards, still no luck. > > >> > > > >> > 2017-05-23 15:07:48,418 INFO > > [org.ovirt.engine.core.dal.dbbroker.DbFacade] > > >> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade > > >> > 2017-05-23 15:07:48,480 INFO > > [org.ovirt.engine.core.bll.Backend] > > >> > (ServerService Thread Pool -- 51) [] Start initializing Backend > > >> > 2017-05-23 15:07:48,502 ERROR > > >> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] > > (ServerService > > >> > Thread Pool -- 46) [] Error initializing: > > PreparedStatementCallback; bad SQL > > >> > grammar [select * from getallmacpoolrangesbymacpoolid()]; > > nested exception > > >> > is org.postgresql.util.PSQL > > >> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() > > does not exist > > >> > Hint: No function matches the given name and argument types. > > You might need > > >> > to add explicit type casts. > > >> > Position: 16 > > >> > 2017-05-23 15:07:48,517 ERROR > > [org.ovirt.engine.core.bll.Backend] > > >> > (ServerService Thread Pool -- 51) [] Error during > > initialization: > > >> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable > > to invoke > > >> > public void > > >> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > > >> > ate() on > > >> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 > > >> >at > > >> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > >> >at > > >> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > >> >at > > >> > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) > > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > >> >at > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) > > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > >> >at > > >> > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > >> >at > > >> > > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultCo
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
Thanks, that's what we've put in place too Logan > > On May 24, 2017 at 2:20 AM Fabrice Bacchella > wrote: > > In /etc/yum.repos.d/pgdg-94-centos.repo, I added : > > [pgdg94] > ... > exclude=postgresql-jdbc > > > > > > Le 23 mai 2017 à 23:06, supp...@jac-properties.com a écrit : > > > > Wow, that looks almost exactly like what we're seeing. > > > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, > > restarting ovirt-engine and rerunning engine-setup produces the same error > > messages. > > > > Logan > > > > > > > > > > On May 23, 2017 at 3:39 PM Yedidyah Bar David > > > wrote: > > > > > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn > > > wrote: > > > > > > > > > > > > > > Hi > > > > > > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and > > > > then to 9.5.7. We > > > > restarted ovirt-engine between 9.5.4 and it worked as > > > > expected. After we > > > > updated to 9.5.7 we have started to get postgres errors > > > > in engine.log and a > > > > 404 error in the browser when we try to start > > > > ovirt-engine. > > > > > > > > Updates were done on client and server to keep them in > > > > sync. > > > > > > > > The error is complaining about a missing function, but > > > > we can verify that > > > > the function exists in the database. We've also > > > > restored engine and > > > > ovirt_engine_history from a backup at 8am this morning > > > > when it was working > > > > and before we upgraded to 9.5.7 with no apparent help > > > > and run engine-setup > > > > afterwards, still no luck. > > > > > > > > 2017-05-23 15:07:48,418 INFO > > > > [org.ovirt.engine.core.dal.dbbroker.DbFacade] > > > > (ServerService Thread Pool -- 51) [] Initializing the > > > > DbFacade > > > > 2017-05-23 15:07:48,480 INFO > > > > [org.ovirt.engine.core.bll.Backend] > > > > (ServerService Thread Pool -- 51) [] Start initializing > > > > Backend > > > > 2017-05-23 15:07:48,502 ERROR > > > > > > > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService > > > > Thread Pool -- 46) [] Error initializing: > > > > PreparedStatementCallback; bad SQL > > > > grammar [select * from > > > > getallmacpoolrangesbymacpoolid()]; nested exception > > > > is org.postgresql.util.PSQL > > > > Exception: ERROR: function > > > > getallmacpoolrangesbymacpoolid() does not exist > > > > Hint: No function matches the given name and argument > > > > types. You might need > > > > to add explicit type casts. > > > > Position: 16 > > > > 2017-05-23 15:07:48,517 ERROR > > > > [org.ovirt.engine.core.bll.Backend] > > > > (ServerService Thread Pool -- 51) [] Error during > > > > initialization: > > > > org.jboss.weld.exceptions.WeldException: WELD-49: > > > > Unable to invoke > > > > public void > > > > > > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > > > > ate() on > > > > > > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 > > > > at > > > > > > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
Yes, postgresql 9.2 JDBC drivers are the only working and supported JDBC drivers. Also please be aware that we test and only PostgreSQL 9.2 for oVirt, so there may be other issues with newer versions. On Tue, May 23, 2017 at 11:15 PM, Yedidyah Bar David wrote: > On Wed, May 24, 2017 at 12:06 AM, wrote: > > Wow, that looks almost exactly like what we're seeing. > > > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, > restarting ovirt-engine and rerunning engine-setup produces the same error > messages. > > > > Please try 9.2. Thanks! > > > Logan > > > >> On May 23, 2017 at 3:39 PM Yedidyah Bar David wrote: > >> > >> > >> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn < > supp...@jac-properties.com> wrote: > >> > Hi > >> > > >> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. > We > >> > restarted ovirt-engine between 9.5.4 and it worked as expected. > After we > >> > updated to 9.5.7 we have started to get postgres errors in engine.log > and a > >> > 404 error in the browser when we try to start ovirt-engine. > >> > > >> > Updates were done on client and server to keep them in sync. > >> > > >> > The error is complaining about a missing function, but we can verify > that > >> > the function exists in the database. We've also restored engine and > >> > ovirt_engine_history from a backup at 8am this morning when it was > working > >> > and before we upgraded to 9.5.7 with no apparent help and run > engine-setup > >> > afterwards, still no luck. > >> > > >> > 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal. > dbbroker.DbFacade] > >> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade > >> > 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] > >> > (ServerService Thread Pool -- 51) [] Start initializing Backend > >> > 2017-05-23 15:07:48,502 ERROR > >> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] > (ServerService > >> > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; > bad SQL > >> > grammar [select * from getallmacpoolrangesbymacpoolid()]; nested > exception > >> > is org.postgresql.util.PSQL > >> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not > exist > >> > Hint: No function matches the given name and argument types. You > might need > >> > to add explicit type casts. > >> > Position: 16 > >> > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] > >> > (ServerService Thread Pool -- 51) [] Error during initialization: > >> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to > invoke > >> > public void > >> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > >> > ate() on > >> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@ > 3a35f461 > >> >at > >> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoke > r.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoke > r.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct( > BasicInjectionTarget.java:126) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at org.jboss.weld.bean.ManagedBean.create( > ManagedBean.java:162) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.bean.ContextualInstanceStrategy$ > DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.bean.ContextualInstanceStrategy$ > ApplicationScopedContextualInstanceStrategy.get( > ContextualInstanceStrategy.java:141) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.bean.ContextualInstance.get( > ContextualInstance.java:50) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.manager.BeanManagerImpl.getReference( > BeanManagerImpl.java:742) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance( > InstanceImpl.java:189) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at > >> > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) > >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >> >at org.ovirt.engine.core.bll.Backend.loadService(Backend. > java:301) > >> > [bll.jar:] > >> >at org.ovirt.engine.core.bll.Backend.initialize(Backend. > java:212) > >> > [bll.jar:] > >> >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) > >> > [bll.jar:] > >> >at sun.reflect.Na
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
In /etc/yum.repos.d/pgdg-94-centos.repo, I added : [pgdg94] ... exclude=postgresql-jdbc > Le 23 mai 2017 à 23:06, supp...@jac-properties.com a écrit : > > Wow, that looks almost exactly like what we're seeing. > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting > ovirt-engine and rerunning engine-setup produces the same error messages. > > Logan > >> On May 23, 2017 at 3:39 PM Yedidyah Bar David wrote: >> >> >> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn >> wrote: >>> Hi >>> >>> We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. We >>> restarted ovirt-engine between 9.5.4 and it worked as expected. After we >>> updated to 9.5.7 we have started to get postgres errors in engine.log and a >>> 404 error in the browser when we try to start ovirt-engine. >>> >>> Updates were done on client and server to keep them in sync. >>> >>> The error is complaining about a missing function, but we can verify that >>> the function exists in the database. We've also restored engine and >>> ovirt_engine_history from a backup at 8am this morning when it was working >>> and before we upgraded to 9.5.7 with no apparent help and run engine-setup >>> afterwards, still no luck. >>> >>> 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] >>> (ServerService Thread Pool -- 51) [] Initializing the DbFacade >>> 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] >>> (ServerService Thread Pool -- 51) [] Start initializing Backend >>> 2017-05-23 15:07:48,502 ERROR >>> [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService >>> Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL >>> grammar [select * from getallmacpoolrangesbymacpoolid()]; nested exception >>> is org.postgresql.util.PSQL >>> Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist >>> Hint: No function matches the given name and argument types. You might need >>> to add explicit type casts. >>> Position: 16 >>> 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] >>> (ServerService Thread Pool -- 51) [] Error during initialization: >>> org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke >>> public void >>> org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre >>> ate() on >>> org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 >>> at >>> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at >>> org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) >>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >>> at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301) >>> [bll.jar:] >>> at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212) >>> [bll.jar:] >>> at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) >>> [bll.jar:] >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> [rt.jar:1.8.0_131] >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>> [rt.jar:1.8.0_131] >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> [rt.jar:1.8.0_131] >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> [rt.jar:1.8.0_131] >>> at >>> org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecyc
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
I downgraded the jdbc to 9.2.1002 and it's working again. Thank you for your help! The full setup is as such in case it helps anyone in the future: OS: CentOS 7.3.1611 Backend: Ceph via Cinder oVirt: 4.0.6.3 Postgres is remote and 9.5.7 on client and server Postgres jdbc: 9.2.1002 Logan > > On May 23, 2017 at 4:15 PM Yedidyah Bar David wrote: > > On Wed, May 24, 2017 at 12:06 AM, wrote: > > > > > > Wow, that looks almost exactly like what we're seeing. > > > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, > > restarting ovirt-engine and rerunning engine-setup produces the same error > > messages. > > > > > > Please try 9.2. Thanks! > > > > > > Logan > > > > > > > > > > On May 23, 2017 at 3:39 PM Yedidyah Bar David > > > wrote: > > > > > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn > > > wrote: > > > > > > > > > > > > > > Hi > > > > > > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and > > > > then to 9.5.7. We > > > > restarted ovirt-engine between 9.5.4 and it worked as > > > > expected. After we > > > > updated to 9.5.7 we have started to get postgres errors > > > > in engine.log and a > > > > 404 error in the browser when we try to start > > > > ovirt-engine. > > > > > > > > Updates were done on client and server to keep them in > > > > sync. > > > > > > > > The error is complaining about a missing function, but > > > > we can verify that > > > > the function exists in the database. We've also > > > > restored engine and > > > > ovirt_engine_history from a backup at 8am this morning > > > > when it was working > > > > and before we upgraded to 9.5.7 with no apparent help > > > > and run engine-setup > > > > afterwards, still no luck. > > > > > > > > 2017-05-23 15:07:48,418 INFO > > > > [org.ovirt.engine.core.dal.dbbroker.DbFacade] > > > > (ServerService Thread Pool -- 51) [] Initializing the > > > > DbFacade > > > > 2017-05-23 15:07:48,480 INFO > > > > [org.ovirt.engine.core.bll.Backend] > > > > (ServerService Thread Pool -- 51) [] Start initializing > > > > Backend > > > > 2017-05-23 15:07:48,502 ERROR > > > > > > > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService > > > > Thread Pool -- 46) [] Error initializing: > > > > PreparedStatementCallback; bad SQL > > > > grammar [select * from > > > > getallmacpoolrangesbymacpoolid()]; nested exception > > > > is org.postgresql.util.PSQL > > > > Exception: ERROR: function > > > > getallmacpoolrangesbymacpoolid() does not exist > > > > Hint: No function matches the given name and argument > > > > types. You might need > > > > to add explicit type casts. > > > > Position: 16 > > > > 2017-05-23 15:07:48,517 ERROR > > > > [org.ovirt.engine.core.bll.Backend] > > > > (ServerService Thread Pool -- 51) [] Error during > > > > initialization: > > > > org.jboss.weld.exceptions.WeldException: WELD-49: > > > > Unable to invoke > > > > public void > > > > > > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > > > > ate() on > > > > > > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 > > > > at > > > > > > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > > > > at > > > > > > > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanc
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
On Wed, May 24, 2017 at 12:06 AM, wrote: > Wow, that looks almost exactly like what we're seeing. > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting > ovirt-engine and rerunning engine-setup produces the same error messages. > Please try 9.2. Thanks! > Logan > >> On May 23, 2017 at 3:39 PM Yedidyah Bar David wrote: >> >> >> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn >> wrote: >> > Hi >> > >> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. We >> > restarted ovirt-engine between 9.5.4 and it worked as expected. After we >> > updated to 9.5.7 we have started to get postgres errors in engine.log and a >> > 404 error in the browser when we try to start ovirt-engine. >> > >> > Updates were done on client and server to keep them in sync. >> > >> > The error is complaining about a missing function, but we can verify that >> > the function exists in the database. We've also restored engine and >> > ovirt_engine_history from a backup at 8am this morning when it was working >> > and before we upgraded to 9.5.7 with no apparent help and run engine-setup >> > afterwards, still no luck. >> > >> > 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] >> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade >> > 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] >> > (ServerService Thread Pool -- 51) [] Start initializing Backend >> > 2017-05-23 15:07:48,502 ERROR >> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService >> > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad >> > SQL >> > grammar [select * from getallmacpoolrangesbymacpoolid()]; nested exception >> > is org.postgresql.util.PSQL >> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist >> > Hint: No function matches the given name and argument types. You might >> > need >> > to add explicit type casts. >> > Position: 16 >> > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] >> > (ServerService Thread Pool -- 51) [] Error during initialization: >> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke >> > public void >> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre >> > ate() on >> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 >> >at >> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at >> > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) >> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >> >at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301) >> > [bll.jar:] >> >at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212) >> > [bll.jar:] >> >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) >> > [bll.jar:] >> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> > [rt.jar:1.8.0_131] >> >at >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> > [rt.jar:1.8.0_131] >> >at >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> > [rt.jar:1.8.0_131] >> >at java.lang.reflect.Method.invoke(Method.java:498) >> > [rt.jar:1.8.0_131] >> >at >> > org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(Ma
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
Wow, that looks almost exactly like what we're seeing. Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting ovirt-engine and rerunning engine-setup produces the same error messages. Logan > On May 23, 2017 at 3:39 PM Yedidyah Bar David wrote: > > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn > wrote: > > Hi > > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. We > > restarted ovirt-engine between 9.5.4 and it worked as expected. After we > > updated to 9.5.7 we have started to get postgres errors in engine.log and a > > 404 error in the browser when we try to start ovirt-engine. > > > > Updates were done on client and server to keep them in sync. > > > > The error is complaining about a missing function, but we can verify that > > the function exists in the database. We've also restored engine and > > ovirt_engine_history from a backup at 8am this morning when it was working > > and before we upgraded to 9.5.7 with no apparent help and run engine-setup > > afterwards, still no luck. > > > > 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] > > (ServerService Thread Pool -- 51) [] Initializing the DbFacade > > 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] > > (ServerService Thread Pool -- 51) [] Start initializing Backend > > 2017-05-23 15:07:48,502 ERROR > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService > > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL > > grammar [select * from getallmacpoolrangesbymacpoolid()]; nested exception > > is org.postgresql.util.PSQL > > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist > > Hint: No function matches the given name and argument types. You might need > > to add explicit type casts. > > Position: 16 > > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] > > (ServerService Thread Pool -- 51) [] Error during initialization: > > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke > > public void > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > > ate() on > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 > >at > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at > > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] > >at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301) > > [bll.jar:] > >at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212) > > [bll.jar:] > >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) > > [bll.jar:] > >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > [rt.jar:1.8.0_131] > >at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > > [rt.jar:1.8.0_131] > >at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > [rt.jar:1.8.0_131] > >at java.lang.reflect.Method.invoke(Method.java:498) > > [rt.jar:1.8.0_131] > >at > > org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) > >at > > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > >at > > org.jboss.invocat
Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn wrote: > Hi > > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. We > restarted ovirt-engine between 9.5.4 and it worked as expected. After we > updated to 9.5.7 we have started to get postgres errors in engine.log and a > 404 error in the browser when we try to start ovirt-engine. > > Updates were done on client and server to keep them in sync. > > The error is complaining about a missing function, but we can verify that > the function exists in the database. We've also restored engine and > ovirt_engine_history from a backup at 8am this morning when it was working > and before we upgraded to 9.5.7 with no apparent help and run engine-setup > afterwards, still no luck. > > 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] > (ServerService Thread Pool -- 51) [] Initializing the DbFacade > 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] > (ServerService Thread Pool -- 51) [] Start initializing Backend > 2017-05-23 15:07:48,502 ERROR > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL > grammar [select * from getallmacpoolrangesbymacpoolid()]; nested exception > is org.postgresql.util.PSQL > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist > Hint: No function matches the given name and argument types. You might need > to add explicit type casts. > Position: 16 > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] > (ServerService Thread Pool -- 51) [] Error during initialization: > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke > public void > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre > ate() on > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 >at > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] >at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301) > [bll.jar:] >at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212) > [bll.jar:] >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) > [bll.jar:] >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [rt.jar:1.8.0_131] >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [rt.jar:1.8.0_131] >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [rt.jar:1.8.0_131] >at java.lang.reflect.Method.invoke(Method.java:498) > [rt.jar:1.8.0_131] >at > org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) >at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) >at > org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) >at > org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70) > [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] >at > org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:117) > [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] >at > org.jboss.as.weld.ejb.Jsr299BindingsInterc
[ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4
Hi We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7. We restarted ovirt-engine between 9.5.4 and it worked as expected. After we updated to 9.5.7 we have started to get postgres errors in engine.log and a 404 error in the browser when we try to start ovirt-engine. Updates were done on client and server to keep them in sync. The error is complaining about a missing function, but we can verify that the function exists in the database. We've also restored engine and ovirt_engine_history from a backup at 8am this morning when it was working and before we upgraded to 9.5.7 with no apparent help and run engine-setup afterwards, still no luck. 2017-05-23 15:07:48,418 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] (ServerService Thread Pool -- 51) [] Initializing the DbFacade 2017-05-23 15:07:48,480 INFO [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 51) [] Start initializing Backend 2017-05-23 15:07:48,502 ERROR [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL grammar [select * from getallmacpoolrangesbymacpoolid()]; nested exception is org.postgresql.util.PSQL Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 16 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 51) [] Error during initialization: org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke public void org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre ate() on org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461 at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301) [bll.jar:] at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212) [bll.jar:] at org.ovirt.engine.core.bll.Backend.create(Backend.java:159) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_131] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:117) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:103) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorConte