Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
70
AMF displays StartProgram name multiple times on the console
without a VCS error code or logs [2872064]
When VCS AMF prevents a process from starting, it displays a message on the
console and in syslog. The message contains the signature of the process that was
prevented from starting. In some cases, this signature might not match the signature
visible in the PS output. For example, the name of the shell script that was 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 process
created by imfd does not exit automatically but gets orphaned. However, if you stop
imfd daemon with the amfconfig -D command, the corresponding vxnotify
process is terminated.
Workaround: The correct way to stop any daemon is to gracefully stop it with the
appropriate command (which is amfconfig -D command in this case), or to
terminate the daemon using Session-ID. Session-ID is the -PID (negative PID) of
the daemon.
For example:
# kill -9 -27824
Stopping the daemon gracefully stops all the child processes spawned by the
daemon. However, using kill -9 pid to terminate a daemon is not a recommended
option to stop a daemon, and subsequently you must kill other child processes of
the daemon manually.
Core dump observed when amfconfig is run with set and reset
commands simultaneously [2871890]
When you run amfconfig -S -R on a node, a command core dump is observed,
instead of displaying the correct usage of the command. However, this core dump
has no effect on the AMF functionality on that node. You need to use the correct
command syntax instead.
Workaround: Use the correct commands:
# amfconfig -S
# amfconfig -R