[ovirt-users] report option gone missing
Yedidyah Bar David
didi at redhat.com
Mon Nov 23 06:35:31 UTC 2015
On Sun, Nov 22, 2015 at 9:20 PM, Rik Theys <Rik.Theys at esat.kuleuven.be> wrote:
> Hi,
>
> I was able to resolve my issue by adding the reports.cer file to the
> /etc/pki/ovirt-engine/.truststore file. It seems the certificate got
> updated by an engine update but was not added automatically to the
> truststore.
Thanks for the report!
Please open a bug about this, attach relevant logs (including engine setup
logs and yum.log), and try to describe the exact flow leading to this.
Thanks again,
--
Didi
>
> Regards,
>
> Rik
>
> --
> Rik Theys
> System Engineer
> KU Leuven - Dept. Elektrotechniek (ESAT)
> Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
> +32(0)16/32.11.07
> ----------------------------------------------------------------
> <<Any errors in spelling, tact or fact are transmission errors>>
>
> On Sun, 22 Nov 2015, Shirly Radco wrote:
>
>> Hi Rik,
>>
>> The ovirt-engine-dwhd process is responsible for collecting the data from
>> the engine to the oviry_engine_history database where samples data is stored
>> and then aggregated to Hourly and daily.
>>
>> If this service is running and there are no errors in the log then you
>> should be able to see up to date data in the statistics tables in the
>> history database (They end with samples/hourly/daily).
>>
>> Please check these table are up to date.
>>
>> http://www.ovirt.org/Ovirt_DWH
>>
>>
>> The ovirt-engine-reportsd is the service of the reports server. If it is
>> running and it is configured with a FQDN you should be able to log in
>> through http://FQDN:8090/jasperserver/
>>
>> If you want to remove the reports you can just run
>>
>> $yum remove ovirt-engine-reports
>>
>> and run
>> $ engine-setup
>>
>> and when you install it again
>> $ yum install ovirt-engine-reports
>>
>> run again
>> $ engine-setup
>>
>> to configure the reports.
>>
>>
>> http://www.ovirt.org/Ovirt_Reports
>>
>> Please let me know how it goes.
>>
>> Best regards,
>> ---
>> Shirly Radco
>> BI Software Engineer
>> Red Hat Israel Ltd.
>>
>>
>> ----- Original Message -----
>>>
>>> From: "Rik Theys" <Rik.Theys at esat.kuleuven.be>
>>> To: users at ovirt.org
>>> Sent: Thursday, November 19, 2015 5:35:52 PM
>>> Subject: Re: [ovirt-users] report option gone missing
>>>
>>> Hi,
>>>
>>> I was able to login on the ovirt-engine-reports web application as
>>> 'admin' but don't see any reports there.
>>>
>>> What is the procedure to fully remove the reporting from the system and
>>> start anew? Will a remove of the package automatically clean up the
>>> databases and such?
>>>
>>> Rik
>>>
>>> On 11/19/2015 04:25 PM, Rik Theys wrote:
>>>>
>>>> Hi,
>>>>
>>>> At some point I had the oVirt reporting configured on my engine and it
>>>> worked. I had a "reports" option in the menu and could generate
>>>> reports for various resources.
>>>>
>>>> At some point I've noticed that the "reports" option was no longer
>>>> there but did not have time to investigate. I believe it happened when
>>>> I migrated the engine host from CentOS 6 to 7 using engine-backup and
>>>> restore.
>>>>
>>>> How can I debug this?
>>>>
>>>> In the ovirt-engine-dwh log I used to see the following error:
>>>>
>>>> Exception in component tJDBCRollback_4
>>>> org.postgresql.util.PSQLException: FATAL: terminating connection due
>>>> to administrator command
>>>> at
>>>>
>>>> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
>>>> at
>>>>
>>>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
>>>> at
>>>>
>>>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>>>> at
>>>>
>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:793)
>>>> at
>>>>
>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.rollback(AbstractJdbc2Connection.java:846)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.tJDBCRollback_4Process(HistoryETL.java:2079)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.tJDBCRollback_3Process(HistoryETL.java:1997)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.tJDBCRollback_2Process(HistoryETL.java:1882)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.tJDBCRollback_1Process(HistoryETL.java:1767)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.tPostjob_1Process(HistoryETL.java:1647)
>>>> at
>>>>
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.runJobInTOS(HistoryETL.java:10785)
>>>> at
>>>> ovirt_engine_dwh.historyetl_3_5.HistoryETL.main(HistoryETL.java:10277)
>>>> 2015-11-19
>>>> 15:42:02|rza8ri|rza8ri|rza8ri|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java
>>>> Exception|tJDBCRollback_4|org.postgresql.util.PSQLException:FATAL: term
>>>>
>>>> But after rebooting the engine host it now only lists 'Service Started'.
>>>>
>>>> The ovirt-engine-reportsd is also running.
>>>>
>>>> Which of these two processes (reportsd vs dwhd) is generating the
>>>> reports (and showing it in the engine admin interface)?
>>>>
>>>> In /var/log/ovirt-engine-reports, the reports.log file is empty, the
>>>> server.log reports Deployed ovirt-engine-reports.war as the last line
>>>> (without any obvious errors). Only jasperserver.log shows:
>>>>
>>>> 015-11-19 15:41:53,304 ERROR DiskStorageFactory,MSC service thread
>>>> 1-2:948 - Could not flush disk cache. Initial cause was
>>>> /tmp/dataSnapshots/snapshot%0043ontents.index (No such file or
>>>> directory)
>>>> java.io.FileNotFoundException:
>>>> /tmp/dataSnapshots/snapshot%0043ontents.index (No such file or
>>>> directory)
>>>> at java.io.FileOutputStream.open(Native Method)
>>>> at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
>>>> at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
>>>> at
>>>>
>>>> net.sf.ehcache.store.disk.DiskStorageFactory$IndexWriteTask.call(DiskStorageFactory.java:1120)
>>>> at
>>>>
>>>> net.sf.ehcache.store.disk.DiskStorageFactory.unbind(DiskStorageFactory.java:946)
>>>> at
>>>> net.sf.ehcache.store.disk.DiskStore.dispose(DiskStore.java:616)
>>>> at
>>>>
>>>> net.sf.ehcache.store.FrontEndCacheTier.dispose(FrontEndCacheTier.java:521)
>>>> at net.sf.ehcache.Cache.dispose(Cache.java:2473)
>>>> at net.sf.ehcache.CacheManager.shutdown(CacheManager.java:1446)
>>>> at
>>>>
>>>> org.springframework.cache.ehcache.EhCacheManagerFactoryBean.destroy(EhCacheManagerFactoryBean.java:134)
>>>> at
>>>>
>>>> org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:211)
>>>> at
>>>>
>>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:498)
>>>> at
>>>>
>>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:474)
>>>> at
>>>>
>>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:442)
>>>> at
>>>>
>>>> org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1066)
>>>> at
>>>>
>>>> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1040)
>>>> at
>>>>
>>>> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:988)
>>>> at
>>>>
>>>> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:541)
>>>> at
>>>>
>>>> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:142)
>>>> at
>>>>
>>>> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489)
>>>> at
>>>> org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999)
>>>> at
>>>>
>>>> org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:108)
>>>> at
>>>>
>>>> org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
>>>> at
>>>>
>>>> org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
>>>> at
>>>>
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> at
>>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>>
>>>> I have no idea on how to proceed debugging this. How is the reporting
>>>> connected to the engine?
>>>>
>>>> Rik
>>>>
>>>>
>>>
>>>
>>> --
>>> Rik Theys
>>> System Engineer
>>> KU Leuven - Dept. Elektrotechniek (ESAT)
>>> Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
>>> +32(0)16/32.11.07
>>> ----------------------------------------------------------------
>>> <<Any errors in spelling, tact or fact are transmission errors>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>
More information about the Users
mailing list