Well, I see that I'm late to give the information :) Thank you to pointing me 
to this, but I have now some other questions now...
How can I see the timezone of the DB ?
When it says "all machines", do you confirm that this is physical machines, not 
VMs ?
May I apply the solution given on access.redhat or not, as there is no more 
messages since 3AM ?
And, last question but not least, can this timezone be changed on the machines 
(and DB ?) without issue ?

--

Regards,

Frank

Le Dimanche, Octobre 28, 2018 11:40 CET, Shirly Radco <sra...@redhat.com> a 
écrit:
 Hi, Please see 
herehttps://www.ovirt.org/documentation/data-warehouse/Data_Collection_Setup_and_Reports_Installation_Overview/
 "It is recommended that you set the system time zone for all machines in your 
Data Warehouse deployment to UTC. This ensures that data collection is not 
interrupted by variations in your local time zone: for example, a change from 
summer time to winter time." What timezone is your DB configured to? Best, --
SHIRLY RADCO
BI SENIOR SOFTWARE ENGINEER
Red Hat IsraelTRIED. TESTED. TRUSTED. On Sun, Oct 28, 2018 at 12:32 PM fsoyer 
<fso...@systea.fr> wrote:Hi all,
Maybe it has already been posted, but I think I've discoverd a little bug. This 
night I had this messages :
28 oct. 2018 03:00:00
ETL service aggregation to hourly tables has encountered an error. Please 
consult the service log for more details.
28 oct. 2018 02:40:27
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:33:42
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:27:42
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:22:27
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:16:37
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:11:06
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:05:06
ETL service sampling has encountered an error. Please consult the service log 
for more details.
28 oct. 2018 02:00:06
ETL service sampling has encountered an error. Please consult the service log 
for more details
28 oct. 2018 02:00:00
ETL service aggregation to hourly tables has encountered an error. Please 
consult the service log for more details.and, coincidence, here in France we 
have change to winter hour at... 2AM :) So regarding this post:
https://access.redhat.com/solutions/3338001
speaking about a time problem, I've supposed that this is related ! No ? 
access.redhat says that the cause was not yet determined, but maybe it can be 
interesting to propose this cause ? But the bug is actually closed.

Question : does this repair all alone (as there is no more messages after 3AM) 
or may I applied the solution with postgres updates (I must say that I'm not 
very enthousiast for that...) ?

Regards,

--
Frank _______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GNGAQKTA5PDJUYMTFJABDLZA27FHUY7O/
 
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D46VJJ5LHQP4JTLMWL6L2QBMPL2SCU3W/

Reply via email to