Veritas Cluster Server Release Notes
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
69<br />
Error message displayed when ProPCV prevents a process from<br />
coming ONLINE to prevent concurrency violation does not have<br />
I18N support [2848011]<br />
The following message is seen when ProPCV prevents a process from coming<br />
ONLINE to prevent concurrency violation. The message is displayed in English and<br />
does not have I18N support.<br />
Concurrency Violation detected by VCS AMF.<br />
Process will be prevented from startup.<br />
Workaround: No Workaround.<br />
Error message seen during system shutdown [2954309]<br />
During some system shutdowns, you might see the following message in the syslog.<br />
Stopping AMF...<br />
AMF amfconfig ERROR V-292-2-405 AMF_UNCONFIG failed, return value = -1<br />
The system continues to proceed with the shutdown.<br />
Workaround: No workaround.<br />
System panics when getnotification requests access of<br />
groups cleaned by AMF [2848009]<br />
AMF while handling an agent that has faulted due to external or internal activity,<br />
cleans up the groups monitored by the agent. Simultaneously, if the agent notification<br />
is in progress and the getnotification thread requests to access an already<br />
deleted group, the system panics.<br />
Workaround: No workaround.<br />
The libvxamf library encounters an error condition while doing<br />
a process table scan [2848007]<br />
Sometimes, while doing a process table scan, the libvxamf encounters an error<br />
condition. As a result, the process offline registration with AMF fails. In most cases,<br />
this registration succeeds when tried again by the agent during the next monitor<br />
cycle for this resource. This is not a catastrophic failure as the traditional monitoring<br />
continues for this resource.<br />
Workaround: No workaround.