Applies to VoipNow 3.5!
Sometimes, when upgrading from VoipNow SPE 3.x.x to VoipNow 3.5.0, you will notice that the upgrade process takes a lot of time. Whenever you're in such a situation, do not stop the upgrade process as it might ruin the entire upgrade. Instead, before starting the upgrade, perform a full table conversion as explained below.
It is assumed that you are using a CentOS 6.x/CentOS 7.x and you have latest version of VoipNow 3.5 installed.
As of VoipNow 3.5, due to several improvements made on the InnoDB storage engine of MariaDB, we decided to perform full table conversion from MyISAM to InnoDB for the call_history, ast_cdr, ast_queue_log, dictionary tables. The conversion is performed by the VoipNow installer script.
If your server has millions of records, the upgrade might take hours to complete; it depends mostly on the server specs. To avoid doing the conversion by the installer script, execute the following command before running the installer:
To perform the upgrade later, you need to log in to SQL (credentials are found in /etc/voipnow/.sqldb) and then run the following command:
ALTER TABLE ast_queue_log ENGINE=InnoDB;
ALTER TABLE ast_cdr ENGINE=InnoDB;
ALTER TABLE dictionary ENGINE=InnoDB;
ALTER TABLE call_history ENGINE=InnoDB;
This process can take a while as it depends on the table size and hardware resources.
It is recommended that you do the conversion during off-peak hours.
|Content by Label|
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.