Reports showing 0% processing on central manager
Article ID: 215081
Updated On:
Products
Issue/Introduction
After configuring the Security Analytics central manager and connecting all sensors successfully, reports are not completing. All sensor reports show 0% processing and never complete. Sensors reports work just fine when directly connected.
Cause
There is a connectivity or authentication issue between the central manager and the sensors.
Resolution
To see exactly what is going on between the central manager and the sensor, run the following command as root from the both the central manager and the sensor and look for any errors.
scm cmc test_connection
If the problem is not evident in the output, contact technical support for additional troubleshooting help.
Additional Information
The following is output that you will see from the scm cmc test_connection commands:
Output from central manager:
scm cmc test_connection
OpenVPN status
-------------------------------------------------
OpenVPN is on
Connection successful
-------------------------------------------------
Testing Connectivity to all the Sensors
CA Connections
7: (dot53) Virtual ##.##.##.## - Real ##.##.##.##:34279 - Success
8: (dot50) Virtual ##.##.##.## - Real ##.##.##.##:57065 - Success
-------------------------------------------------
-------------------------------------------------
/etc/pgbouncer/additional.ini
listen_addr = ##.##.##.##
listen_port = 6432
-------------------------------------------------
/etc/pgbouncer/database.ini
dsweb = dbname=dsweb pool_size=5000 max_db_connections=150 pool_mode=transaction user=dsweb
-------------------------------------------------
/etc/pgbouncer/userlist.txt
"dsweb" "sha_hash"
"dsweb-##.##.##.##" "sha_hash"
The following is sample output that you will see from the sensors:
scm cmc test_connection
OpenVPN status
-------------------------------------------------
OpenVPN is on
Connection successful
-------------------------------------------------
Testing Connectivity to all the CMCs
CA IP: ##.##.##.##
0: Virtual: ##.##.##.## Real ##.##.##.## - Success
-------------------------------------------------
/etc/pgbouncer/additional.ini
listen_addr = 127.0.0.1
listen_port = 6432
-------------------------------------------------
/etc/pgbouncer/database.ini
dsweb-##.##.##.## = dbname=dsweb pool_size=50 max_db_connections=5 pool_mode=transaction host=##.##.##.## port=6432
-------------------------------------------------
/etc/pgbouncer/userlist.txt
"dsweb-##.##.##.##" "sha_hash"
-------------------------------------------------
Testing pgbouncer connection to each cmc
Testing cmc pgbouncer connection
Db params: host=##.##.##.## port=6432 dbname=dsweb
Connected to PGBouncer
Testing local pgbouncer connection
Db params: host=localhost port=6432 dbname=dsweb-##.##.##.##
Connected to PGBouncer
Feedback
