< Previous  | TOC | Index | Next  >  

V-5-0-114 

Disconnecting rlink rlink_name to permit transaction to proceed. 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support.  

V-5-0-208 

Log over 80% full for rlink rlink_name 

This indicates that SRL is almost full. 

Action: Check that the srlprot attribute is set correctly in order to avoid failing of writes, throttling of writes or overflow of SRL. 

V-5-0-267 

Rlink rlink_name disconnecting due to ack timeout on msg type message 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support.  

V-5-0-329 

Unable to connect rlink rlink_name on rvg rvg_name: Unknown error (errno) 

VVR encountered an unknown error. 

Action: Contact Veritas Customer Support. 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name: Disk group or rlink not found on remote 

The Primary RLINK indicates a Secondary disk group and RLINK combination that does not exist on the Secondary. 

Action: Ensure that the disk group and the RLINK specified by the Primary RLINK exist on the Secondary. 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name: Rlink detached on remote 

The RLINK on the Secondary node is in the detached or stale state.  

Action: Attach the RLINK and retry. 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Not ready on remote 

VVR was not able to connect the named RLINK for the reason mentioned in the message.  

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.  

If the errors persist, they may indicate a problem with the network configuration.  

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Rlink already connected on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Stream error on remote  

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Checksum error on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Unexpected command on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Out of space on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Port closing on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Too many threads on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Invalid port on remote 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name:
Send error on remote 

V-5-0-330 

Unable to connect rlink rlink_name on rvg rvg_name: 

KTLI connect failed 

V-5-0-330 

Unable to connect to rlink rlink_name on rvg rvg_name: Time out on remote 

The Secondary machine is unreachable. Will clear up when the network or the Secondary node recovers. 

V-5-0-0 

Disconnecting rlink rlink_name due to error in sending (error-code) 

VVR disconnected the named RLINK for the reason mentioned in the message.  

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.  

If the errors persist, they may indicate a problem with the network configuration.  

V-5-0-0 

Disconnecting rlink rlink_name due to loss of TCP connection 

V-5-0-0 

Disconnecting rlink rlink_name due to stream error 

V-5-0-0 

Disconnecting rlink rlink_name due to header checksum error 

V-5-0-0 

Disconnecting rlink rlink_name due to unexpected message 

V-5-0-0 

Disconnecting rlink rlink_name as Secondary data volumes are stopped 

V-5-0-0 

Disconnecting rlink rlink_name due to bad message. 

V-5-0-0 

Disconnecting rlink rlink_name due to error : error-code 

V-5-0-0 

Disconnecting rlink rlink_name remote already connected 

V-5-0-0 

Disconnecting rlink rlink_name due to pending transaction 

These errors are caused by transient network issues.  

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.  

If the errors persist, they may indicate a problem with the network configuration.  

V-5-0-0 

Received from unexpected port. Expected from port port, received from port port 

V-5-0-0 

Header checksum error  

V-5-0-0 

Received unexpected message. Expected message with opcode operation-code, received opcode operation-code 

V-5-0-0 

Data checksum error for handshake message id (message-id), data checksum computed (checksum-value) but header contains (checksum-value) 

V-5-0-0 

Data checksum error. Received message id message-id with data checksum : checksum-value expected checksum : checksum-value 

V-5-0-100 

DCM Logs not accessible, dcm logging aborted 

DCM logs are not accessible. This might have happened due to a media failure, in which case, other errors may have been logged to the console. This error is unlikely to occur, because the default is to mirror the DCM. 

V-5-0-102 

DCM volume vol name is detached 

The DCM volume became detached because a DCM log entry cannot be written. This might have happened due to a media failure, in which case other errors may have been logged to the console. Any RLINKs currently using the DCM will be detached and marked STALE. This error is unlikely to occur, because the default is to mirror the DCM. 

V-5-0-107 

Detaching rlink rlink_name due to I/O error on remote SRL during recovery 

