6:49 a.m.
I'm not sure if this one is related to "time shift" in the DB (as I found
that dwh_history_timekeeping had some entries 1 month ahead/ETL service issues also/, but
I keep getting spammed that the host has been activated.
Any hint ?
Best Regards,
Strahil Nikolov
9:37 a.m.
On Thu, Jun 11, 2020 at 6:55 AM Strahil Nikolov via Users
<users(a)ovirt.org> wrote:
I'm not sure if this one is related to "time shift" in the DB (as I found
that dwh_history_timekeeping had some entries 1 month ahead/ETL service issues also/, but
I keep getting spammed that the host has been activated.
Any hint ?
I'd start with:
1. Check (in /var/log) if you had a case of time moving forward and
than backward for some weird reason
2. Dump the entire db (engine, perhaps also dwh if you want) and
search for future dates. If you only find a few, it might be easier to
handle them one-by-one (hopefully by updating the relevant entity from
the UI, not directly in the db). If it's many, it might require
something more significant.
In 4.4, that's just:
su - postgres -c 'pg_dump engine' | less
In 4.3:
su - postgres -c 'scl enable rh-postgresql10 "pg_dump engine"' | less
Then search e.g. '2020-07', or '2020-06-2', etc.
Best regards,
--
Didi
11:27 a.m.
New subject: ovirt 4.3.10 Web UI constantly "finished activating host"
Hey Didi,
it seems that there is still timeshift in the DB - lots of stuff was reporting ahead of
time.
I had to update the table jobs with the correct month and now at least I have no more spam
in the web ui.
Best Regards,
Strahil Nikolov
В четвъртък, 11 юни 2020 г., 9:39:45 ч. Гринуич+3, Yedidyah Bar David
<didi(a)redhat.com> написа:
On Thu, Jun 11, 2020 at 6:55 AM Strahil Nikolov via Users
<users(a)ovirt.org> wrote:
I'm not sure if this one is related to "time shift" in the DB (as I found
that dwh_history_timekeeping had some entries 1 month ahead/ETL service issues also/, but
I keep getting spammed that the host has been activated.
Any hint ?
I'd start with:
1. Check (in /var/log) if you had a case of time moving forward and
than backward for some weird reason
2. Dump the entire db (engine, perhaps also dwh if you want) and
search for future dates. If you only find a few, it might be easier to
handle them one-by-one (hopefully by updating the relevant entity from
the UI, not directly in the db). If it's many, it might require
something more significant.
In 4.4, that's just:
su - postgres -c 'pg_dump engine' | less
In 4.3:
su - postgres -c 'scl enable rh-postgresql10 "pg_dump engine"' | less
Then search e.g. '2020-07', or '2020-06-2', etc.
Best regards,
--
Didi
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XREOMRKOGY5...
1622
days inactive
1625
days old
2 comments
2 participants
participants (2)
-
Strahil Nikolov -
Yedidyah Bar David