The vradmin Error Messages

This section lists and describes some of the error messages that may be displayed by vradmin, if a problem occurs. It also suggests the appropriate action that needs to be taken if a problem occurs.

Unique Message Identifier (UMI)	Message	Message Definition
V-5-36-2086	Server volume access error during [assign volids] volume path: [/dev/vx/dsk/dgname/volumename]	This error may occur while performing the vradmin syncvol command if the remote volume, that is, the volume being synchronized, is not enabled or available for read and write. Action: Make sure the remote volume is available for read and write. Start the volume if it is currently stopped. If the volume is part of an RVG, make sure the RVG or the replication (i.e. RLINK) is in a certain state which allows read/write to the data volume.
V-5-52-12	vradmind server not running on this system.	Action: Start the vradmind server by running: /sbin/init.d/vras-vradmind.sh start Then, run the command again.
V-5-52-16	vradmind stopped running - Exiting.	The vradmind server got terminated during command execution. This could be due to an administrative action or due to some problem in vradmind. Action: Contact VERITAS Customer Support to look into the problem. In the mean time, restart vradmind to resume normal operations.
V-5-84-162	Terminating the collection of statistics.	This error may occur while trying to run the vrstat command on the secondary, if the vradmind server on the Primary was terminated while the vrstat command was in progress. This could be due to an administrative action or due to some problem in vradmind. Action: If you had stopped the vradmind server manually, then restart it and run the vrstat command again. If the vradmind server stopped due to some problem, contact VERITAS Customer Support.
V-5-52-242	Attribute cachesize is not allowed with the -k cache option.	When cache objects are created using the cachesize option they get deleted when snapshots are deleted. Action: Either use the -k snap option or create a cache object and use the cache attribute.
V-5-52-401	RDS rds is processing another command or a configuration change.	An attempt to run a vradmin command on RDS rds failed because another vradmin command is already running on this RDS or the RDS is undergoing a configuration change. Action: Retry running the command that you had specified after some time.
V-5-52-405	Primary vradmind server disconnected.	The vradmind server on Primary is not running. Action: Start the vradmind server on Primary.
V-5-52-418	Volumes on host host are incorrectly mapped.	One or more data volumes on the Primary do not have corresponding Secondary data volumes mapped to it. Action: Check the volume mapping between the Primary and the corresponding Secondary using vradmin printvol command. There must be one-to-one mapping between Primary and Secondary data volumes.
V-5-52-421	vradmind server on host host not responding or hostname cannot be resolved.	The vradmind server on the host host is not running, or it's running on a different port, or host is not reachable. Action: Make sure host is the correct host name and is reachable. Also make sure that vradmind is running on host and is using the same port as that on the Primary. Use vrport command to check and/or set the ports.
V-5-52-422	Primary disk group dg is not authenticated.	Before adding a new Secondary (using addsec) or overwriting data on a remote host (using syncvol), vradmin performs some authentication. This is done by checking that the /etc/vx/vras/.rdg file on the remote host contains an entry for the Primary disk group ID. The vradmin addsec or syncvol command fails if /etc/vx/vras/.rdg file on the remote host does not have such an entry. Action: Add the Primary disk group ID to the /etc/vx/vras/.rdg file on the remote host. To find disk group ID, run the vxprint -l diskgroup_name command on the Primary.
V-5-52-429	Secondary is processing a configuration change or its Primary is still reachable.	This error may occur only when performing the vradmin takeover command when the Primary is still reachable from the Secondary or when the Secondary is undergoing a configuration change. To know if the Primary is reachable or not from this Secondary, run vradmin -l printrvg rvg_name. If the output of the printrvg command shows the Pri or Sec IP not available or vradmind not running or the No Primary RVG error in the Config Errors, it indicates that the Primary is not reachable from this Secondary. Action: Check whether the Primary is reachable. If it is reachable then takeover cannot take place. In such a case, run the vradmin migrate command instead, to migrate the role of the Primary. If the Secondary is undergoing a configuration change, retry running the command after some time.
V-5-52-447	RDS has configuration error. Check information about this RDS.	Some vradmin commands will not proceed if the RDS has any configuration error(s). Action: Check the Config Errors listing for the specific RDS in the output of the vradmin -l printrvg command to identify the errors. Correct the errors and then retry running the command.
V-5-52-448	Secondary on sec_host has configuration error. Check information about this RDS.	Some vradmin commands will not proceed if the specified Secondary has any configuration error(s). (The command will still proceed if any of the other Secondary RVGs in the RDS has a configuration error). Action: Check the Config Errors listing for the specific RDS in the output of the vradmin -l printrvg command to identify the error. Correct the error and then retry running the command.
V-5-52-449	Secondary rvg_name does not have an active Primary.	The Secondary cannot determine its Primary due to one or more of the following reasons: it has some configuration error. the Primary is not reachable. it does not have any RLINK. Action: Run the vradmin -l printrvg on this Secondary to verify the cause of the problem. Correct the configuration error reported in the output of the printrvg command and then retry running the command.
V-5-52-451	Volumes vol_name on Primary and Secondary differ in size; +/- not allowed in the size specification.	When Primary and Secondary data volume vol_name differ in size then specifying a relative size using +/- is not allowed in the vradmin resizevol command. Use the vradmin printvol command to verify the size of the Primary and Secondary data volume. Action: Specify absolute size for the volume instead of a relative size in the vradmin resizevol command.
V-5-52-456	Volumes in RVG rvg_name do not have DCMs required for failback logging.	This error occurs if the vradmin takeover command is run with failback logging enabled but at least one of the data volumes in the Secondary RVG does not have DCM. Failback logging requires that all volumes must have DCMs. Action: If you want to run the takeover command with failback logging enabled, first add DCMs to all the data volumes. Then, run the takeover command. If you do not want to have failback logging enabled in the takeover command, then use it with the -N option. This requires either full synchronization or difference-based synchronization of the data volumes on the original Primary.
V-5-52-465	Primary RVG rvg_name still has one or more Secondary RVGs.	The vradmin delpri command performs the required deletion only when Primary RVG does not have any configured Secondaries. Action: Before deleting a Primary RVG, you must delete all the Secondaries. Use the vradmin delsec command to delete a Secondary.
V-5-52-467	Script script_name does not exist.	If the missing script is the onfreeze script, then it must exist on the Secondary host, where the off-host processing task is performed. Action: Put the onfreeze script on the Secondary. Make sure that the script is located in the following directory: /etc/vx/vvr/ibc_scripts/task_name Retry running the vradmin ibc command.
V-5-52-468	script_name is not executable.	Action: Change the permission for the script script_name to make it executable by root user.
V-5-52-469	Script script_1 is provided; script script_2 must also be provided.	The vradmin ibc command requires that both the quiesce and the unquiesce script, if provided, must be present together on the Primary. If you only need one script, you will still need to provide the other one so that the vradmin ibc command executes properly. Therefore, for the script that you don't need create an empty script, that is, a script which contains only the following lines: #!/sbin/sh exit 0 Action: Create script_2 on the Primary and retry running the ibc command.
V-5-52-471	host has failback flag set.	Failback logging was enabled when the Secondary on host took over as a Primary. When the failback logging is enabled you cannot use the makesec command to convert original Primary to Secondary. Action: Use the vradmin fbsync command to convert the original Primary to a Secondary.
V-5-52-478	Cannot perform incremental synchronization: RLINK rlk_name on host host not in CONNECT state.	The vradmin fbsync command will proceed only if the RLINK rlk_name on the original Primary host is attached. This error occurs when the RLINK rlk_name somehow gets paused or is not in connect state. Action: Check the RLINK rlk_name on the original Primary host. If the RLINK is paused, resume the RLINK then retry running the vradmin fbsync command. If it is already detached, then failback synchronization cannot be performed. In this case you will need to use the vradmin makesec command to convert the original Primary to Secondary of the new Primary and then synchronize the original Primary (new Secondary) with the new Primary.
V-5-52-479	Host host not reachable.	This error generally occurs in either of the following: network connection to host host is down. vradmind server on host is not running or is running on a different port. Action: Correct the network if it's a network connection problem. In the case the vradmind server is not running start vradmind on host host using /sbin/init.d/vras-vradmind.sh start OR Make sure vradmind on host runs on the same port as the local vradmind. Use vrport command to check and reset the port.
V-5-52-480	Operation requires a disk group.	The command for which the specified operation failed requires a valid disk group to be present.
V-5-52-481	Cannot perform the operation in a cross-version replication environment.	In a cross-version replication environment, operations which can result in configuration changes, like vradmin addvol, delvol and resizevol, are not allowed. Action: Upgrade VVR on all the hosts running earlier version of VVR to the same version of VVR running on the other hosts in the RDS.
V-5-52-482	Cannot perform the operation: Secondary has an earlier version of VVR.	This error may occur in a cross-version replication environment while: Performing the vradmin addsec command to add a host running an earlier version of VVR to an RDS which has at least one host running a later version of VVR. Performing the vradmin syncvol command to synchronize volumes to a host running an earlier version of VVR. Action: Upgrade VVR version on the host to the later version of VVR.
V-5-52-483	Cannot perform the operation: the cross-version feature of VVR does not support the VVR version installed on host.	The cross-version replication in VVR is only supported between two immediate major releases. Action: Upgrade the VVR version on the host host to the same VVR version as on the other hosts in the RDS.
V-5-52-489	Cannot determine local IP address: multiple IP addresses configured for the Primary RVG.	This error occurs when running the vradmin syncrvg command to multiple Secondaries for an RDS in which the local_host field of the Primary RLINKs resolve to different IP addresses. Action: If possible, make the local_host field of all the Primary RLINKs the same. If you still need to configure different interfaces for the Primary RLINKs, then run the vradmin syncrvg command to synchronize one Secondary at a time.
V-5-52-491	Cannot perform the operation: host is not a Primary (acting secondary).	The vradmin fbsync command requires that the specified host be an acting Secondary. Action: Check the vradmin printrvg output to see whether the host host is an acting Secondary.
V-5-52-492	host is an acting secondary. Complete the failback synchronization before making any configuration changes.	When an RDS has an acting Secondary, no other configuration command is allowed on this RDS except the vradmin fbsync command. Action: Run the vradmin fbsync command to convert the acting Secondary to a Secondary before making any configuration changes.
V-5-52-493	Cannot perform the operation: none of the Secondaries is in DCM logging mode.	None of the Primary RLINKs are in DCM logging mode, hence the resync operation cannot be performed. Action: none
V-5-52-494	The command is not available in earlier version of VVR.	This message results when a new command, added in a later VVR version, is run in a cross-version replication environment. Action: To be able to make use of the new commands, make sure that VVR on all hosts in the RDS is upgraded to the appropriate higher version.
V-5-52-502	Host name or IP host is not configured or available on the Primary.	This happens during addsec command, when the host name or IP address specified for the Primary host is not configured or unavailable for use. Action: Make sure the hostname or IP address specified for the Primary host is correct and reachable.
V-5-52-604	Primary RLINK rlk_name not up-to-date.	The command for which this error occurred requires the Primary RLINK rlk_name to be up-to-date. Action: Verify that Primary RLINK rlink_name is up-to-date before running the command. Use vradmin repstatus rvg command or vxrlink status rlk_name command to verify current status of the RLINK.
V-5-52-605	RLINK rlink_name in CONNECT state.	The command for which this error occurred requires that the Primary RLINK rlk_name must not be in CONNECT state. Action: Use vradmin stoprep command to stop replication.
V-5-52-609	Volume vol_name in disk group dg_name not of equal length as Primary volume.	The vradmin addsec and addvol commands require that the Secondary data volume(s) must be of the same size as the corresponding Primary data volume(s). Action: Resize either the Secondary or Primary data volume vol_name to make them of the same size. Then retry running the command. Use the vxresize command to resize a data volume.
V-5-52-610	Primary RLINK rlk_name not in CONNECT state.	The command for which this error occurred requires that the Primary RLINK rlk_name must be in CONNECT state. Action: If the RLINK is not attached, use the vradmin startrep command to start replication. If the RLINK is already attached, but not in CONNECT state, refer to the chapter Troubleshooting VVR for identifying and correcting the problem.
V-5-52-611	RLINK rlk_name is inconsistent or failed.	This error occurs when the specified Secondary data is inconsistent as a result of which the specific Secondary cannot be converted to Primary. Action: Use another Secondary which is consistent or restore a consistent data from the backup to the Secondary data volumes.
V-5-52-803	Lost connection to host host; terminating command execution.	During command execution, the host host became unreachable or vradmind server on host host stopped running. Action: Retry running the command after host host becomes reachable or after restarting vradmind on host host. This could also be due to some problem with vradmind. In such a case, contact VERITAS Customer Support.
V-5-52-2406	Cannot allocate space to grow volume to new_size blocks.	The system does not have enough free space to accommodate the requested growth in volume size. Action: Retry running the command when there is enough free space in VM configuration.
V-5-4-2411	Volumes under RVG rvg_name are not prepared for the instant snapshot.	The command requires the data volumes to be prepared before using the instant snapshot operations. The error occurred when trying to create instant snapshots of all the data volumes under an RVG, because the volumes were not prepared. Action: For the first time, before creating instant full snapshot of the volumes under an RVG, prepare the volumes using the command: vxsnap -g diskgroup prepare volume For more information, refer to the vxsnap(1M) manual page.

