Bug 1705132 - [Docs] ETL service sampling has encountered an error. Please consult the service log for more details. (No dashboard data)
Summary: [Docs] ETL service sampling has encountered an error. Please consult the serv...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Documentation
Version: 4.2.4.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ovirt-4.3.5
: ---
Assignee: Eli Marcus
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks: 1723791
TreeView+ depends on / blocked
 
Reported: 2019-05-01 15:07 UTC by Mikhail
Modified: 2019-08-04 09:48 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-04 09:41:49 UTC
oVirt Team: Metrics
Embargoed:
pm-rhel: ovirt-4.3+


Attachments (Terms of Use)
DWH log (9.46 MB, text/plain)
2019-05-05 12:56 UTC, Mikhail
no flags Details
Setup and upgrade logs (14.50 MB, application/gzip)
2019-05-30 15:35 UTC, Mikhail
no flags Details
rpm -qa (27.01 KB, text/plain)
2019-05-31 09:00 UTC, Mikhail
no flags Details
DWHPID (121.92 KB, text/plain)
2019-06-04 07:50 UTC, Mikhail
no flags Details

Description Mikhail 2019-05-01 15:07:42 UTC
Description of problem:

I recently upgraded to 4.3.2 from 4.2.8 and there is no info about the status on the dashboard.

Version-Release number of selected component (if applicable):

oVirt 4.3.3.5-1.el7


How reproducible:

I don't think it is a common error.

Actual results:

Empty dashboard and error in logs "ETL service sampling has encountered an error. Please consult the service log for more details."

Error in /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log

2019-05-01 16:59:24|3T1zO9|WaTt56|O6SQbD|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|6|Java Exception|tRunJob_1|java.lang.RuntimeException:Child job running failed|1
Exception in component tJDBCOutput_2
org.postgresql.util.PSQLException: Can't infer the SQL type to use for an instance of java.util.UUID. Use setObject() with an explicit Types value to specify the type to use.
        at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1920)
        at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:36)
        at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:47)
        at ovirt_engine_dwh.configurationsync_4_3.ConfigurationSync.tJDBCInput_2Process(ConfigurationSync.java:6848)
        at ovirt_engine_dwh.configurationsync_4_3.ConfigurationSync.tJDBCInput_11Process(ConfigurationSync.java:6053)
        at ovirt_engine_dwh.configurationsync_4_3.ConfigurationSync.tJDBCInput_9Process(ConfigurationSync.java:4288)
        at ovirt_engine_dwh.configurationsync_4_3.ConfigurationSync$2.run(ConfigurationSync.java:59898)
2019-05-01 16:59:24|HwdgUS|WaTt56|zBXxD7|OVIRT_ENGINE_DWH|ConfigurationSync|Default|6|Java Exception|tJDBCOutput_2|org.postgresql.util.PSQLException:Can't infer the SQL type to use for an instance of java.util.UUID. Use setObject() with an explicit Types value to specify the type to use.|1
Exception in component tRunJob_1
java.lang.RuntimeException: Child job running failed
        at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tRunJob_1Process(SampleRunJobs.java:1198)
        at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tRunJob_4Process(SampleRunJobs.java:1000)
        at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tJDBCConnection_2Process(SampleRunJobs.java:767)
        at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tJDBCConnection_1Process(SampleRunJobs.java:642)
        at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs$2.run(SampleRunJobs.java:2683)
2019-05-01 16:59:24|zBXxD7|WaTt56|kZRtTg|OVIRT_ENGINE_DWH|SampleRunJobs|Default|6|Java Exception|tRunJob_1|java.lang.RuntimeException:Child job running failed|1
Exception in component tRunJob_1
java.lang.RuntimeException: Child job running failed
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tRunJob_1Process(SampleTimeKeepingJob.java:6067)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCInput_2Process(SampleTimeKeepingJob.java:5809)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCConnection_1Process(SampleTimeKeepingJob.java:4444)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCConnection_2Process(SampleTimeKeepingJob.java:4319)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tRowGenerator_2Process(SampleTimeKeepingJob.java:4188)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCInput_3Process(SampleTimeKeepingJob.java:3593)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCInput_5Process(SampleTimeKeepingJob.java:2977)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCInput_4Process(SampleTimeKeepingJob.java:2295)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob.tJDBCConnection_3Process(SampleTimeKeepingJob.java:1649)
        at ovirt_engine_dwh.sampletimekeepingjob_4_3.SampleTimeKeepingJob$2.run(SampleTimeKeepingJob.java:11363)



Expected results:

Dashboard with status data.

Comment 1 Shirly Radco 2019-05-05 10:59:52 UTC
Hi, Please attach the DWH log.

Comment 2 Mikhail 2019-05-05 12:56:43 UTC
Created attachment 1563914 [details]
DWH log

Required log

Comment 3 Mikhail 2019-05-15 12:34:03 UTC
Hi, 

any additional info needed?

Best regards,

Mikhail

