After upgrading to NetWitness Logs & Network 10.6.x, the NetWitness UI (web interface which listens on port 443/TCP) may not be immediately available and performance of the NetWitness head-unit server may be very slow.
This can be caused if the collectd service is performing a migration of the rsa-sms RRD files. This is seen as multiple python processes in a 'top' output with moderate CPU usage on the NetWitness head-unit server.
This process is automatic and will complete eventually. Once the rsa-sms service has started, then the jettysrv service can fully load. Progress can be tracked through the collectd's SMS_RRD_migration logs.
# cd /var/lib/netwitness/collectd
# ls -ltr
-rw-r--r--. 1 root root 532351827 Jan 19 16:54 stats.tgz
drwxr-xr-x. 83 root root 4096 Feb 3 23:15 rrd
-rw-r--r--. 1 root root 2054193 Mar 2 05:50 SMS_RRD_migration_20160302052940.log
-rw-r--r--. 1 root root 2040073 Mar 2 05:50 SMS_RRD_migration_20160302053311.log
-rw-r--r--. 1 root root 2031828 Mar 2 05:50 SMS_RRD_migration_20160302053312.log
The /etc/init/jettysrv.conf file shows the service dependencies for the jettysrv upstart service.
In NetWitness 10.6.x, the jettysrv service depends on the following services to be running before the NetWitness UI will be available: rabbitmq-server, tokumx and rsa-sms These Linux System V services are located in /etc/rc.d/init.dand can be checked using:
service rabbitmq-server status
service tokumx status
service sa-sms status