This appendix lists error messages and warnings that can appear as output of the ha_cfgverify command. This command aids in verifying the validity of the configuration file ha.conf. ha_cfgverify can be run manually (see the section “Creating a Configuration File” in Chapter 4) and is run automatically each time IRIS FailSafe is started on a node and when a node moves from standby state to another state.
 | Note: ha_cfgverify generates warnings when a possible error exists, but it is unable to determine for sure. You must check each warning manually. A warning could indicate invalid IRIS FailSafe configuration. |
The error messages are listed in alphabetical order.
ha_cfgverify: action-timer section must be present for application-class <name>
Every application class must have an action-timer section where different time intervals for monitoring the application are specified. The name of this section must be same as the application class name.
ha_cfgverify: Agent <agent_name> is not valid in <app_class> application class
The monitoring agent agent_name specified in the application class app_class does not exist or does not have execute permissions.
ha_cfgverify: all nodes must be present in the server nodes entry for main application class
Both nodes need server-node entries for main application class.
ha_cfgverify: <name> application class does not have a server node
All application class entries must have at least one server-node entry.
ha_cfgverify: <application> application class: start-monitor-time must be greater than the long-timeout value
For application class section labelled application, start-monitor-time must be greater than the long-timeout value.
ha_cfgverify: backup-node entry in filesystem <name> must be present
The filesystem section must have a server-node and a backup-node.
ha_cfgverify: backup-node entry <node name> in filesystem <name> is not a valid node
The backup node does not have a node section in the configuration file.
ha_cfgverify: backup-node entry in volume <node_name> is not a valid node
The backup node name must match one of the node block labels.
ha_cfgverify: broadcast address <address> is not valid for node <node_name>
The broadcast address is either not in Internet standard “.” notation or the name lookup of the broadcast address failed.
ha_cfgverify: broadcast address for interface block <block_name> is not present for node <node_name>
The broadcast address must be specified for the interface block block_name.
ha_cfgverify: broadcast address for primary-ip not present for node <node name> ha_cfgverify: broadcast address for private-ip not present for node <node name> ha_cfgverify: broadcast address for secondary-ip not present for node <node name>
The broadcast address for primary-ip, secondary-ip, and private-ip must be specified in the ha.conf file.
ha_cfgverify: broadcast-addr entry <addr> is not valid in interface-pair <ipair>
The broadcast address addr specified in interface pair section labelled ipair is not a valid internet address or the name lookup of the broadcast address failed.
ha_cfgverify: broadcast-addr entry in interface-pair <ipair> must be present
This entry specifies broadcast address for the list of IP addresses in interface-pair.
ha_cfgverify: Check if rpc.statd has been started with -h option
The rpc.statd process must be started with -h option. In IRIX 6.2, check if the /etc/config/statd.options file has -h option. In IRIX 5.3, check if the latest networking rollup patch has been installed.
ha_cfgverify: Configuration file <filename> opening/parsing error
There was an error in opening or parsing the configuration file. Check the previous error message from ha_cfgverify for explanation.
ha_cfgverify: device name entry in volume <vol_name> must be present
All volume sections must have device-name entries.
ha_cfgverify: Failed to find hostname
The file /etc/sys_id must have the hostname. The hostname must be configured using hostname command hostname -s <host name>.
ha_cfgverify: filesystem type entry in filesystem <name> must be present
All filesystem sections must have mount point, filesystem type, device name, and mount mode entries.
ha_cfgverify: <type> filesystem type is not valid in filesystem <name>
The filesystem must be XFS.
ha_cfgverify: giveaway function <file name> is not valid in <name> application class ha_cfgverify: giveback function <file name> is not valid in <name> application class
Either the filename is not present in the node or it does not have execute permission.
ha_cfgverify: heartbeat ip address not present for node <node name>
The heartbeat IP address for the node must be specified. It is usually the private IP address.
ha_cfgverify: heartbeat ip address <ip address> is not valid for the node <node name>
The heartbeat IP address must be the private IP address. It must be same for all the nodes, that is, heartbeat IP address for all nodes must be the respective private IP addresses.
ha_cfgverify: heartbeat lost count for the node <node name> must be specified
The heartbeat lost count must be specified for each node.
ha_cfgverify: heartbeat probe time for the node <node name> must be specified
The heartbeat probe time (in seconds) must be specified for each node.
ha_cfgverify: heartbeat timeout for the node <node name> must be specified
The heartbeat timeout (in seconds) must be specified for each node.
ha_cfgverify: heartbeat private ip name is not present for node <node_name>
The heartbeat IP address for the node must be specified.
ha_cfgverify: heartbeat public ip name <public_ip> is not present for node <node_name>
If the private network between the nodes fail, the hb-public-ipname is used for heartbeat. This parameter must be set to a fixed IP address.
ha_cfgverify: httpd-script <script> is not valid in <app> application
The httpd-script value script specified for the webserver application is not present in the node or it does not have execute permission. This script is used to start and stop the Web server.
ha_cfgverify: hostname <hostname> must be one of the node labels
The node label of the node section must be the node's hostname. The ha_cfgverify command must be run in one of the nodes of the cluster.
ha_cfgverify: interface block <block_name> does not have MAC-address entry
The re-mac'ing option has been set to true but the MAC address has not been specified in the interface block.
ha_cfgverify: interface block name <name> must be unique for the configuration file
The name of the interface block in the node section must be unique for the configuration file.
ha_cfgverify: interface name <ifname> for node <node_name> must be configured in /etc/config/netif.options file
The interface name ifname must be assigned an IP address in the /etc/config/netif.options file. This interface must be configured when the node boots up.
ha_cfgverify: interface name for primary-ip not present for node <node name> ha_cfgverify: interface name for private-ip not present for node <node name> ha_cfgverify: interface name for secondary-ip not present for node <node name>
The interface name for primary-ip, secondary-ip, and private-ip must be specified.
ha_cfgverify: interface name <name> is not valid for node <node_name>
The interface name is not valid in the node. Check the interface name using the netstat command.
ha_cfgverify: <agent_name> : interface-agent section must have start-monitor-time entry ha_cfgverify: <agent_name> : interface-agent section must have interface-probe-interval entry ha_cfgverify: <agent_name> : interface-agent section must have interface-probe-timeout entry ha_cfgverify: <agent_name> : interface-agent section must have remote-send-probe-interval entry ha_cfgverify: <agent_name> : interface-agent section must have remote-send-timeout entry
Interface agent section must have all the following entries: start-monitor-time, interface-probe-interval, interface-probe-timeout, remote-send-probe-interval, and remote-send-timeout.
ha_cfgverify: interface-agent section must have interface-probe-interval entry ha_cfgverify: interface-agent section must have interface-probe-timeout entry ha_cfgverify: interface-agent section must have remote-send-probe-interval entry ha_cfgverify: interface-agent section must have start-monitor-time entry,
The interface-agent section must have interface-probe-interval, interface-probe-timeout, remote-send-probe-interval, start-monitor-time entries.
ha_cfgverify: internal section: version-major value is invalid (must be <num>)
The value of version-major parameter in the internal section must be the number shown.
ha_cfgverify: internal section: version-minor value is invalid (must be <num>)
The value of version-minor parameter in the internal section must be the number shown.
ha_cfgverify: ip address <value> is not present in the hosts database ha_cfgverify: ip alias <value> is not present in the hosts database ha_cfgverify: heartbeat private ip name <value> is not present in the hosts database ha_cfgverify: node name <node_name> is not present in the hosts database ha_cfgverify: node name <node_name> is not present in the hosts database
The ip-address, ip-alias or node name could not be found in the hosts database. The host-name or address should be found either in the /etc/hosts file, from NIS, or named server.
ha_cfgverify: ip address for interface block <block_name> is not present for node <node_name>
The interface block of the node section must have an entry for ip-address that is a fixed IP address. This IP address is configured using /etc/config/netif.options.
ha_cfgverify: ip address for primary-ip not present for node <node name> ha_cfgverify: ip address for private-ip not present for node <node name> ha_cfgverify: ip address for secondary-ip not present for node <node name>
The IP address for the primary-ip, secondary-ip, and private-ip must be specified in the ha.conf file.
ha_cfgverify: ip-aliases field must be present for nfs server node <server_node>
The server-node section of application-class nfs must contain the ip-aliases parameter. NFS clients use one of the ip-aliases specified here for mounting filesystems from this server.
ha_cfgverify: kill function <file name> is not valid in <name> application class
Either the filename is not present in the node or it does not have execute permission.
ha_cfgverify: local monitor <file name> is not valid in <name> application class
Either the filename is not present in the node or it does not have execute permission.
ha_cfgverify: local monitor probe time not specified for <name> application class ha_cfgverify: local monitor timeout not specified for <name> application class
If the application has a local monitor, local monitor timeout and probe time in seconds must be specified.
ha_cfgverify: long-timeout value missing
The long-timeout value must be specified in the internal section of the ha.conf file.
ha_cfgverify: mac address for primary-ip not present for node <node_name> ha_cfgverify: mac address for private-ip not present for node <node_name> ha_cfgverify: mac address for secondary-ip not present for node <node_name>
If re-mac'ing of interfaces is needed (the re-mac variable in the system-configuration section of the configuration file is set to true), the MAC address of primary-ip, private-ip, and secondary-ip for the node node_name must be specified.
ha_cfgverify: MAC-address %s is not valid for node <node_name>
MAC address specified in the interface section of node_name does not match the physical address of network interface. The MAC address must be obtained using macconfig command.
ha_cfgverify: main application class does not have all server nodes
Either the main application class does not have server-node entries, or there is no main application class entry in application class section.
ha_cfgverify: main application class must have giveaway function ha_cfgverify: main application class must have giveback function ha_cfgverify: main application class must have kill function ha_cfgverify: main application class must have local monitor function ha_cfgverify: main application class must have takeback function ha_cfgverify: main application class must have takeover function
The main application class must have giveback, takeback, takeover, giveaway, kill, and local monitor scripts.
ha_cfgverify: main application class must have start monitor time
The start monitor time entry for main application class must be specified in seconds.
ha_cfgverify: mount mode entry in filesystem <name> must be present ha_cfgverify: mount point entry in filesystem <name> must be present
All filesystem sections must have mount point, filesystem type, volume, and mount mode entries.
ha_cfgverify: mount point entry <name> in filesystem <name> is present in /etc/fstab file
The mount point must not be present in the /etc/fstab file. If it is present in the /etc/fstab file, the “noauto” mount option must be specified. The IRIS FailSafe software mounts the directory.
ha_cfgverify: name of the interface must be present for the interface block <name> ha_cfgverify: netmask for interface block <name> is not present for node <node_name>
The interface block in the node section must specify the interface name and netmask.
ha_cfgverify: netmask <mask> is not valid for node <node_name> ha_cfgverify: netmask entry <mask> is not valid in interface-pair <pair_name>
The netmask entry mask must be a valid mask for an internet address.
ha_cfgverify: netmask entry in interface-pair <name> must be present
Every interface-pair block must have a netmask entry. It is missing from the interface-pair block name.
ha_cfgverify: netmask for primary-ip not present for node <node name> ha_cfgverify: netmask for private-ip not present for node <node name> ha_cfgverify: netmask for secondary-ip not present for node <node name>
The netmask for the primary-ip, secondary-ip, and private-ip must be specified in the ha.conf file.
ha_cfgverify: nfs is not configured in the system
Either the NFS software has not been configured in the system, or the nfs configuration flag is not chkconfig'd on.
ha_cfgverify: NFS lockd/statd FailSafe compatible patch is not installed in the system
The NFS lockd/statd patch required by IRIS FailSafe is not installed.
ha_cfgverify: nfs <name> section: export point entry is invalid
The export point entry must be a subdirectory of the mount-point entry of the filesystem.
ha_cfgverify: nfs <name> section: export point entry <dir> or its subdirectory is present in /etc/exports file
The export point entry must not be present in the /etc/exports file. It is exported by the IRIS FailSafe software.
ha_cfgverify: nfs <name> section must have the export info entry ha_cfgverify: nfs <name> section must have the export point entry ha_cfgverify: nfs <name> section must have the filesystem entry
All NFS sections must have filesystem, export-point, and export-info entries.
ha_cfgverify: nfs <name>: the filesystem entry <filesystem name> is invalid
The filesystem entry does not match the filesystem section labels.
ha_cfgverify: no application class section
The ha.conf file does not have an application class section. The application class has an entry for main application and optional entries for NFS and Web server applications.
ha_cfgverify: no interface section for the node <node_name>
Every node block must have an interface section. Interface section is missing for the node block labelled node_name.
ha_cfgverify: no interface-pair section
The configuration file is missing the interface-pair section. The name must be unique in the IRIS FailSafe configuration file. There should be one interface-pair block for each combination of network interfaces.
ha_cfgverify: No ip-aliases entry in interface-pair <name>
The interface-pair section name does not contain the parameter ip-aliases. It contains the list of ip-addresses that are failed over.
ha_cfgverify: No nfs section present in the file
There is an NFS application class entry but there is no NFS section.
ha_cfgverify: No node sections in the configuration file
The ha.conf file must have two node sections. The name of the node block must be the hostname of the node.
ha_cfgverify: No webserver section present in the file
The configuration file has a Web server application class entry, but there is no Web server section.
ha_cfgverify: node name <node_name> is not present in the hosts database
The node_name must be present in the /etc/hosts file, or its IP address can be obtained from the named server.
ha_cfgverify: <node_name> section: hb_use_public entry must be set to “no” in hot standby configuration.
In an active/backup configuration (each node in the cluster has only two network interfaces), the hb_use_public entry must be set to no.
ha_cfgverify: primary-interface entry <p_interface> in interface-pair <pair_name> is invalid ha_cfgverify: secondary-interface entry <p_interface> in interface-pair <pair_name> is invalid
The value assigned to primary-interface and secondary-interface parameter must match one of the interface block labels of the node block.
ha_cfgverify: primary-interface entry in interface-pair <pair_name> must be present ha_cfgverify: secondary-interface entry in interface-pair <pair_name> be present
Every interface-pair block must have entries for primary-interface and secondary-interface. The interface-pair labelled pair_name is missing the indicated entry.
ha_cfgverify: primary-interface entry in interface-pair <pair_name> require both ip-aliasing and re-mac'ing. Re-macing requires a dedicated secondary interface.
On a failure, IRIS FailSafe moves the MAC address of an interface along with the IP addresses. But, MAC addresses can be moved only between one set of primary and secondary interfaces. Check if the primary-interface entry has been specified in multiple interface-pair blocks.
ha_cfgverify: primary-ip and secondary-ip information must be present for the node <node_name>
The primary-ip and secondary-ip information is needed for all nodes in a dual-active configuration. In an active/backup configuration, primary-ip information is needed for one node and secondary-ip information is needed for the other node.
ha_cfgverify: primary-ip broadcast address <address> is not valid for node <node name>
The broadcast address is not a valid internet address.
ha_cfgverify: primary-ip information must be present for the node <node_name>
The primary-ip and secondary-ip information is needed for all nodes in a dual-active configuration. In an active/backup configuration, primary-ip information is needed for one node and secondary-ip information is needed for the other node.
ha_cfgverify: primary-ip interface name <interf. name> for node <node name> is present in /etc/config/netif.options file
The primary-ip interface must not be configured using the netif.options file. The IRIS FailSafe software configures the interface.
ha_cfgverify: primary-ip interface name <interface name> is not valid for node <node name>
The interface name is not valid in the node. Check the interface name using the netstat command.
ha_cfgverify: primary-ip mac address <mac_address> is not valid for node <node_name>
The MAC address/physical address specified for primary-ip and secondary-ip is incorrect. Use macconfig(1M) to find the correct physical address.
ha_cfgverify: primary-ip netmask <net mask> is not valid for node <node name>
The netmask for the primary-ip, secondary-ip, or private-ip is not a valid internet netmask.
ha_cfgverify: private-ip broadcast address <address> is not valid for node <node name>
The broadcast address is not a valid internet address.
ha_cfgverify: private-ip interface name <interface name> for node <node name> must be present in /etc/config/netif.options file
The private-ip must be specified in the netif.options file.
ha_cfgverify: private-ip interface name <interface name> is not valid for node <node name>
The interface name is not valid in the node. Check the interface name using the netstat command.
ha_cfgverify: private-ip name <ip_name> for node <node_name> must match the hostname
The private-ip name in the node section of the configuration file must be same as the hostname of that node.
ha_cfgverify: private-ip netmask <net mask> is not valid for node <node name>
The netmask for the primary-ip, secondary-ip, or private-ip is not a valid internet netmask.
ha_cfgverify: raw device name entry in filesystem <fs> must be present ha_cfgverify: mount point entry in filesystem <fs> must be present ha_cfgverify: filesystem type entry in filesystem <fs> must be present ha_cfgverify: volume-name entry in filesystem <fs> must be present ha_cfgverify: server-node entry in filesystem <fs> must be present ha_cfgverify: backup-node entry in filesystem <fs> must be present ha_cfgverify: device name entry in filesystem <fs> must be present ha_cfgverify: mount mode entry in filesystem <fs> must be present
All filesystem sections must have raw device, mount point, filesystem type, volume name, server node, backup node, device name, and mount mode entry in them.
ha_cfgverify: raw device name entry in filesystem <fs> is invalid ha_cfgverify: Warning: device name entry in filesystem <fs> is invalid
The device names do not exist or they are not special device names in the node.
ha_cfgverify: remote monitor probe time not specified for <name> application class ha_cfgverify: remote monitor timeout not specified for <name> application class
If the application has a remote monitor, the remote monitor timeout and probe time (in seconds) must be specified.
ha_cfgverify: secondary-ip broadcast address <address> is not valid for node <node name>
The broadcast address is not a valid internet address.
ha_cfgverify: secondary-ip information must be present for the node <node_name>
The primary-ip and secondary-ip information is needed for all nodes in a dual-active configuration. In an active/backup configuration, primary-ip information is needed for one node and secondary-ip information is needed for the other node.
ha_cfgverify: secondary-ip interface name <interface name> for node <node name> must be present in /etc/config/netif.options file
The secondary-ip must be specified in the netif.options file.
ha_cfgverify: secondary-ip interface name <interface name> is not valid for node <node name>
The interface name is not valid in the node. Check the interface name using the netstat command.
ha_cfgverify: secondary-ip mac address <mac_address> is not valid for node <node_name>
The MAC address/physical address specified for primary-ip and secondary-ip is incorrect. Use macconfig(1M) command to find the correct physical address.
ha_cfgverify: secondary-ip netmask <net mask> is not valid for node <node name>
The netmask for the primary-ip, secondary-ip, or private-ip is not a valid internet netmask.
ha_cfgverify: <name> section: hb_use_public entry must be set to “no” in active/standby configuration
In active/backup configuration hb-use-public entry must be set to no.
ha_cfgverify: server-node entry <node name> in filesystem <name> is not a valid node
The server-node does not have a node section.
ha_cfgverify: server-node entry in volume <vol_name> is must be present ha_cfgverify: backup-node entry in volume <vol_name> must be present ha_cfgverify: device name entry in volume <vol_name> must be present
The volume block must have server-node, backup-node, device name entry. This entry is missing for volume block labelled vol_name.
ha_cfgverify: server-node entry <node_name> in volume <vol_name> is not a valid node ha_cfgverify: backup-node entry <node_name> in volume <vol_name> is not a valid node
Server-node and backup-node value must match one of the node labels.
ha_cfgverify: server-node entry <node_name> in filesystem <fs> is not a valid node ha_cfgverify: backup-node entry <node_name> in filesystem <fs> is not a valid node ha_cfgverify: server node <node_name> is not a valid node in main application class
The node_name must match one of the node labels.
ha_cfgverify: server node <node name> is not a valid node in <name> application class
The server-node in the application class does not have a node section.
ha_cfgverify: short-timeout value must be smaller than long-timeout value
The long-timeout value in the internal section must be larger than the short-timeout value.
ha_cfgverify: Some xlv patches have not been installed in the system
All XLV patches must be installed on the node. Check the release notes for the latest XLV patch numbers.
ha_cfgverify: specify a reset-host, or a reset-tty for node <node_name>
reset-tty is the device filename of the serial link that is connected to remote power control unit.
ha_cfgverify: start-monitor-time (action-timer block) must be present for application-class <app_class>
The action-timer block of application-class app_class does not contain the entry for start-monitor-time.
ha_cfgverify: statmon-dir <dir_name> must be called “statmon”
The name of the statmon directory must be statmon.
ha_cfgverify: statmon-dir must be present for nfs server node <node_name>
The statmon-dir parameter in the application classes block of the configuration file must be specified for the NFS primary node node_name.
ha_cfgverify: takeback function <file name> is not valid in <name> application class ha_cfgverify: takeover function <file name> is not valid in <name> application class
Either the filename is not present in the node or it does not have execute permission.
ha_cfgverify: The /etc/config/routed.options must have -q option
The routed daemon must be started with the -q option. The routed options file /etc/config/routed.options must have the -q option.
ha_cfgverify: The ip-alias <value> in interface-pair <name> is a fixed ip address.
The ip-alias value in the interface-pair name cannot be a fixed IP address. It must be an IP alias that can be failed over.
ha_cfgverify: Too many application classes: <num>
The IRIS FailSafe software supports up to 16 application class entries.
ha_cfgverify: Too many filesystems <n>
The number of filesystems n specified in the configuration file is greater than maximum filesystems allowed.
ha_cfgverify: Too many node entries: <num>. Only 2 two nodes are permitted
The configuration file ha.conf can have only two node sections. The IRIS FailSafe software permits only clusters of two nodes.
ha_cfgverify: Too many volumes <n>
The number of volumes specified in the configuration file is greater than maximum volumes allowed.
ha_cfgverify: /usr/etc/ha_statd command missing
The command /usr/etc/ha_statd is missing on the node.
ha_cfgverify: volume-name entry <vol_name> in filesystem <fs> is not a valid volume.
The volume-name value must match one of the volume block labels.
ha_cfgverify: Warning: check if xlv license has been installed
If XLV plexing is being used, a plexing license must be installed in the /etc/nodelock file.
ha_cfgverify: Warning: device name entry in filesystem <name> is invalid
Either the filename is not present in the node or it does not have execute permission.
ha_cfgverify: Warning: mount point entry <name> in filesystem <name> is not a valid directory
The mount point must be a valid directory.
ha_cfgverify: Warning: netscape is not configured in the system
Either the Web server software has not been configured in the system, or the ns_httpd configuration flag is not chkconfig'd on.
ha_cfgverify : Warning NFS lockd/statd patch for Failsafe (1032) is not installed in the system
The NFS lockd/statd patch (see the release notes for the patch number) is necessary for failing over NFS locks for the NFS service.
ha_cfgverify: Warning: no filesystems found in the configuration file
The ha.conf file does not have a filesystem section. Most IRIS FailSafe system configurations require one. Check if your system configuration requires a filesystem section in the ha.conf file.
ha_cfgverify: webserver <name> : httpd-optionsfile and httpd-script must be specified
Either both httpd-optionsfile and httpd-script must be specified or both must not be specified.
ha_cfgverify: webserver <section_name> section must have the backup-node entry ha_cfgverify: webserver <section_name> section must have the server-node entry
The webserver section_name block of the configuration file must have server-node and backup-node entries.
ha_cfgverify: webserver <section_name> : the backup-node entry <node_name> is invalid ha_cfgverify: webserver <section_name> : the server-node entry <node_name> is invalid
The server-node and backup-node entries must have a node section in the configuration file.