Hi,

Please open a bug with the details you added here.
Please attach setup logs (all of them since 4.2, including) and ovirt-engine-dwh log so we can investigate this issue.

If you stop ovirt-engine-dwhd process, does pg calm down?

Thank you
--

Shirly Radco

BI Senior Software Engineer

Red Hat



On Sun, Jun 16, 2019 at 12:07 PM Albl, Oliver <Oliver.Albl@fabasoft.com> wrote:

Hi,

 

ovirt_engine_history=# SELECT id, version, script, checksum, installed_by, started_at, ended_at, state, current, comment

FROM schema_version

ORDER BY version DESC limit 10  ;

id | version  |                              script                               |             checksum             |     installed_by     |         started_at         |          ended_at          |   state   | current |

comment

----+----------+-------------------------------------------------------------------+----------------------------------+----------------------+----------------------------+----------------------------+-----------+---------+-----------

--------------------

50 | 04030020 | upgrade/04_03_0020_update_rx_tx_rate_percition.sql                | c480b070cc69681cf62fb853f3d7139f | ovirt_engine_history | 2019-06-14 18:14:44.960503 | 2019-06-14 18:14:44.991593 | SKIPPED   | t       | Installed

already by 04020040

49 | 04030010 | upgrade/04_03_0010_update_network_name_length.sql                 | a1a0d75560575cdc60c0bbaad2cda773 | ovirt_engine_history | 2019-06-14 18:14:44.904426 | 2019-06-14 18:14:44.935725 | SKIPPED   | f       | Installed

already by 04020030

48 | 04020040 | upgrade/04_02_0040_update_rx_tx_rate_percition.sql                | c480b070cc69681cf62fb853f3d7139f | ovirt_engine_history | 2018-07-07 14:34:42.505446 | 2018-07-07 14:36:31.662577 | INSTALLED | f       |

47 | 04020030 | upgrade/04_02_0030_update_network_name_length.sql                 | a1a0d75560575cdc60c0bbaad2cda773 | ovirt_engine_history | 2018-07-07 14:34:42.438056 | 2018-07-07 14:34:42.482705 | INSTALLED | f       |

46 | 04020020 | upgrade/04_02_0020__updated_vm_interface_history_id_to_bigint.sql | 58a8afa29fc720dc87f37b7f9c9e0151 | ovirt_engine_history | 2018-04-18 17:17:04.908667 | 2018-04-18 17:17:39.111339 | INSTALLED | f       |

45 | 04020010 | upgrade/04_02_0010_updated_vm_template_name_length.sql            | 4b5391f40e8787e3b1033635aafe18a1 | ovirt_engine_history | 2018-01-05 09:56:39.213757 | 2018-01-05 09:56:39.238775 | SKIPPED   | f       | Installed

already by 04010020

44 | 04010020 | upgrade/04_01_0020_updated_vm_template_name_lentgh.sql            | 4b5391f40e8787e3b1033635aafe18a1 | ovirt_engine_history | 2017-10-05 13:53:04.225474 | 2017-10-05 13:53:04.269508 | INSTALLED | f       |

43 | 04010010 | upgrade/04_01_0010_added_seconds_in_status_to_sample_tables.sql   | be7a1b2fc7f03d263b45a613d5bced03 | ovirt_engine_history | 2017-02-03 13:16:18.29672  | 2017-02-03 13:16:18.320728 | SKIPPED   | f       | Installed

already by 04000050

42 | 04000050 | upgrade/04_00_0050_added_seconds_in_status_to_sample_tables.sql   | be7a1b2fc7f03d263b45a613d5bced03 | ovirt_engine_history | 2016-10-03 15:13:33.856501 | 2016-10-03 15:13:34.010135 | INSTALLED | f       |

41 | 04000040 | upgrade/04_00_0040_drop_all_history_db_foreign_keys.sql           | ed8b2c02bea97d0ee21f737614a2d5e3 | ovirt_engine_history | 2016-10-03 15:13:33.763905 | 2016-10-03 15:13:33.839532 | INSTALLED | f       |

(10 rows)

 

All the best,

