Hi,
I am the progress of updating from 5.4.7 to 6.0.1 on Centos8. The database is postgres 13 with TimescaleDB version: 20500. The database has been stuck in the automatic database upgrade phase for some time without any error as per below and I am a bit split in how to proceed. This process has usually been very fast in the past upgrading from previous versions. I will let it stay like so for a bit and hopefully it will get moving but in case it does not does anyone have any experience with this scenario? Can I restart the zabbix server and hope that this would restart the upgrade process or would this likely break it? I would assume that as it has already started if I would chose to revert the upgrade I would need restore the database from backup.
4171891:20220306:215743.826 starting automatic database upgrade
4171891:20220306:215743.911 completed 0% of database upgrade
4171891:20220306:215743.937 completed 1% of database upgrade
4171891:20220306:215743.939 completed 2% of database upgrade
4171891:20220306:215743.943 completed 3% of database upgrade
4171891:20220306:215743.945 completed 4% of database upgrade
4171891:20220306:215743.948 completed 5% of database upgrade
4171891:20220306:215743.951 completed 6% of database upgrade
Any opinions appreciated
I am the progress of updating from 5.4.7 to 6.0.1 on Centos8. The database is postgres 13 with TimescaleDB version: 20500. The database has been stuck in the automatic database upgrade phase for some time without any error as per below and I am a bit split in how to proceed. This process has usually been very fast in the past upgrading from previous versions. I will let it stay like so for a bit and hopefully it will get moving but in case it does not does anyone have any experience with this scenario? Can I restart the zabbix server and hope that this would restart the upgrade process or would this likely break it? I would assume that as it has already started if I would chose to revert the upgrade I would need restore the database from backup.
4171891:20220306:215743.826 starting automatic database upgrade
4171891:20220306:215743.911 completed 0% of database upgrade
4171891:20220306:215743.937 completed 1% of database upgrade
4171891:20220306:215743.939 completed 2% of database upgrade
4171891:20220306:215743.943 completed 3% of database upgrade
4171891:20220306:215743.945 completed 4% of database upgrade
4171891:20220306:215743.948 completed 5% of database upgrade
4171891:20220306:215743.951 completed 6% of database upgrade
Any opinions appreciated
Comment