When the original Primary comes up after it has been taken over, an I/O error has occurred on the original Primary's SRL while performing recovery. The new Primary has detached the RLINK that connects to the failed Primary because now there is no way to make the old Primary consistent and convert it to a Secondary of the new Primary. 

Action: Fix the I/O error on the SRL, convert the original Primary into a Secondary of the new Primary, and perform a complete synchronization. 

V-5-0-280 

Rlink rlink_name stale due to log overflow 

The specified RLINK has fallen too far behind, and overflowed the SRL. It will be detached and marked stale. The Secondary will require a complete resynchronization. This can be avoided in the future by using the RLINK's srlprot attribute. 

V-5-0-287 

rvg rvg_name, SRL srl: Inconsistent log - detaching all rlinks 

SRL contains corrupt data, and so is not usable. All RLINKs are detached and marked STALE. All secondaries will require a complete resynchronization. This error probably indicates a bug in VVR.
Action: Contact Veritas Customer Support. 

V-5-0-288 

Secondary log overflowed. Pausing rlink rlink_name 

Specified Secondary RLINK gets paused. 

Action: Associate the SRL of the same size as that of Primary to the Secondary RVG and resume the RLINK.  

V-5-0-293 

SRL for RVG rvg_name contains old version of SRL header 

Specified SRL associated with the RVG is of older version. You may not have followed the proper procedure for upgrading VVR as described in Release Notes.  

Action: Refer to the latest Release Notes for the correct upgrading procedures. 

V-5-1-435 

Cannot allocate space for 20480 block volume or not enough disks for creating dcm with 2 mirrors 

By default, the DCM is mirrored; therefore, it requires space on two disks. An attempt to associate a DCM to a new data volume or an existing data volume failed because sufficient space is not available.  

Action: We recommend that you provide the required space. Alternatively, you can specify nlog=1 in the vxassist make or vxassist addlog command. 

V-5-0-18 

startdaemon_deferred: Could not create volkmsgd 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support.  

V-5-0-44 

Cannot alloc bind structure (errno) 

V-5-0-45 

Cannot alloc bind structure for listen server (errno) 

V-5-0-46 

Cannot alloc connection indication call structure (errno) 

V-5-0-47 

Cannot alloc ktli header (errno) 

V-5-0-40 

Cannot bind the acceptor (errno) 

V-5-0-49 

Cannot connect rlink rlink_name due to protocol mismatch: remote rlink is using protocol_name protocol, local rlink is using protocol_name protocol 

VVR is not able to communicate with the remote host because the selected protocol differs between local and remote hosts. 

Action: Verify that the Primary and Secondary RLINKs are set to use the same network communication protocol.See Setting the network transport protocol. 

V-5-0-50 

Cannot connect to host ip address port port_number (errno) 

You may see this message when vxnetd has not been run on the remote host. 

Action: Run vxnetd by issuing the command /etc/init.d/vxnm-vxnetd. If the message persists, contact Veritas Customer Support. 

V-5-0-51 

Cannot connect to remote due to header format mismatch or checksum error 

Action: Contact Veritas Customer Support. 

V-5-0-54 

Cannot find any free port to bind 

All the ports in the specified list have been utilized. 

Action: Add the ports to be used for replication using the vrport command. 

V-5-0-75 

Cannot open ktli (errno) 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support. 

V-5-0-76 

Cannot open ktli for listen server (errno) 

V-5-0-77 

Cannot open the acceptor port (errno) 

V-5-0-78 

Cannot open the server port (errno) 

V-5-0-80 

Cannot send out a message 

V-5-0-82 

Cannot spawn netiod thread; invalid transport selected 

V-5-0-84 

Cannot spawn server thread 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support. 

V-5-0-611 

Could not send heartbeat id to node node 

V-5-0-174 

header checksum error 

V-5-0-175 

Heartbeat unacknowledged from node ip-addr for t seconds 

