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