Hi Sandro,

It seems this issue is not related to current RC (earliest entry found for 02 Feb 2019).

I have followed RH Solution #3338001 (https://access.redhat.com/solutions/3338001) and last night I didn't have that event in the UI.

It seems that I still have exceptions in the logs like :
Exception in component tJDBCInput_3
org.postgresql.util.PSQLException: This connection has been closed.
        at org.postgresql.jdbc2.AbstractJdbc2Connection.checkClosed(AbstractJdbc2Connection.java:822)
        at org.postgresql.jdbc3.AbstractJdbc3Connection.createStatement(AbstractJdbc3Connection.java:229)
        at org.postgresql.jdbc2.AbstractJdbc2Connection.createStatement(AbstractJdbc2Connection.java:294)
        at ovirt_engine_dwh.dailytimekeepingjob_4_3.DailyTimeKeepingJob.tJDBCInput_3Process(DailyTimeKeepingJob.java:1331)
        at ovirt_engine_dwh.dailytimekeepingjob_4_3.DailyTimeKeepingJob.tPostjob_1Process(DailyTimeKeepingJob.java:1070)
        at ovirt_engine_dwh.dailytimekeepingjob_4_3.DailyTimeKeepingJob.runJobInTOS(DailyTimeKeepingJob.java:8784)
        at ovirt_engine_dwh.dailytimekeepingjob_4_3.DailyTimeKeepingJob.runJob(DailyTimeKeepingJob.java:8375)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun.tInfiniteLoop_3Process(ParallelRun.java:3539)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun.tJava_4Process(ParallelRun.java:3300)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun$4.run(ParallelRun.java:5712)
2019-07-17 00:00:00|sykykw|ayRRMN|6ekzCe|OVIRT_ENGINE_DWH|DailyTimeKeepingJob|Default|6|Java Exception|tJDBCInput_3|org.postgresql.util.PSQLException:This connection has been closed.|1
Exception in component tJDBCInput_10
org.postgresql.util.PSQLException: This connection has been closed.
        at org.postgresql.jdbc2.AbstractJdbc2Connection.checkClosed(AbstractJdbc2Connection.java:822)
        at org.postgresql.jdbc3.AbstractJdbc3Connection.createStatement(AbstractJdbc3Connection.java:229)
        at org.postgresql.jdbc2.AbstractJdbc2Connection.createStatement(AbstractJdbc2Connection.java:294)
        at ovirt_engine_dwh.deletetimekeepingjob_4_3.DeleteTimeKeepingJob.tJDBCInput_10Process(DeleteTimeKeepingJob.java:1493)
        at ovirt_engine_dwh.deletetimekeepingjob_4_3.DeleteTimeKeepingJob.tPostjob_2Process(DeleteTimeKeepingJob.java:1232)
        at ovirt_engine_dwh.deletetimekeepingjob_4_3.DeleteTimeKeepingJob.runJobInTOS(DeleteTimeKeepingJob.java:11707)
        at ovirt_engine_dwh.deletetimekeepingjob_4_3.DeleteTimeKeepingJob.runJob(DeleteTimeKeepingJob.java:11308)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun.tInfiniteLoop_6Process(ParallelRun.java:4174)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun.tJava_5Process(ParallelRun.java:3716)
        at ovirt_engine_dwh.parallelrun_4_3.ParallelRun$5.run(ParallelRun.java:5758)
2019-07-17 03:00:01|QGmtgL|ayRRMN|6ekzCe|OVIRT_ENGINE_DWH|DeleteTimeKeepingJob|Default|6|Java Exception|tJDBCInput_10|org.postgresql.util.PSQLException:This connection has been closed.|1

I'm not sure how fatal are those, as this type of exceptions are logged for a lot of time - the earliest occurrence I found in the logs is for : 'etlVersion|4.2.4.3' from 2019-01-31 .


So , latest RC seems to be OK.

Best Regards,
Strahil Nikolov 

В вторник, 16 юли 2019 г., 15:28:10 ч. Гринуич+3, Sandro Bonazzola <sbonazzo@redhat.com> написа:




On Tuesday, July 16, 2019, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Hi Sandro,

I'm currently running the latest release candidate.
So far I found only 1 problem - It seems that every night the following event is being generated:

ETL service aggregation to hourly tables has encountered an error. Please consult the service log for more details.

I haven't checked the logs yet, but I will keep you updated.


thanks for the feedback, Shirley can you please follow up? 


 
best Regards,
Strahil Nikolov

В четвъртък, 11 юли 2019 г., 5:34:52 ч. Гринуич-4, Sandro Bonazzola <sbonazzo@redhat.com> написа:


The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 Fifth Release Candidate for testing, as of July 11th, 2019.

While testing this release candidate please consider deeper testing on gluster upgrade since with this release we are switching from Gluster 5 to Gluster 6.

This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)

See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed.

Notes:
- oVirt Appliance is laready available
- oVirt Node is already available[2]

Additional Resources:
* Read more about the oVirt 4.3.5 release highlights:http://www.ovirt. org/release/4.3.5/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:http://www.ovirt.org/ blog/

[1] http://www.ovirt.org/release/ 4.3.5/
[2] http://resources.ovirt.org/ pub/ovirt-4.3-pre/iso/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

______________________________ _________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/ QCJ2IZOKMIIN4DMN4T4K22P7L4MJK6 TA/



--