V-5-0-206 

listen server port in use (errno) 

Port assigned to VVR is in use by another application.  

Action: Change the assigned port using the vrport command.  

V-5-0-219 

nmcom client cannot bind ktli port (errno) 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support. 

V-5-0-220 

nmcom client cannot open ktli port (errno) 

V-5-0-236 

Number of ports available (total-port) is less than the number of rlinks (numreplicas) in the system 

The specified number of ports are less than total number of RLINKs in the system. Some of the RLINKs will be disconnected.  

Action: For all RLINKs that are to take part in replication, configure at least n number of ports using the vrport command, where n is >=num_of_rlink in the system. 

V-5-0-246 

port port-id is in use by another application 

Port assigned to VVR is in use by another application.  

Action: Change the assigned port using the vrport command.  

V-5-0-247 

port in use (port id) 

Port assigned to VVR is in use by another application.  

Action: Change the assigned port using the vrport command.  

V-5-0-253 

Received 100 duplicate packets. Check network configuration 

Indicates a possible network misconfiguration, such as multiple NICs with the same address.  

Action: Check network configuration and make sure that the IP assigned to the RLINK is unique on the system. 

V-5-0-376 

VVR listener thread exiting 

If VVR is using the TCP protocol, a thread listens for incoming RLINK connections from remote hosts. When this thread encounters a fatal error, it exits with this message. 

Action: Run vxnetd by issuing the command /etc/init.d/vxvm-vxnetd. If the message persists, contact Veritas Customer Support.  

V-5-0-0 

2a: Received invalid message block in TCP stream 

Ignore message if seen occasionally.  

Action: If the message persists, contact Veritas Customer Support. 

V-5-0-0 

2b: Received invalid message block in TCP stream 

V-5-0-0 

2c: Received invalid message block in TCP stream 

V-5-0-0 

2d: Received invalid message block in TCP stream 

V-5-0-0 

Could not save message block, TCP stream error 

V-5-3-0 

Received invalid message block in TCP stream 

V-5-0-29 

Configuration error on rvg rvg_name pausing rlink rlink_name 

Indicates configuration error. 

Action: Clear the mentioned error. 

V-5-0-30 

Cannot find matching volume for volume pri_datavol on primary 

V-5-0-31 

Name on Secondary datavol_name does not match name on primary pri_datavol 

V-5-0-32 

Size of volume pri_datavol on primary (vol_size) does not match size on Secondary (sec_vol_sz) 

V-5-0-511 

Replica has an unsupported message format 

Remote host is running older version of VVR. The RLINKs will go into the STALE state. 

Action: For replication to take place, all the hosts in the VVR configuration must be running the same version of VVR. The exception is during certain upgrade scenarios that enable you to upgrade the Primary and the Secondary at different times. This type of upgrade is usually supported only between the current release and the immediately prior release. 

V-5-0-512 

Replica is running an unsupported version 

V-5-0-858 

Received from unexpected port 

These errors are caused by transient network issues. VVR handles these errors so they can be ignored if seen occasionally. If the errors persist, it may indicate a problem with the network configuration.  

V-5-0-859 

Received unexpected message 

V-5-1-10128 

Operation requires transaction 

Indicates that another configuration change is in progress. 

Action: Issue the command again. 

V-5-0-167 

Failing writes on rvg rvg_name. Remote is now a primary rvg. 

When the original Primary comes up after it has been taken over and the application on the original Primary tries to perform writes, the writes will fail because this RVG is no longer the Primary. 

Action: Stop the application on the original Primary. 

V-5-0-232 

Node nodename is logowner for Rvg rvg_name 

The specified node has become the logowner for the specified RVG.  

Action: No action required. 

V-5-0-350  

vol_rv_ioctl: rvg rvg_name already has owner 

An attempt to set the logowner of an RVG failed because the RVG already has a logowner.  

Action: Clear the logowner on the node where it currently resides first. 