Messages Related to Configuration Errors

This section describes the configuration related errors that are displayed by the
vradmin -l printrvg command and the vradmin -l repstatus command. The Config Errors section appears in the output of the commands only if there are configuration errors in an RDS. The host variable in the error messages is the host name on which the error has occurred.

Note Sometimes, the Config Errors section in the printrvg command output may display multiple error messages separated by commas, for a specific host.

Message

Message Definition

host: Pri or Sec IP not available or vradmind not running

The Primary IP or the Secondary IP address is not available, or the vradmind daemon on the host is not running or is running on a different port.

Action: If it is a network problem, correct it. If vradmind server is not running on host, start it. If vradmind is running and network connection is fine, make sure that vradmind is using the same port, as vradmind on other hosts in the RDS. Use vrport command to check or set the ports.

host: disk group missing.

Host host does not have any disk group with the same name as that specified in the remote_dg attribute, of the Primary RLINK pointing to this host.

Action: Make sure the remote_dg attribute of the Primary RLINK contains the correct remote disk group name. Use vxprint -l rlink_name to see the RLINK settings. If the disk group needs to be imported on host, and it hasn't been done, then import the disk group on host.

host: RLINK missing.

Primary RVG has an RLINK to host, but host does not have corresponding rlink to this Primary RLINK.

