On Mon, Jan 2, 2023 at 2:33 PM Diego Ercolani <diego.ercolani@ssis.sm> wrote:
Finally it worked: After the step previous described: 1. put cluster in global maintenance 2. stop ovirt-engine and ovirt-engine-dwhd 3. in the table dwh_history_timekeeping @enginedb I changed the dwhUuid 4. launched engine-setup, the engine-setup asked to disconnect a "fantomatic" DWH (I answered "YES") 5. engine setup reconfigure things and set back the dwhUuid to the previous state 6. stopped ovirt-engine and ovirt-engine-dwhd because I saw that in the same table I had timestamp in the future (year 2177),
This might hint at the issue. I do not know the relevant logic well, sorry. Perhaps you had some local time issue which caused this line to be written? Perhaps there is then logic to not update/ignore/whatever stuff that's written "in the past". Anyway, good catch!
so I removed the erroneous timestamp (putting to [NULL]) 7. in the /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log I saw: Setting a value for the key "lastErrorSent" has failed. Error message: null Setting a value for the key "lastErrorSent" has failed. Error message: null so I put in "consistent" value:
This is my set: INSERT INTO public.dwh_history_timekeeping (var_name,var_value,var_datetime) VALUES ('dwhHostname','ovirt-engine.ovirt',NULL), ('dwhUuid','53878f7e-cb3d-45cc-9edf-9e389414ce6e',NULL), ('lastSampling',NULL,'2023-01-02 13:32:00.2+01'), ('lastSync',NULL,'2023-01-02 13:31:00+01'), ('lastErrorSent','2023-01-02 12:47:15.318 +0100','2023-01-02 12:47:15.318+01'), ('lastOsinfoSync','2023-01-02 12:47:15.318 +0100','2023-01-02 12:47:15.318+01'), ('lastFullHostCheck','2001-01-01 02:01:00.000 +0100','2023-01-02 13:03:00+01'), ('lastOsinfoUpdate','2023-01-02 12:47:15.318 +0100','2023-01-02 12:47:15.318455+01'), ('heartBeat',NULL,'2023-01-02 13:31:59.082+01'), ('timesFailed','0',NULL); INSERT INTO public.dwh_history_timekeeping (var_name,var_value,var_datetime) VALUES ('DwhCurrentlyRunning','1',NULL);
Best regards, -- Didi