The reports from Analyze -> Summary will not return values if the captured packets are not indexed. Releases previous to 8.2.1 required extended startup time for the indexing process after a reboot on systems with larger packet capture databases. The startup timeout must be extended to correct this.
The startup process has been streamlined and there are also health tests to check for and notify the administrators if the indexing process (shaft) has failed.
Release : 7.3.6
There are some systems with very large packet capture filesystems and the indexing process (shaft) may be canceled if it takes too long to start.
To correct this, the number of seconds configured in TimeoutStartSec must be extended. This allows the shaft indexing process to get started before it is deemed to have failed and killed.