Oliver

 

Von: Shirly Radco <sradco@redhat.com>
Gesendet: Sonntag, 16. Juni 2019 11:04
An: Albl, Oliver <Oliver.Albl@fabasoft.com>
Cc: sleviim@redhat.com; users@ovirt.org; Eli Mesika <emesika@redhat.com>; Yedidyah Bar David <didi@redhat.com>
Betreff: Re: [ovirt-users] Re: Cannot access dashboard after upgrading to 4.3.4

 

Hi,

 

Please attach here the result of the following query from the ovirt_engine_history db:

 

SELECT id, version, script, checksum, installed_by, started_at, ended_at, state, current, comment

FROM schema_version

ORDER BY version DESC limit 10  ;

 

Best regards,

--

Shirly Radco

BI Senior Software Engineer

Red Hat

Das Bild wurde vom Absender entfernt.

 

---------- Forwarded message ---------
From: Albl, Oliver <
Oliver.Albl@fabasoft.com>
Date: Sun, Jun 16, 2019 at 11:42 AM
Subject: AW: [ovirt-users] Re: Cannot access dashboard after upgrading to 4.3.4
To:
sradco@redhat.com <sradco@redhat.com>
Cc:
sleviim@redhat.com <sleviim@redhat.com>, users@ovirt.org <users@ovirt.org>

 

Hi,

 

  rebooted oVirt engine VM (no hosted engine), same result. DHW packages are:

 

ovirt-engine-dwh.noarch               4.3.0-1.el7                @ovirt-4.3

ovirt-engine-dwh-setup.noarch         4.3.0-1.el7                @ovirt-4.3

 

After reboot the following two queries start running again (they were running for more than 24 hours before this reboot):

 

SELECT name, AVG(total) AS total, AVG(used) AS used, MAX(previous_used) AS previous_used, MAX(previous_total) AS previous_total, MAX(vm_disk_usage_percent) AS us