Action: This error can occur due to the following reasons:

One or more of the following attributes in the Primary RLINK is incorrect: remote_host, remote_dg, and remote_rlink. Make sure these attributes are correct.
The corresponding Secondary RLINK on host is missing. To fix this, you can dissociate the Primary RLINK, delete it from the configuration, and then use vradmin addsec command to add host to the RDS.

host: RLINK dissociated.

Host host does have an RLINK corresponding to the Primary RLINK. However, it is not associated with the Secondary RVG.

Action: Reassociate the RLINK to the Secondary RVG on host.

host: disk-group mismatch.

The remote_dg attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the remote_dg attribute of the Primary RLINK contains the Secondary disk group name and the remote_dg attribute of the Secondary RLINK contains the Primary disk group name.

host: RLINK mismatch.

The remote_rlink attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the remote_rlink attribute of the Primary RLINK contains the Secondary RLINK name and the remote_rlink attribute of the Secondary RLINK contains the Primary RLINK name.

host: host mismatch.

The local_host and/or remote_host attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the value of the local_host attribute of the Primary RLINK is the same as that of the remote_host attribute value of the Secondary RLINK. Also make sure the value of the remote_host attribute of the Primary RLINK is the same as that of the local_host attribute of the Secondary RLINK.

host: Primary-Primary configuration.

