Messages similar to the following will be observed in the /var/VRTScps/log/cpsadm_A.log file on the VCS cluster at the time the core is generated:
CPS ERROR V-97-1400-798 Failed to connect to host
CPS ERROR V-97-1400-798 Failed to connect to host
CPS ERROR V-97-1400-798 Failed to connect to host
This has been identified as incident 4152882 which occurs when rolling-over the /var/VRTScps/log/vxcpserv_[A|B|C].log files. Instead of referencing the new log file, an invalid pointer still references the previous log file causing the vxcpserv process to receive a SIGABRT signal.
Stopping and restarting the VCS cluster or killing and restarting the vxcpserv process on the affected CP server will workaround the issue. The CP server code has also been updated and hofixes are available for VRTScps 8.0.0 and VRTScps 8.0.2.
Please contact Veritas Technical Support to obtain the appropriate hotfix.
A hotfix is now available for this issue in the current version(s) of the product(s) mentioned, please contact Veritas Technical Support to obtain the hotfix.
#8 0x00007f75209f67e2 in fwrite () from /lib64/libc.so.6
#9 0x000000000056668c in Log::write_log (this=0x2d39be8, timet=1707722066, sev=4, whop=0x602eb1 "do_list_membership",
filep=0x601f02 "server_actions.C", line=1375, flags=32768, cat=1400, id=904, msgp=0x0, msg_structp=0x7f74f4008cf8) at Log.C:2065
#10 0x0000000000565093 in Log::write_app (this=0x2d39be8, sev=SEV_INFO, whop=0x602eb1 "do_list_membership", filep=0x601f02 "server_actions.C",
line=1375, flags=32768, cat=1400, id=904, ipm_msg_in=0x7f74f4008cf8) at Log.C:1470
#11 0x0000000000461ec4 in do_list_membership (clus_uuid="{<uuid info>}", clus_name="", recv_nodeid=0, out_resp=...,
list_inactive=false) at server_actions.C:1373
#12 0x000000000045411a in handle_requested_action (uuid_from_client_cert="{<uuid info>}", is_client_local=false, req=...)
at server_https.C:332
#13 0x0000000000454e8a in CPSHTTPSRequestHandler::handleRequest (this=0x7f74f4029a08, req=..., resp=...) at server_https.C:428