Memory Troubleshooting

Provisioning Failures

Detailed information on any provisioning issues can be found in the VSP-memory-assist logs.

Windows – Auto-instrumentation enabled

Symptom: Auto-instrumentation is enabled and provisioning fails 

Recommended Actions: 

1. Ensure that an entry for the application that is being provisioned does not exist in the registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
2. If it exists, VSP-Memory does not overwrite any existing entry (to prevent breaking any existing functionality)
   1. Remove the registry key if possible and re-provision the application
   2. If the key cannot be removed, uncheck the auto-instrumentation option in CMS and re-provision the application. After the application is provisioned, instrument the application manually

Linux – Auto-instrumentation enabled

Symptom: Auto-instrumentation is enabled and provisioning fails 

Recommended Actions: 

1. Refer the VSP-memory-assist logs for information on where the issue occurred
2. If this application has been auto-instrumented previously, check the application path to see if existing VSP-memory auto-instrumentation binaries exist
   1. VSP-memory auto-instruments applications by renaming the original application with a “-virsec” appendage. A special VSP-memory auto-instrumentation binary is copied to the application path. When the application is started, the VSP-memory auto-instrumentation binary calls the real application with the “-virsec” appendage
   2. If provisioning fails after auto-instrumentation, rename the “-virsec” or “-virsec.backup” version of the application back the original name. Remove any remaining “-virsec*” binaries

Auto-instrumentation disabled

Symptom: Auto-instrumentation is disabled and provisioning fails 

Recommended Actions: 

1. Ensure the application path provided in CMS exists
2. Refer the VSP-memory-assist logs for more information

Auto-instrumentation Failures

VSP-memory auto-instrumentation in Windows may fail because the targeted application may already have an existing entry in the Image File Execution Options registry setting (located in: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options).  If so, VSP-memory does not overwrite any existing entry. To continue provisioning, either remove the IFEO entry for the targeted application or turn off auto-instrumentation via CMS and instrument the application manually.

Application status not Normal

Symptom: Application is not moving to the normal state in CMS

Recommended Actions: 

1. Check the VSP-memory-assist statistics file to determine if the number of “app-alives sent” counter is increasing over time
2. If it is not going up, ensure the application is running on the host. The VSP-memory-assist logs record whether the APP_START message is received from the application
3. If the count is going up, but CMS is not showing the application as normal, it is likely to be a network issue or a CMS-internal issue that may require further triaging