Page History

...

The new version will need to be downloaded and this tutorial assumes you have put it in ~/tmp, it can be anywhere you like but you will have to adjust the command to untar. 

Upgrade Steps

...

scp opExport-New-Version.tar.gz user@server:/tmp/

Upgrade Steps

cd /usr/local/omk

1. Backup old configuration installation 

   Code Block
   mkdir conf_date_here cp -r conf/* conf_date_hereomk omk-backup-<date>/

2. Stop the current service service (note, if your server is running multiple omkd then you will need to use ps -ef to find the correct one).  The opmante.exe WITHOUT the webserver is the one we want.

   Code Block

   service#more than one omkd use stopthese # if that does not work try kill `cat /tmp/prefork.pid` # verify it omkd is stopped ps aux | grep opman # if they are still running kill them killall opmantek.exe instructions ps -ef | grep opmantek.exe [root@server ~]# ps -ef | grep opmantek.exe root 944 742 0 20:44 pts/0 00:00:00 grep opmantek.exe root 16533 1 8 Dec12 ? 09:44:54 opmantek.exe root 20229 1 0 Dec06 ? 00:02:10 opmantek.exe webserver kill 16533 # (leave 20229, it is not opExport) ps aux | grep opmantek.exe

3. Untar the new version 

   Code Block
   cd /usr/local tar -zxvf ~/tmp/opExport-New-Version.tar.gz

4. Upgrade the configuration 

   Code Block
   cd /usr/local/omk cp ./bin/opupdateconfig.pl ./install/opCommon.nmis ./conf/ cp install/users.dat conf/ cd conf

   *if you are upgrading the MySQL server daemon, you will need new schemas: 

   Code Block
   cp install/*.json conf/opCommon.nmis

5. Start the service back up 

   Code Block
   service omkd start

6. Load the GUI in web browser http://your.upgraded.server.name.or.ip:3000/omk/opExport, this is required to accept the EULA, if this is not done schemas will not be saved in the next step!

   

7. Push schema to NMIS server from MySQL (only if the upgraded server is NMIS server) .