flowstatus.sh script

Partek^® Flow^® comes with a standalone diagnostic script that reports how Partek Flow is installed and detects common installation problems. This script can be run independently of Partek Flow as installation issues or crashes can prevent Partek Flow from starting. This utility gathers Partek Flow log files and server information which, upon customer approval, will be sent to Partek so our support team has all requisite information to address the issue. Some examples of when this script should be run include:

...

Running flowstatus.sh via the command line

1. Locate the Partek Flow installation directory. This is defined as the FLOWhome variable in the file /etc/partekflow.conf.
   $ grep FLOWhome /etc/partekflowd.conf
   For this example, we assume the Partek Flow install directory is /opt/partek_flow. If it is not, replace it with the directory found in step 1.

2. Run the script
   $ bash /opt/partek_flow/flowstatus.sh
   After the script is run, a report will appear on the screen, then you will be asked if you wish to upload this report to Partek. If this report is uploaded, you will be contacted by support team who will assist with your issue. 

Running flowstatus.sh via the command line (alternative method)

If you get an error saying, "No such file or directory" or you are unable to find the flowstatus.sh script on your system, then run the following: 

...

$ curl -O  https://customer.partek.com/flowstatus.sh
$ bash flowstatus.sh

Interpreting flowstatus.sh reports

When running the flowstatus.sh script, you will see a report similar to Figure 2.

...

After displaying Partek Flow configuration information, several installation checks are performed. This covers common issues that can break a Partek Flow installation such as full disks or running Partek Flow under the wrong user account.

Sending the error report to Partek

At the end of the report, you will be given an option to send the error to Partek (Figure 3).

...