Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_components:qoestor:install_and_update:update [2023/08/29 07:45] – edrudichgmailcom | en:dpi:dpi_components:qoestor:install_and_update:update [2024/09/26 15:29] (current) – external edit 127.0.0.1 |
|---|
| - Stop DB <code>fastor-db-stop</code> | - Stop DB <code>fastor-db-stop</code> |
| |
| Updating is performed using the same scripts as in the [[en:dpi:dpi_components:qoestor:install_and_update:start#installation |Installation]] section. | Updating is performed using the same scripts as in the [[en:dpi:dpi_components:qoestor:install_and_update:install|Installation]] section. |
| |
| | |
| | <note important>In some systems, the database starts very slowly (from several minutes to several tens of minutes, especially in systems with long-term data storage) and when updating you may receive an error like **ERROR: while updating DB scheme** |
| | |
| | {{:dpi:dpi_components:qoestor:dbcheme_update_err.png?600|}} |
| | |
| | Wait for the database to start. You can check the tail /var/log/clickhouse-server/clickhouse-server.log logs, or simply try to launch the clickhouse-client client - if there is a connection, then the database has started and is ready for connections. |
| | |
| | |
| | After starting the database, run the command <code>fastor-db-scheme</code> |
| | </note> |
| <note important>Do not forget to execute <code>fastor-db-scheme</code> after update. This insures cases when the schema does not have time to update as a result of a long restart of the database. </note> | <note important>Do not forget to execute <code>fastor-db-scheme</code> after update. This insures cases when the schema does not have time to update as a result of a long restart of the database. </note> |
| | |
| | <note warning>If QoE Stor is installed on CentOS 7, use the [[en:dpi:dpi_components:qoestor:install_and_update:update:centos7]] guide.</note> |
