Re: [ovirt-users] ETL service sampling has encountered an error. Please consult the service log for more details.

2017-04-23 Thread Shirly Radco
Hi Nicolas, These are DWH error. I see in engine.log that around the time you are referring to there are many connectipn errors to the postgresql database. When DWH is unable to connect to the engine database and error is sent to the ovirt-engine-history.log. I don't see the error you are

Re: [ovirt-users] ETL service sampling has encountered an error. Please consult the service log for more details.

2017-04-23 Thread Nicol√°s
Any ideas on this? Thanks. El 20/04/17 a las 12:12, nico...@devels.es escribió: Hi, We're using oVirt 4.1.1.8 (upgraded yesterday) and since it has been showing some strange errors I'd like to know about: ETL service sampling has encountered an error. Please consult the service log

Re: [ovirt-users] ETL service sampling has encountered an error

2017-02-23 Thread Shirly Radco
Hi, This in a known issue. We have a bug targeted to 4.2 for this. https://bugzilla.redhat.com/show_bug.cgi?id=137 This error means that the dwh tried to reach the engine database and for some reason the heartbeat of the engine did not update since the last dwh sync. Best regards, Shirly

Re: [ovirt-users] ETL service sampling

2016-08-24 Thread knarra
Thank you Fernando and shirly for the explanation On 08/24/2016 11:46 PM, Shirly Radco wrote: The ETL sampling process collects the configurations and statistics for the new dashboards. The engine has a heartbeat that should update every 15 seconds. Sampling runs every 20 seconds. If the

Re: [ovirt-users] ETL service sampling

2016-08-24 Thread Shirly Radco
The ETL sampling process collects the configurations and statistics for the new dashboards. The engine has a heartbeat that should update every 15 seconds. Sampling runs every 20 seconds. If the engine is busy and the heartbeat does not update for some reason , the dwh will send an error. It

Re: [ovirt-users] ETL service sampling

2016-08-24 Thread Fernando Fuentes
Kasturi, I had the same issue and here is what Yaniv said: This can happen when the engine is down or very busy. This error seems to happen only sometimes, which indicates this is the case. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th