opFlow 2.5.x upgrade instructions

This documentation assumes you are upgrading from 2.4.X and currently have opFlow reports running.

Upgrade files

1. Backup your existing installation 

   cd /usr/local
   cp -r opmantek opmantek_backup_`date +%F-%T`

2. Obtain a copy of the tarball, from now on it will be assumed the file is in /tmp

3. Stop daemons 

   service opflowd stop

4. Untar 

   cd /usr/local
   tar -zxvf /tmp/opFlow-Linux-x86_64-2.5.X-release.tar.gz   

5. Update config files 

   cd /usr/local/opmantek
   ./bin/opupdateconfig.pl install/opFlow.nmis conf/opFlow.nmis
   ./bin/opupdateconfig.pl install/opCommon.nmis conf/opCommon.nmis    

6. opFlow database now uses capped sizes, please adjust the following config settings to make sure they fit on your partition and are the size you want (the defaults are listed):

   # /usr/local/opmantek/conf/opFlow.nmis:
   'opflow_db_conversation_collection_size' => 16106127360, #15G
   'opflow_db_flow_collection_size' => 5368709120 # 5G
   
   

   To see the current sizes or check what the current config will do run the setup tool: 

   /usr/local/opmantek/bin/opflow_setup.pl setup=db_config

   
   If you do not want to keep existing data, drop your current database, which will free all space and then skip the next step (7).
    

7. When you are happy with the configuration, run the setup tool again with force, this will upgrade your existing collections to capped collections, expanding/shrinking based on the requested size.  Expect this to take a while.

   /usr/local/opmantek/bin/opflow_setup.pl setup=db_config force=1

    

   1. Optional: running the setup tool with force, run repairDatabase on mongo to reclaim space, as it will likely be 2x larger than it was previously.  You must have free space = current size of DB to perform this operation. Expect this to take a while.

      mongo
      use nmis; // (replace with custom db name if you changed from defaults, might be opflow)
      db.auth('opUserRW','op42flow42'); // again, replace with custom credentials if you have changed them from defaults
      db.repairDatabase();

8. Fix permissions 

   cd /usr/local/opmantek/bin
   ./opfixperms.pl  

9. Make sure everything is setup: 

   /usr/local/opmantek/bin/opflow_setup.pl setup=all

   Double check script output for any errors or activities you may need to perform, also double check that the existing cron entries match up with the ones listed by the setup tool.

10. Start Daemons 

    service opflowd start 

     

    1. Debian/Ubuntu

       Verify/Edit /etc/init.d/flowd, /etc/init.d/mongod and /etc/init.d/opflowd

       #change this line: 
       . /etc/init.d/functions
       #to this: 
       . /lib/lsb/init-functions