The two Primary RVG RLINKs are pointing to each other. This situation will arise after the original Primary comes up after a Primary failover.

Action: Use vradmin fbsync or
vradmin makesec command to convert the original Primary to a Secondary.

host: multiple Primary error.

The same Secondary RVG has more than one Primary RVGs.

Action: Check both Primary RVGs to verify which one is the intended Primary then do the following:

Dissociate the Secondary RLINK pointing to the unwanted Primary RVG.
Dissociate the Primary RLINK from the unwanted Primary RVG.
Remove the disassociated RLINK(s) from the configuration.

host: two or more nodes on same host.

Two or more RVGs in the same RDS are located on the same host, host. This configuration is not supported.

Action: Keep only one RVG on that host and remove the rest.

host: platform mismatch.

Replication is allowed only between hosts that are on the same platform. This is an invalid configuration.

No Primary RVG.

Ignore this error if it displays only for a few seconds and disappears. If the error persists, then the problem may be due to the Secondary not being able to determine its Primary because it has some configuration error, the Primary is not reachable, or it does not have any RLINK.

Action: If the Secondary has an RLINK to a Primary, check to see if the Primary RVG and the corresponding Primary RLINK exist. If yes, make sure that vradmind is running on Primary and the network between Primary and Secondary is good. If everything is good, then run
vradmin -l printrvg command on the Primary to see what type of configuration error is displayed. Correct the configuration error(s).