V-5-0- 439 

vol_rv_send_request_start: unknown type 

An illegal call was made to send a request to the cluster master.  

Action: Contact Veritas Customer Support. 

V-5-0-352  

vol_rv_wrship_start: Corrupted memory list 

Memory corruption occurred during a remote write.  

Action: Contact Veritas Customer Support. 

V-5-0-79 

cannot recover vol vol_name 

A memory allocation failure occurred during a cluster reconfiguration. 

Action: Contact Veritas Customer Support. 

V-5-0-1008 

Cannot connect rlink due to protocol mismatch with 

For STORAGE rlink the protcol field of the other rlink is not set to STORAGE, hence rlink can not be connected. 

Action: Set the protocol of both the rlink as STORAGE. 

V-5-0-1009 

Cannot connect rlink to remote rlink since secondary rvg %s is not ready. 

The Secondary rvg has stopped volumes, hence cannot connect the rlink. 

Action: Start the volumes in the secondary rvg and then connect the rlink. 

V-5-0-0 

Size of primary SRL ("VOFFDSTR") does not match size wth secondary SRL" 

Indicates that the size of the SRL on the bunker secondary does not match the size of the SRL on the Primary.  

Action: Make the bunker Secondary SRL size same as primary SRL size and then reconnect the Primary to bunker rlink. 

V-5-0-0 

Disconnecting rlink %s to reconnect from new position, 

When a Secondary switches connection from Primary rvg to bunker Primary or vice versa, then after the first connect it disconnects the rlink to reconnect from new position. 

Action: No action is required. It will reconnect in the next try from new position. If it happens frequently then contact Symantec consultant. 

V-5-0-59 

cannot log error for rvg rvg_name 

The messages in this set mean that VVR attempted to log the specified event in the kernel log; however, the attempt failed. The attempted write to the log failed either because the kernel log is full or because of a write error to the drive.  

Action: If error messages were seen from the disk driver, it is likely that the last copy of the log failed due to a disk error. The failed drive in the disk group must be replaced and the log will then be re-initialized on the new drive.  

If there were no error messages from the disk driver, contact Veritas Customer Support.  

V-5-0-62 

cannot log atomic commit changes for rvg rvg_name 

V-5-0-63 

cannot log changes for rvg rvg_name 

V-5-0-65 

cannot log datavol error for rvg rvg_name 

V-5-0-68  

cannot log error during failback for rvg rvg_name 

V-5-0-70  

cannot log srl error for rvg rvg_name 

V-5-0-71 

cannot log srl error for rvg rvg_name 

V-5-0-72 

cannot log unfreeze error for rvg rvg_name 

V-5-0-73 

cannot log update commit state for rvg rvg_name 

V-5-0-95 

could not log config error for rvg rvg_name 

V-5-0-160 

failed to flush log on detach of rvg rvg_name 

The messages in this set mean that VVR logged the event(s) specified in the kernel log but was unable to flush the log.  

Action: Contact Veritas Customer Support. 

V-5-0-161 

failed to flush log on errors on rvg rvg_name 

V-5-0-165 

Failed to log the detach of the DCM volume vol name 

The messages in this set mean that VVR attempted to log the specified event in the kernel log; however, the attempt failed. The attempted write to the log failed either because the kernel log is full or because of a write error to the drive.  

Action: If error messages were seen from the disk driver, it is likely that the last copy of the log failed due to a disk error. The failed drive in the disk group must be replaced and the log will then be re-initialized on the new drive.  

If there were no error messages from the disk driver, contact Veritas Customer Support. 

V-5-0-348  

vol_rp_set_state_atomic_commit_done:cannot log atomic commit state for rvg rvg_name 

V-5-0-349 

vol_rp_set_state_atomic_commit_start: cannot log atomic commit state for rvg rvg_names 

 ^ Return to Top

< Previous  | TOC | Index | Next  >