FlowTraq: Unable to connect to Flow Server error

Categories:
Solution Number:
S35481
Last Modified:
2022-03-29
Issue
The main issue is usually that the FlowTraq daemon has stopped running.
 
Solution
If they send a screenshot of the login screen, check "Portal Address" – if it says "127.0.0.1" or "localhost" it's probably the FlowTraq daemon being shut down. If it says anything else, they're likely running the Web UI on a separate box and may have lost connectivity.
The primary cause of the FlowTraq daemon stopping is that the server has run out of disk space. This is a very difficult fault to catch reliably. “Quickview” directory size is a significant cause of failure for some users. “Quickviews” by default are 8GB each for each of three granularities, and on older systems that have been upgraded can cause it to run low.
Another common cause is that simply setting “SESSIONDB” or “ARCHIVEDB” is too large for their disks. In both cases, check the output of the command "df -h" and look for any disk that's ~100% full. Then check /opt/flowtraq/flowtraq.conf to find the configured sizes.
Always check /opt/flowtraq/flowtraq.log for any error messages – or an indication that someone shut the daemon down on purpose.
Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case