Application resource running in a container with PidFiles attribute reports offline on upgrade to VCS 6.0 or later

Last published : Sep 18, 2026
Application resource configured to run in a container configured with PidFiles attribute reports state as offline after upgrade to InfoScale 6.0 or later versions.
When you upgrade InfoScale from lower versions to 6.0 or later, if application resources are configured to run in a container with monitoring method set to PidFiles, then upgrade may cause the state of the resources to be reported as offline. This is due to changes introduced in the Application agent where if the resource is configured to run in a container and has PidFiles configured for monitoring the resource then the value expected for this attribute is the pathname of the PID file relative to the zone root.
In releases prior to InfoScale 9.0, the value expected for the attribute was the pathname of the PID file including the zone root.
For example, a configuration extract of an application resource configured in InfoScale 5.0MP3 to run in a container would appear as follows:
Application apptest (
User = root
StartProgram = "/ApplicationTest/app_test_start"
StopProgram = "/ApplicationTest/app_test_stop"
PidFiles = {
      "/zones/testzone/root/var/tmp/apptest.pid" }
ContainerName = testzone
)
Whereas, the same resource if configured in InfoScale 6.0 and later releases would be configured as follows:
Application apptest (
User = root
StartProgram = "/ApplicationTest/app_test_start"
StopProgram = "/ApplicationTest/app_test_stop"
PidFiles = {
      "/var/tmp/apptest.pid" }
)
Note: The container information is set at the service group level.
Workaround: Modify the PidFiles pathname to be relative to the zone root as shown in the latter part of the example.
\# hares -modify apptest PidFiles /var/tmp/apptest.pid