Kernel Messages

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 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

Ignore message if seen occasionally.

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

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

Ignore message if seen occasionally.

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

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 due to error in sending (error-code)

Ignore message if seen occasionally.

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

V-5-0-0

Disconnecting rlink rlink due to loss of TCP connection

V-5-0-0

Disconnecting rlink rlink due to stream error

V-5-0-0

Disconnecting rlink rlink due to header checksum error

V-5-0-0

Disconnecting rlink rlink due to unexpected message

V-5-0-0

Disconnecting rlink rlink as Secondary data volumes are stopped

V-5-0-0

Disconnecting rlink rlink due to bad message.

V-5-0-0

Disconnecting rlink rlink due to error : error-code

V-5-0-0

Disconnecting rlink rlink remote already connected

V-5-0-0

Disconnecting rlink rlink due to pending transaction

Ignore message if seen occasionally.

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

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 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 Changing the VVR Tunables.

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 /sbin/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.

V-5-0-254

Received from unexpected port

V-5-0-255

Received unexpected message

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 /sbin/init.d/vxnm-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 same version of VVR. The only exception being when Primary is running VVR 4.0 and the Secondary is running VVR 3.5 MP2.

V-5-0-512

Replica is running an unsupported version

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-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

V-5-0-113

Disconnecting rep rlink_name to shift to DCM protection

This indicates a temporary disconnect during shifting to DCM protection.

V-5-0-149

Encountered IBC while flushing SRL to DCM - IBC dropped

The IBC residing on the SRL will be dropped when DCM protection gets triggered. You need to reissue the IBC after the DCM replay completes.

V-5-0-265

Rlink rlink connected to remote

The named RLINK has succeeded in connecting to its remote RLINK.

V-5-0-266

Rlink rlink disconnected from remote

The named RLINK has disconnected from its remote RLINK. This can have many different causes, including:

• The network is down
• The Secondary node is down
• The Primary RLINK was paused or detached
• The Secondary RLINK was detached

The RLINK will connect automatically when the situation clears.

V-5-0-270

Rlink rlink has a secondary config error

Indicates different states of the specified RLINK.

V-5-0-271

Rlink rlink has a secondary log error

V-5-0-274

Rlink rlink is in failed state

V-5-0-275

Rlink rlink is inconsistent

V-5-0-276

Rlink rlink is primary paused

V-5-0-277

Rlink rlink is secondary paused

V-5-0-278

Rlink rlink is stale and not replicating

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-467

Paused replay on RVG rvg_name

The DCM replay gets paused on Primary. This can have many different causes, including:

• The network is down
• The Secondary node is down
• The Primary RLINK was paused or detached.
• The Secondary RLINK was paused or detached.

DCM replay will start automatically when the RLINK gets connected.

V-5-0-0

Disconnecting rlink rlink due to kernel reset

This may happen due to a user initiated action, which causes the kernel objects to be recreated.

V-5-0-0

Disconnecting rlink rlink to permit transaction to proceed

The RLINK may get temporarily disconnected if a transaction is in progress. Once the transactions is completed, the RLINK will get reconnected.

V-5-0-79

cannot recover vol vol_name

During a reboot, the specified data volume was found to be disabled, and so cannot be recovered properly. The data volume may no longer be considered valid.

V-5-0-101

DCM replay complete on rlink rlink_name

DCM replay gets completed on the specified RLINK.

V-5-3-0

Resumed replay on RVG rvg_name

DCM replay gets resumed on the Primary. DCM replay will start automatically when the RLINK gets connected.