age_percent FROM (SELECT history_datetime, vms.vm_name AS name, SUM(vm_disk_size_mb) AS total, SUM(vm_disk_actual_size_mb) AS used, COALESCE(MAX(previous_actual_size), 0) AS previous_used, COALESCE(MAX(previous_

total_size), 0) AS previous_total, CASE WHEN MAX(vm_disk_size_mb) = 0 THEN 0 ELSE (CAST(MAX(vm_disk_actual_size_mb) AS DECIMAL)/ MAX(vm_disk_size_mb) * 100) END AS vm_disk_usage_percent FROM v4_2_statistics_vms_

disks_resources_usage_samples samples INNER JOIN v4_2_latest_configuration_vms_devices devices ON devices.device_id = vm_disk_id INNER JOIN v4_2_latest_configuration_vms vms ON vms.vm_id = devices.vm_id INNER JO

IN v4_2_latest_configuration_vms_disks disks ON disks.vm_disk_id = samples.vm_disk_id LEFT OUTER JOIN (SELECT vm_name, AVG(previous_actual_size) AS previous_actual_size, AVG(previous_total_size) AS previous_tota

l_size FROM (SELEC

 

 

All the best,

Oliver

 

Von: Shirly Radco <sradco@redhat.com>
Gesendet: Sonntag, 16. Juni 2019 10:34
An: Albl, Oliver <
Oliver.Albl@fabasoft.com>
Cc:
sleviim@redhat.com; users@ovirt.org
Betreff: Re: [ovirt-users] Re: Cannot access dashboard after upgrading to 4.3.4

 

Hi,

 

Please try to restart postgres an ovirt-engine-dwhd.

It looks that this is a 4.2 query.

What version are the dwh packages?

 

Best,

--

Shirly Radco

BI Senior Software Engineer

Red Hat

Das Bild wurde vom Absender entfernt.

 

 

On Sun, Jun 16, 2019 at 11:10 AM Albl, Oliver <Oliver.Albl@fabasoft.com> wrote:

Hi,

 

  I am not using hosted engine but a dedicated installation. The upgrade was performed with following steps:

 

yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

yum update "ovirt-*-setup*"

engine-setup

yum update

 

All the best,

Oliver

 

Von: Shani Leviim <sleviim@redhat.com>
Gesendet: Sonntag, 16. Juni 2019 09:03
An: Albl, Oliver <
Oliver.Albl@fabasoft.com>
Cc:
users@ovirt.org
Betreff: Re: [ovirt-users] Cannot access dashboard after upgrading to 4.3.4

 

Hi,

Did you run 'engine-setup' and 'yum update' after upgrading ovirt?

 

 

Regards,

Shani Leviim

 

 

On Sat, Jun 15, 2019 at 10:26 AM Albl, Oliver <Oliver.Albl@fabasoft.com> wrote:

Hi all,

 

  I upgraded our installation from 4.2.8 to 4.3.4 and I am unable to access the dashboard in UI as there is only “Loading data…” displayed. There are postgres processes running on the engine taking 100% cpu. One is running for more than 14 hours:

 

SELECT name, AVG(total) AS total, AVG(used) AS used, MAX(previous_used) AS previous_used, MAX(previous_total) AS previous_total, MAX(vm_disk_

usage_percent) AS usage_percent FROM (SELECT history_datetime, vms.vm_name AS name, SUM(vm_disk_size_mb) AS total, SUM(vm_disk_actual_size_mb) AS used, COALESCE(MAX(previous_actual_size), 0)

AS previous_used, COALESCE(MAX(previous_total_size), 0) AS previous_total, CASE WHEN MAX(vm_disk_size_mb) = 0 THEN 0 ELSE (CAST(MAX(vm_disk_actual_size_mb) AS DECIMAL)/ MAX(vm_disk_size_mb) *

100) END AS vm_disk_usage_percent FROM v4_2_statistics_vms_disks_resources_usage_samples samples INNER JOIN v4_2_latest_configuration_vms_devices devices ON devices.device_id = vm_disk_id IN

NER JOIN v4_2_latest_configuration_vms vms ON vms.vm_id = devices.vm_id INNER JOIN v4_2_latest_configuration_vms_disks disks ON disks.vm_disk_id = samples.vm_disk_id LEFT OUTER JOIN (SELECT v

m_name, AVG(previous_actual_size) AS previous_actual_size, AVG(previous_total_size) AS previous_total_size FROM (SELEC

13783 | 2019-06-15 08:41:52.349769+02 | active | SELECT name, AVG(total) AS total, AVG(used) AS used, MAX(previous_used) AS previous_used, MAX(previous_total) AS previous_total, MAX(vm_disk_

usage_percent) AS usage_percent FROM (SELECT history_datetime, vms.vm_name AS name, SUM(vm_disk_size_mb) AS total, SUM(vm_disk_actual_size_mb) AS used, COALESCE(MAX(previous_actual_size), 0)

AS previous_used, COALESCE(MAX(previous_total_size), 0) AS previous_total, CASE WHEN MAX(vm_disk_size_mb) = 0 THEN 0 ELSE (CAST(MAX(vm_disk_actual_size_mb) AS DECIMAL)/ MAX(vm_disk_size_mb) *

100) END AS vm_disk_usage_percent FROM v4_2_statistics_vms_disks_resources_usage_samples samples INNER JOIN v4_2_latest_configuration_vms_devices devices ON devices.device_id = vm_disk_id IN

NER JOIN v4_2_latest_configuration_vms vms ON vms.vm_id = devices.vm_id INNER JOIN v4_2_latest_configuration_vms_disks disks ON disks.vm_disk_id = samples.vm_disk_id LEFT OUTER JOIN (SELECT v

m_name, AVG(previous_actual_size) AS previous_actual_size, AVG(previous_total_size) AS previous_total_size FROM (SELEC…

 

oVirt Engine is configured with 128 GB memory and 24 cores.

 

Please advice how to adress this.

 

Thank you and all the best,

Oliver

 

_______________________________________________
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/JJWRQKGCIHRG765YJCEG5CV6BJTFPFAO/

_______________________________________________
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/BW6GWQ43ACOPMXBZZKLRPF6TUTVOU7WD/