Hi Andrea,
I believe that dwh not working is unrelated to what Liron mentioned.
Please open a bug on ovirt-dwh and attach the dwh log and ovirt_engine_dwh
db dump, dashboard screenshot.
I will check what is the reason that data is not collected.
Best regards,
Shirly Radco
BI Software Engineer
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
On Tue, Jan 17, 2017 at 6:21 PM, Andrea Ghelardi <a.ghelardi(a)iontrading.com>
wrote:
Hello Liron,
Thank you for your reply.
So basically our DWH is not creating reports because vdsm is too slow in
collecting results?
I understand the message logged in engine is informational instead of
warning, but still DWH is not working.
Do you have any additional hint about what to check?
Cheers
AG
-----Original Message-----
From: Liron Aravot [mailto:laravot@redhat.com]
Sent: Tuesday, January 17, 2017 2:30 PM
To: Tal Nisan <tnisan(a)redhat.com>
Cc: Shirly Radco <sradco(a)redhat.com>; users <users(a)ovirt.org>; Andrea
Ghelardi <a.ghelardi(a)iontrading.com>
Subject: Re: [ovirt-users] Ovirt 4.0.5 reporting dashboard not working.
When a host is "connected" to a storage pool it monitors the active pool
domains. When the domain monitoring results are reported back from the
host, the first monitor run may haven't finished yet. In that case the
returned status from vdsm is a dummy status and not an actual result - when
getting such a status the engine logs it.
We should change that log print to INFO rather then WARN.
On Tue, Dec 20, 2016 at 12:17 PM, Tal Nisan <tnisan(a)redhat.com> wrote:
> Liron, can you please check why does this "report isn't an actual
> report" is appearing in the log?
>
> On Mon, Dec 19, 2016 at 10:33 AM, Andrea Ghelardi
> <a.ghelardi(a)iontrading.com> wrote:
>>
>> Hello Shirly,
>>
>> I restarted dwh service as per your suggestion with no success.
>>
>>
>>
>> Here a sample of DWH log:
>>
>> 2016-12-14
>> 12:31:55|kdcGa9|GCXnuH|PIv06L|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|D
>> efault|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not
>> updating the statistics. Please check your oVirt Engine status.|9704
>>
>> 2016-12-14
>> 12:32:20|ncjn2O|GCXnuH|PIv06L|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|D
>> efault|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not
>> updating the statistics. Please check your oVirt Engine status.|9704
>>
>> 2016-12-14
>> 15:52:37|Xx2zzb|GCXnuH|PIv06L|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|D
>> efault|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not
>> updating the statistics. Please check your oVirt Engine status.|9704
>>
>> 2016-12-16 17:39:13|ETL Service Stopped
>>
>> 2016-12-16 17:39:14|ETL Service Started
>>
>> ovirtEngineDbDriverClass|org.postgresql.Driver
>>
>>
>> ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/o
>> ovirtEngineHistoryDbJdbcConnection|virt_engine_history?sslfactory=org
>> ovirtEngineHistoryDbJdbcConnection|.postgresql.ssl.NonValidatingFacto
>> ovirtEngineHistoryDbJdbcConnection|ry
>>
>> hoursToKeepDaily|0
>>
>> hoursToKeepHourly|720
>>
>> ovirtEngineDbPassword|**********************
>>
>> runDeleteTime|3
>>
>>
>> ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?s
>> ovirtEngineDbJdbcConnection|slfactory=org.postgresql.ssl.NonValidatin
>> ovirtEngineDbJdbcConnection|gFactory
>>
>> runInterleave|20
>>
>> limitRows|limit 1000
>>
>> ovirtEngineHistoryDbUser|ovirt_engine_history
>>
>> ovirtEngineDbUser|engine
>>
>> deleteIncrement|10
>>
>> timeBetweenErrorEvents|300000
>>
>> hoursToKeepSamples|24
>>
>> deleteMultiplier|1000
>>
>> lastErrorSent|2011-07-03 12:46:47.000000
>>
>> etlVersion|4.0.5
>>
>> dwhAggregationDebug|false
>>
>> dwhUuid|a18846e6-d188-4170-8549-aeb1c54fa390
>>
>> ovirtEngineHistoryDbDriverClass|org.postgresql.Driver
>>
>> ovirtEngineHistoryDbPassword|**********************
>>
>>
>>
>>
>>
>> And here a sample of Engine.log
>>
>>
>>
>> 2016-12-19 04:32:05,939 WARN
>> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
>> (DefaultQuartzScheduler5) [53791585] Domain
>> '05c01989-18a1-4a45-9ed6-76c6badc728a:intel2-dstore04' report isn't
>> an actual report
>>
>> 2016-12-19 04:32:05,939 WARN
>> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
>> (DefaultQuartzScheduler5) [53791585] Domain
>> 'f0d8ea03-17ab-4feb-bbf8-408e0550fc29:boole2-dstore1' report isn't
an
>> actual report
>>
>>
>>
>>
>>
>> So apparently DWH is working, but that “report isn't an actual
>> report” is quite obscure to me.
>>
>> I need to clarify that (almost) all these storages are iscsi SAN
>> hosted and have been detached from Ovirt3 installation and IMPORTED
into Ovirt4.
>>
>>
>>
>> Could you suggest for next step?
>>
>> Thanks
>>
>> Andrea
>>
>>
>>
>> From: Shirly Radco [mailto:sradco@redhat.com]
>> Sent: Thursday, December 8, 2016 10:22 AM
>> To: Andrea Ghelardi <a.ghelardi(a)iontrading.com>
>> Cc: users <users(a)ovirt.org>
>> Subject: Re: [ovirt-users] Ovirt 4.0.5 reporting dashboard not working.
>>
>>
>>
>> Hi Andrea,
>>
>>
>>
>> Please try to restart the dwh service.
>>
>> It is the service that collects the samples data from the engine
>> database to a data warehouse, ovirt_engine_history.
>>
>> run:
>>
>>
>>
>> service ovirt-engine-dwhd restart
>>
>>
>>
>> and send me the log again.
>>
>>
>>
>> If data is still not collected to ovirt_engine_history db I'll need
>> you to open a bug so we can follow on this there.
>>
>>
>> Best regards,
>>
>> Shirly Radco
>>
>> BI Software Engineer
>>
>> Red Hat Israel Ltd.
>>
>> 34 Jerusalem Road
>>
>> Building A, 4th floor
>>
>> Ra'anana, Israel 4350109
>>
>>
>>
>> On Wed, Dec 7, 2016 at 5:43 PM, Andrea Ghelardi
>> <a.ghelardi(a)iontrading.com> wrote:
>>
>> Hello group,
>>
>> I noticed that my dashboard does not show little colored “cubes”
>> which show storage CPU and RAM usage history status.
>>
>> Attached an image and logs from
>> /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log
>>
>> Here’s an extract:
>>
>>
>>
>> Exception in component tJDBCInput_5
>>
>> org.postgresql.util.PSQLException: ERROR: smallint out of range
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryEx
>> ecutorImpl.java:2157)
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor
>> Impl.java:1886)
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja
>> va:255)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Stat
>> ement.java:555)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(Abstract
>> Jdbc2Statement.java:403)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc
>> 2Statement.java:283)
>>
>> at
>> ovirt_engine_dwh.statisticssync_4_0.StatisticsSync.tJDBCInput_5Proces
>> s(StatisticsSync.java:4056)
>>
>> at
>> ovirt_engine_dwh.statisticssync_4_0.StatisticsSync$3.run(StatisticsSy
>> nc.java:15979)
>>
>> Exception in component tJDBCInput_8
>>
>> org.postgresql.util.PSQLException: ERROR: current transaction is
>> aborted, commands ignored until end of transaction block
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryEx
>> ecutorImpl.java:2157)
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor
>> Impl.java:1886)
>>
>> at
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja
>> va:255)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Stat
>> ement.java:555)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(Abstract
>> Jdbc2Statement.java:403)
>>
>> at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc
>> 2Statement.java:283)
>>
>> at
>> ovirt_engine_dwh.statisticssync_4_0.StatisticsSync.tJDBCInput_8Proces
>> s(StatisticsSync.java:5991)
>>
>> at
>> ovirt_engine_dwh.statisticssync_4_0.StatisticsSync$4.run(StatisticsSy
>> nc.java:16025)
>>
>> 2016-11-27
>> 14:27:40|tm1tT6|GCXnuH|0jajaj|OVIRT_ENGINE_DWH|StatisticsSync|Default
>> |6|Java
>> Exception|tJDBCInput_5|org.postgresql.util.PSQLException:ERROR:
>> Exception|smallint out
>> of range|1
>>
>>
>>
>> This is a quite fresh new installation, and restarting engine VM
>> (hosted-engine –vm-stop + hosted-engine –vm-start) does not fix the
problem.
>>
>> Ovirt is behaving normally.
>>
>>
>>
>> Any clue?
>>
>> Cheers
>>
>> Andrea
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>