Comment 4 Yedidyah Bar David 2019-05-30 05:51:05 UTC
Please attach also setup/upgrade log (/var/log/ovirt-engine/setup/*) and output of 'rpm -qa'. Thanks!

Comment 5 Mikhail 2019-05-30 15:35:38 UTC
Created attachment 1575282 [details]
Setup and upgrade logs

Comment 6 Mikhail 2019-05-31 09:00:23 UTC
Created attachment 1575622 [details]
rpm -qa

Comment 7 Yedidyah Bar David 2019-06-02 17:15:53 UTC
Based on the attached logs, it seems like:

1. dwhd stopped working starting with the upgrade from 4.2.8 to 4.3.2, log file ovirt-engine-setup-20190407130123-uf4ua5.log . The errors in dwhd log start right after dwhd is started, near the the end of this file.

2. engine-setup itself, both in this run and in the next, last 3 runs (two without updates, last one from 4.3.2 to 4.3.3), did manage to connect to dwh's db, and update it as needed (last run).

I must conclude that the error is unrelated to engine-setup itself, but is caused by some underlying missing/bad java library/package/etc.

Mikhail, please attach also:

ps auxww | grep dwhd

Thanks.

Comment 8 Mikhail 2019-06-03 11:21:34 UTC
Good day,

output of ps auxww | grep dwhd

[root@kamelot-linux-4 ~]# ps auxww | grep dwhd
ovirt     2353  0.0  0.1 204908 10732 ?        Ss   Apr16   0:00 /usr/bin/python /usr/share/ovirt-engine-dwh/services/ovirt-engine-dwhd/ovirt-engine-dwhd.py --redirect-output --systemd=notify start
ovirt     2457  0.8  6.8 6471720 550068 ?      Sl   Apr16 559:17 ovirt-engine-dwhd -Dorg.ovirt.engine.dwh.settings=/tmp/tmpSYi0H2/settings.properties -Xms1g -Xmx1g -classpath /usr/share/ovirt-engine-dwh/lib/*::/usr/share/java/dom4j.jar:/usr/share/java/apache-commons-collections.jar:/usr/share/java/postgresql-jdbc.jar ovirt_engine_dwh.historyetl_4_3.HistoryETL --context=Default
root     17734  0.0  0.0 112708   968 pts/0    S+   13:19   0:00 grep --color=auto dwhd


Best regards, 

Mikhail

Comment 9 Yedidyah Bar David 2019-06-04 05:59:02 UTC
Thanks, Mikhail. Please attach also the output of this:

DWHPID=$(ps auxww | awk '/[d]whd.*settings/ {print $2}')

for l in /proc/$DWHPID/fd/*; do f=$(readlink $l); echo === $f ===; rpm -Vvf $f; done

Thanks.

Comment 10 Mikhail 2019-06-04 07:50:25 UTC
Created attachment 1576936 [details]
DWHPID

Comment 11 Yedidyah Bar David 2019-06-04 09:31:53 UTC
I now realized that you have many packages from el 7.4. oVirt 4.3 is supported only with 7.6. Can you please upgrade your machine to 7.6 and see if this helps? Thanks.

The release notes say that it's for 7.6, but I guess we should also clarify in the upgrade instructions that you should upgrade the OS first.

Comment 12 Mikhail 2019-06-05 10:05:31 UTC
(In reply to Yedidyah Bar David from comment #11)
> I now realized that you have many packages from el 7.4. oVirt 4.3 is
> supported only with 7.6. Can you please upgrade your machine to 7.6 and see
> if this helps? Thanks.
> 
> The release notes say that it's for 7.6, but I guess we should also clarify
> in the upgrade instructions that you should upgrade the OS first.

Good day, 

I upgraded and restarted the engine server 

[root@kamelot-linux-4 ~]# cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)

Dashboard is back to normal and working, thank you.

Best regards,

Mikhail

Comment 13 Yedidyah Bar David 2019-06-05 10:16:50 UTC
Thanks for the report.

Shirly - leaving it up to you to decide how to continue.

You can try finding out which package was too old and patch the spec file to require the one you need. Might check talend docs for this, no idea.

You can also update the documentation.

Comment 14 Shirly Radco 2019-06-10 08:33:27 UTC
Hi, What do we need to update in the documentation?

Comment 15 Yedidyah Bar David 2019-06-11 07:17:30 UTC
(In reply to Shirly Radco from comment #14)
> Hi, What do we need to update in the documentation?

That before upgrading dwh (or the engine, etc.), user must 'yum update' (everything, including OS, jboss/wildfly, etc.).

Comment 19 Sandro Bonazzola 2019-07-10 06:13:21 UTC
Can this move to QE?

Comment 21 Eli Marcus 2019-07-25 09:38:46 UTC
Can someone confirm that this is sufficient, and already covered in the documentation, so that this is not really a bug? 

the the "yum update" command is already included in the Data Warehouse Guide procedures under: 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/data_warehouse_guide/index#Migrating_the_Data_Warehouse_Service_to_a_Separate_Machine_migrate_DWH
and under: 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/data_warehouse_guide/index#Installing_and_Configuring_Data_Warehouse_on_a_Separate_Machine_DWH_admin

"Installing Data Warehouse on a Separate Machine

    1. Log in to the machine where you want to install the database.

    2. Ensure that all packages are up to date:

    # yum update

    3. Install the ovirt-engine-dwh-setup package:

    # yum install ovirt-engine-dwh-setup

    4. Run the engine-setup command to begin the installation:

    # engine-setup"
     
          ...

I have seen similar bugs recently that request a reminder for the user to perform a "yum update" to make sure that all the packages are up to date, 
I have double checked our installation and upgrade documents, and they all include a reminder like the following: 


"2. Ensure that all packages are up to date:

   # yum update"

Comment 22 Sandro Bonazzola 2019-07-25 10:43:39 UTC
I tend to agree this can be closed as not a bug but letting reporter to reply


Note You need to log in before you can comment on or make changes to this bug.