This section provides additional tools that may be useful for system administrators who maintain the the Partek^® Flow^® server.
 

...

At anytime, you wish to know the status of Partek Flow:
$ service partekflowd status
Possible outputs are RUNNING or STOPPED.

To find out the current Flow installation path, run:

Locating the

...

log files

• The

...

• Partek Flow server log is contained in the file 

...

• /opt/partek_flow/logs/catalina.out
  In some cases, it may be necessary to run $ ps aux | grep flow to determine the current Partek Flow installation path. That should lead us to the most recent catalina.out file.  

• To zip all the logs of Partek Flow (server and task logs)
  
  1. zip /opt/partek_flow/logs/
  2. zip /home/flow/.partekflow/logs (or the whole .partekflow folder that has the database)
  These zipped files contain the complete logs of Partek Flow and can be sent to Partek technical support for troubleshooting. Note that running the flowstatus.sh script and sending the error report would upload these files to Partek.

Changing the Temporary Folder Location

By default, temporary files resulting from genomic data uploads to Flow are stored in /opt/partek_flow/temp and are removed upon upload completion. If Flow is installed on a small root partition (<20GB), exceedingly large uploads may fill the root partition and necessitate moving this temporary directory to a larger partition. In order to select a new Flow temp folder, complete the following logged in as root:

...

1. Install Partek Flow as described earlier in this document.
   When prompted for license, paste the license generated for the new machine. 
   
   
2. Shutdown Partek Flow to install previous database:
   $ sudo service partekflowd stop
   
   
3. Unpack partekflowdb.bkup.tgz:
   $ sudo su - flow
   $ tar -xzvf partekflowdb.bkup.tgz
   $ exit
   
   

4. Restart Partek Flow
   $ sudo service partekflowd start 

...

...

...