Known Limitations

Distribution

21907: Hard reboot of instance can corrupt running Docker container
	Due to a known Docker bug (https://github.com/docker/containerd/pull/410) , 
	Docker may hang after an instance reboot due to containers that were not shut 
	down completely. 
	
	When this happens, users will note that MySQL, Docker, and Host displays will not 
	populate, and they will not be able to store historical data. 
	
	To avoid this, users can manually stop Docker containers before rebooting their 
	instance. 
	
	$ docker stop MYSQL 
	$ docker stop rtvHostAgent 
	$ docker stop cadvisor-rtview
	
	To recover an instance if this has already occurred, users can manually clear the 
	Docker container state by doing the following. Do not try this if you are not 
	comfortable working in a Linux shell environment, as it will involve deleting 
	files as root user. 
	
	- SSH into your Amazon EC2 instance 
	$ sudo su ? 
	$ sudo service docker stop
	$ sudo ls /var/run/docker/libcontainerd 
	$ sudo ls /var/run/docker/libcontainerd/containerd
	- take note of any directories with very long names, such as: 
	
	7b9a95fd9de14456add57cdd7b74a833348a2cf81075b72121cd08bde552ff6d 
	b2a3d5c0f4021609bf1ed4e3d2268978febe801f4355e75f451840d3e6497d77 
	e97f5b0ae0af7731a3af90d78cb6d43c9313acaf1dad70220ab2874f3b44d53d 
	
	Under healthy shut down, these will not existing if a container is not running. 
	If you see them, then that indicates that your problem is caused by the Docker 
	bug described above 
	
	$ sudo rm -rf /var/run/docker/libcontainerd
	$ sudo service start docker 
	$ docker images
	- you should now see your three docker containers
	$ docker ps
	- your containers may have already restarted. If you do not see all three 
	containers, then you can manually start them by typing: 
	$ docker start MYSQL
	$ docker start rtvHostAgent
	$ docker start cadvisor-rtview

Key Metrics

20205: "Response Time" KM for WSM mapped to non-history column
	The Response Time key metric for WebSphere (CI Type WAS-APP) is not supported in 
	the Key Metrics History displays at this time. 

20324: KM filtering is not supported on tablets
	The Filter in the Key Metrics displays cannot be modified when running on a 
	tablet. This is because the Filter is set via popup menu which is not supported 
	on tablets. 

Monitor

20157: History Table Statistics does not calculate Deltas until one update cycle passed
	The History Table Statistics display will initially show incorrect data for Delta 
	Rows. You must wait one update cycle for this to be resolved. 

Platform Support

21636: Agent cannot connect to receiver on OSX
	The RTVAgent servlet is not supported on Mac OS X.

Scripts

20838: "stop_rtv all" does not include a server listed after "viewer/builder" lines
	Documentation clarification:
	
	The rtvservers.dat file contains groups of servers called a "config", associated 
	by a common name, e.g. "central". Such groups must be contiguous in the file. 
	That is to say, a config may not be split up in the file; all the servers it 
	includes must appear contiguously. 

Solution Package

Docker

21559: Unable to remove a stopped container in Docker: 'device or resource busy'
	If cAdvisor is started after other containers, it prevents Docker from removing 
	those containers. If cAdvisor is the first container loaded into Docker, then 
	other containers can be removed without any issue. 
	
	The workaround is to start the cAdvisor before any other container.

MySQL

21923: MysqlServerProperties cache columns don't support mixed MySQL versions
	The MysqlServerProperties cache columns are created based on the first connection 
	property that returns result. If subsequent connection results return that are a 
	different version of MySQL, they may contain a different order or number of 
	columns. The result is that the MysqlServerProperties cache may show row values 
	in the wrong columns. 
	
	This problem only appears if you look at the cache directly for troubleshooting 
	purposes -- it does not effect any displays. 

Solace

21865: Calculated Totals on the Neighbor Summary display are not a direct sum
	The calculated totals field in the Solace Monitor "Neighbor Summary" display are 
	not always an exact sum of the above calculated fields. 
	
	This is because the values in the Totals row are not derived by adding up the 
	Data, Control, and Discards values. These calculations are derived from a direct 
	query to the Solace appliance of the total number of messages to its CSPF 
	Neighbors. The delta and rate calculations are therefor not always exact sum of 
	the calculations against the Data, Control, and Discarded messages. 

TIBCO Hawk

20568: HawkAlerts cache sometimes out of sync with with alerts in the Hawk Display
	There are 2 cases where the HawkAlerts cache may not be in sync with the Hawk 
	Alerts on an agent: 
	
	1. If RTView does not receive any updates for a HawkAlert for the amount of time 
	specified in $rtvHawkAlertClearTime + $rtvHawkAlertDeleteTime (defaults to 10 
	days + 1 hour), it is removed from the HawkAlerts cache. 
	
	2. When using a sender to update the HawkAlerts cache, any events that occur when 
	the sender is running but the receiver is not will be missed. To fix this, 
	restart the sender after any restart of the receiver. 

VMWare vSphere

20594: MySQL historian requires NO_BACKSLASH_ESCAPES
	The VMWMON package collect metrics about disk usage on Windows systems, which 
	results in the backslash (\) character being present in the data collected. 
	
	MySQL databases will not correctly store data with a backslash (\) unless the 
	NO_BACKSLASH_ESCAPES mode is enabled.