Veritas Storage Foundation and High Availability Solutions Release Notes

114About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: No workaround.AMF displays StartProgram name multiple times on the console without aVCS error code or logs [2872064]When VCS AMF prevents a process from starting, it displays a message on theconsole and in syslog. The message contains the signature of the process that wasprevented from starting. In some cases, this signature might not match thesignature visible in the PS output. For example, the name of the shell script thatwas prevented from executing will be printed twice.Workaround: No workaround.Terminating the imfd daemon orphans the vxnotify process [2728787]If you terminate imfd daemon using the kill -9 command, the vxnotify processcreated by imfd does not exit automatically but gets orphaned. However, if youstop imfd daemon with the amfconfig -D command, the corresponding vxnotifyprocess is terminated.Workaround: The correct way to stop any daemon is to gracefully stop it with theappropriate command (which is amfconfig -D command in this case), or toterminate the daemon using Session-ID. Session-ID is the -PID (negative PID) ofthe daemon.For example:# kill -9 27824Stopping the daemon gracefully stops all the child processes spawned by thedaemon. However, using kill -9 pid to terminate a daemon is not a recommendedoption to stop a daemon, and subsequently you must kill other child processes ofthe daemon manually.Issues related to the Cluster Manager (Java Console)This section covers the issues related to the Cluster Manager (Java Console).Some Cluster Manager features fail to work in a firewall setup [1392406]In certain environments with firewall configurations between the Cluster Managerand the VCS cluster, the Cluster Manager fails with the following error message:V-16-10-13 Could not create CmdClient. Command Servermay not be running on this system.Workaround: You must open port 14150 on all the cluster nodes.