If Primary RVG does not exist or the Secondary RVG does not have any RLINKs, then just remove the Secondary RVG.

host: Primary and Secondary have same disk-group ID.

This condition happens in the cases when the split mirrored plexes of the Primary volumes are exported without using the Disk Group split option and then imported on the Secondary with force option.

Action: Contact VERITAS Customer Support.

host: unknown

The configuration status is currently unknown.

Action:

host: stale information

The configuration status may be stale.

Action:

host: no data volume

This error can occur if one of the RVGs in the RDS does not have a data volume associated with it.

Action: Create the appropriate data volume and associate it with the RVG.

host: network-protocol mismatch

The protocol attribute of the Primary RLINK is different from that of the Secondary RLINK.

Action: Make sure the value of the protocol attribute for the Primary and Secondary RLINK is the same.

host: VVR-heartbeat-port mismatch

The local_port attribute setting for the Primary RLINK is different from that of the Secondary RLINK.

Action: Make sure the value of the local_port attribute for the Primary and Secondary RLINK is the same.

host: unsupported VVR version in cross-version replication

The cross-version replication in VVR is only supported between two immediate major releases.

Action: Upgrade the VVR version on the host host to the same VVR version as on the other hosts in the RDS.

host: no contact from Primary

This error can occur if the vradmind server on the Secondary host is unable to establish contact with the vradmind server on the Primary. This can be because the Primary RVG of this RDS cannot be found or the vradmind server is not running or is unreachable.

Action: If the vradmind server is not running, start it.

host: vxconfigd disabled

The vxconfigd daemon is currently disabled on the host on which this error occurred.

Action: Start the vxconfigd daemon.

host: volume-number mismatch

This error can occur if the number of volumes in the Primary and Secondary RVGs of the RDS are different.

Action: Use vradmin printvol to find out which RVG has the extra data volumes and then either remove them from that RVG or associate corresponding data volumes for these extra data volumes to the other RVGs in the RDS.

host: volume-size mismatch

This error can occur if the sizes of some or all of the data volumes in the Primary and Secondary RVGs of the RDS do not match.

Action: Use vradmin printvol to find out which data volumes have mismatching sizes and then use the vradmin resizevol command to correct the size mismatch error.

host: volume-name mismatch

This error can occur if some or all of the volumes in the Primary and Secondary RVGs of the RDS are not mapped correctly.

Action: Use vradmin printvol to find out which data volumes are not mapped correctly and correct the mapping error. For more information, refer to the section Mapping the Name of a Secondary Data Volume to a Differently Named Primary Data Volume.

host: Primary SRL missing

This error can occur if the Primary SRL was disassociated from the Primary RVG or is missing.

Action: If the Primary SRL is missing, create it and associate it to the Primary RVG. If it was disassociated, re-associate it back to the Primary RVG.

host: Secondary SRL missing

This error can occur if the Secondary SRL was disassociated from the Secondary RVG or is missing.

Action: If the Secondary SRL is missing, create it and associate it to the Secondary RVG. If it was disassociated, re-associate it back to the Secondary RVG.


^ Return to Top	< Previous \| Next >

Product: Volume Replicator Guides
Manual: Volume Replicator 4.1 Administrator's Guide
VERITAS Software Corporation www.veritas.com