No Data in NFA reports "An error occurred! Control(3002)"

Document ID : KB000122485
Last Modified Date : 11/12/2018
Show Technical Document Details
Issue:
When loading a report in NFA, no data is seen and an error message like below is seen:
An error occurred!
Control(30002): Stacked Protocol Trend - In

A Unable to connect to any of the specified MySQL hosts. error was returned: at MySql.Data.MySqlClient.NativeDriver.Open() 
 
User-added image
Cause:
NetQos NQMysql service on the Harvesters is either down or in a hung state.
Port 3307 is blocked between the Console and the Harvester servers. 
CA Anomaly Detector can cause the NQMysql service to be overloaded in high volume environments. 
Resolution:
1. RDP to the Harvester server that holds the data for this device.

2. Check to see if the Netqos NQMysql Service(on Windows) or the nfa_mysqlCSE service on RedHat is running, if it is stopped start it.
For RedHat run:  service nfa_mysqlCSE start

3. If it is running, log in to MySql by running:
mysql -P3307

4. Then run:
show processlist;

5. Check for any queries that do not say Sleep and that are running for a long time in the "Time" column and make note of the "ID" for that query.

6. Run the command below to kill that ID where x is the ID of the query that is running for a long period of time:
kill x

7. The restart the NetQos NQMysql service. 

8. RDP to the NFA Console server and verify the port is open between the Console and Harvester by running the following where x.x.x.x is the IP address of the Harvester server:
mysql -unetqos -pnetqos -P3307 -h x.x.x.x

9. Then try loading the report again and it should show data.

10. If the service goes down again create a log file in the \CA\NFA\Netflow\data directory(/opt/CA/NFA/Netflow/logs on Redhat) named "NFAStorageEngine.log"
      Note if you create this log file on RedHat, you must change the permissions on the file to be owned by the 'nfa' user and group.
            chown nfa:nfa /opt/CA/NFA/Netflow/logs/NFAStorageEngine.log

    Then restart the service after creating the log file.  Sometimes it will log additional information, and sometimes that is enough to stop the service from going down again in the future. 

 
Additional Information:
If you are running CA Anomaly Detector, you may need to shut down the CA NFA Hunter Tracker Service on the Anomaly Detector server and Anomaly Detector can fill up the mysql connections on high volume Harvesters.