...
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
...
Code Block |
---|
scp opExport-New-Version.tar.gz user@server:/tmp/ |
Upgrade Steps
Code Block |
---|
cd /usr/local/omk |
Backup old configuration installation
Code Block mkdir conf_date_here cp -r conf/* conf_date_hereomk omk-backup-<date>/
Stop the current service
Code Block 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 #more than one omkd use these instructions, note: do not use service omkd stop if you have more than one opmantek.exe ps -ef | grep opmantek.exe [root@server # if that does not work try kill `cat /tmp/prefork.pid`~]# 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
Untar the new version
Code Block cd /usr/local tar -zxvf ~/tmp/opExport-New-Version.tar.gz
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
Clean up old files (very important if server has fallen behind)
Code Block rm /usr/local/omk/log/* rm -rf /usr/local/omk/var/perf/*
Start the service back up
Code Block service omkd start
- Load the upgraded GUI in a 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!
Push schema to NMIS server from MySQL (only if the upgraded server is NMIS server) .
Load the MySQL Server GUI in web browser http://your.MySQL.Server:3000/omk/opExport, push the schema to the upgraded server