Performance issue: buffer usage process not running
The buffer usage process is running on the system to monitor the sniffer and populate the Buffer usage monitor report. If this process is not running, the report is not populated.
Symptoms
Key columns in the Buffer usage monitor report: TimestampCauses
A common cause of this is the internal database previously filled up to 90% and the buffer usage process was not restarted afterwards.Diagnosing the problem
Check the timestamp column of the report and the run time parameters. Does the report have one row every minute up to the current time?Using the CLI, check if the database is close to full: support show db-status used %.
Resolving the problem
If the Buffer usage monitor report does have one row every minute up to the current time, the buffer usage process should be restarted.If the database is more than 75% full or unusually full for the appliance, consider purging more data. See Purging data to resolve a full disk when the GUI is down.
If the database is at a normal size, restart the buffer usage process.
To restart the buffer usage process, run:
restart stopped_services
restart sniffer_buffer_usage