Important Upgrade Notes for KnowledgeTree

From KnowledgeTree Document Management Made Simple

1 Upgrades to KnowledgeTree 3.5.X
- 1.1 Known Issues - Upgrading to 3.5.2, 3.5.2a or 3.5.2b
2 Upgrades to KnowledgeTree 3.4
3 Upgrades to KnowledgeTree 3.3

Upgrades to KnowledgeTree 3.5.X

Please note: Upgrades to version 3.5.2 from Beta and Release Candidate versions are not supported.

Before you begin ...
- Please backup your repository.

[edit]

Known Issues - Upgrading to 3.5.2, 3.5.2a or 3.5.2b

Upgrading from KnowledgeTree 3.1b, 3.3.7, or 3.4.2?

Upgrades to 3.5.x series fails when upgrading from the following versions: 3.1b, 3.3.7, and 3.4.2. The workaround is to first upgrade to 3.4.6; then, upgrade to 3.5.x

3.4.6 Upgrade Installers are available for download from the Download older versions of KnowledgeTree Server and Tools 
section on the Commercial Editions Download page.

When the upgrade installer does not automatically stop MySQL processes, upgrade fails

The MySQL service should be stopped automatically by the upgrade installer before installing the new version. When the MySQL service is not stopped, the upgrade fails with the following error message: 'Can't copy ktdms/mysql to ktdms/backup/mysql...'.

To resolve this issue, perform the following steps:

Step 1: Stop ktdms mysql processes

Temporarily disable services, jobs, systems that automatically start KnowledgeTree processes - e.g. any cron jobs, heartbeat systems, etc.
Use the following code to check if there are any ktdms mysql processes that failed to stop:

ps aux | grep mysql

If you have one MySQL server running, use: killall -TERM mysqld.bin

NOTE: If you have more than one server, restart the second server (the other mysql service you may have running) after this command or you can use alternate kill commands to kill just the ktdms mysql processes. (See 'man kill' - a unix/linux command you run to see the system manual page for the kill command).

2. Ensure that you have a backup of your current installation. See the following example:

Code:  
cp -a /opt/ktdms /opt/ktdms.old

NOTE: If the copy fails again you still have mysql processes hanging around. Go to step 1 above.

3. Restore the automatic backup made by the upgrade installer. See the following example:

Code:
cp -a /opt/ktdms/backup/* /opt/ktdms/

NOTE: Your system should be back to it's original state at this point.

4. Start the upgrade process again. The upgrade should now run successfully.

More Notes: 
* The upgrade installer uses the the mysql.pid file (e.g. /opt/ktdms/mysql/data/mysql.pid) 
to determine which mysql process(es) to kill before install - if any.
* The "dmsctl.sh stop" command will not work when the upgrade has failed in the manner 
described above. However, once you have completed step 3 above (restore automatic backup 
made by the upgrade installer), it should be functioning again.

[edit]