We just published patch release 5 for version 4.3! Changes since previous patch release:
- Fixed bug in X.509 certificate subject and issuer decoding
- Agent tunnel listener will not start if server certificate is not loaded
- Fixed WEB service configuration import with multiple headers
- Fixed login issues in new web UI
- Small fixes and improvements in new management client application
Fixed issues:
- NX-2272 (Session is not closed if user cancel 2FA auth initialization)
- NX-2276 (Warn user when adding too wide mask to active discovery)
- NX-2388 (Modify default templates - filesystem with type "ahafs" should be excluded from discovery)
- NX-2404 (Integer division by zero in NXSL crashes server)
- NX-2406 (Entering maintenance mode on cluster does not trigger maintenance mode on nodes within cluster)
Hi Victor, good work.
Upgrading from 4.3.4 to 4.3.5 I had the following problem:
QuoteRunning background upgrade procedure for version 43.9
Converting table maintenance_journal
Running background upgrade procedure for version 43.9
Converting table maintenance_journal
SQL query failed (42P01 ERROR: relation "maintenance_journal_v43_9" does not exist
LINE 1: ...eation_time),to_timestamp(modification_time) FROM maintenanc...
^):
...
Running
nxdbmgr background-upgradeQuoteConverting table maintenance_journal
SQL query failed (42P01 ERROR: relation "maintenance_journal_v43_9" does not exist
Thanks in advance
Hi,
are you using TimescaleDB?
Best regards,
Victor
Can you check if you actually have tables maintenance_journal and maintenance_journal_v43_9, and if table maintenance_journal is a hypertable?
If you are not using maintenance journal functionality you can safely ignore this error, just make sure that hypertable maintenance_journal exists.
Best regards,
Victor
Quote from: Victor Kirhenshtein on April 26, 2023, 02:50:09 PMCan you check if you actually have tables maintenance_journal and maintenance_journal_v43_9, and if table maintenance_journal is a hypertable?
If you are not using maintenance journal functionality you can safely ignore this error, just make sure that hypertable maintenance_journal exists.
Best regards,
Victor
I'm sorry for the late reply,
There is only maintenance_journal which is a hypertable. Is it possible to manually adjust this situation? Would it be safe to upgrade to new versions?
Thanks,
Seems that actual conversion was already done. Execute the following SQL statement:
UPDATE metadata SET var_value='' WHERE var_name='PendingOnlineUpgrades';
This will inform nxdbmgr that all pending background updates are completed.
Yes, it should be safe to upgrade to 4.3.6.
Best regards,
Victor