Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Issues related to installation and upgrade
Application resource running in a container with PidFiles attribute reports offline on upgrade to VCS 6.0 or later [2850927]
Application resource configured to run in a container configured with PidFiles attribute reports state as offline after upgrade to Veritas InfoScale 6.0 or later versions.
When you upgrade Veritas 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 Veritas InfoScale 7.4.2, 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 Veritas 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 Veritas 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