This section explains messages that are output upon error occurrence at executing the cfconfig command for each option specified to the command.
Content:
The CF startup routine has failed. This error message usually indicates that an unprivileged user has attempted to start CF. An additional error message, for this case, will also be generated in the system log file:
OSDU_start: failed to open /dev/cf (EACCES)
Corrective action:
Execute start, stop, and configuration of CF with a system administrator authority.
Content:
The CF startup routine has failed. This error message usually indicates that the CF configuration file /etc/default/cluster cannot be found. Additional error messages, for this case, may also be generated in the system log file:
OSDU_getconfig: failed to open config file (errno)OSDU_getconfig: failed to stat config file (errno)Corrective action:
Create a CF configuration file and /etc/default/cluster.
Content:
The CF startup routine has failed. This error message usually indicates that the CF configuration file does not match the physical hardware (network interfaces) installed in/on the node.
Corrective action:
Match the CF configuration file settings with the hardware (network interface) installed to the node.
Content:
The CF startup routine has failed. One cause of an error message of this pattern is that the CF cluster configuration file has been damaged or is missing.
Corrective action:
If you think this is the case, delete and then re-specify your cluster configuration information, and try the command again. If the same error persists, see below.
Additional error messages, for this case, will also be generated in the systemlog file:
OSDU_getconfig: corrupted config file
OSDU_getconfig: failed to open config file (errno)OSDU_getconfig: failed to stat config file (errno)OSDU_getconfig: read failed (errno)These messages are generated only when a failure occurs to the CF driver or other kernel components.
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Additional error messages, for this case, may also be generated in the system log file:
OSDU_getconfig: malloc failed
OSDU_getstatus: mconn status ioctl failed (errno)OSDU_nodename: malloc failed
OSDU_nodename: uname failed (errno)OSDU_start: failed to get configuration
OSDU_start: failed to get nodename
OSDU_start: failed to kick off join
OSDU_start: failed to open /dev/cf (errno)OSDU_start: failed to open /dev/mconn (errno)OSDU_start: failed to select devices
OSDU_start: failed to set clustername
OSDU_start: failed to set nodename
OSDU_start: icf_devices_init failed
OSDU_start: icf_devices_setup failed
OSDU_start: IOC_SOSD_DEVSELECTED ioctl failed
OSDU_start: netinit failed
If the device driver for any of the network interfaces to be used by CF responds in an unexpected way to DLPI messages, additional message output (in the system log) may occur, with no associated command error message. These messages may be considered as warnings, unless a desired network interface cannot be configured as a cluster interconnect. These messages are:
dl_attach: DL_ACCESS error
dl_attach: DL_ATTACH_REQ putmsg failed (errno)dl_attach: DL_BADPPA error
dl_attach: DL_OUTSTATE error
dl_attach: DL_SYSERR error
dl_attach: getmsg for DL_ATTACH response failed (errno)dl_attach: unknown error
dl_attach: unknown error hexvaluedl_bind: DL_ACCESS error
dl_bind: DL_BADADDR error
dl_bind: DL_BIND_REQ putmsg failed (errno)dl_bind: DL_BOUND error
dl_bind: DL_INITFAILED error
dl_bind: DL_NOADDR error
dl_bind: DL_NOAUTO error
dl_bind: DL_NOTESTAUTO error
dl_bind: DL_NOTINIT error
dl_bind: DL_NOXIDAUTO error
dl_bind: DL_OUTSTATE error
dl_bind: DL_SYSERR error
dl_bind: DL_UNSUPPORTED error
dl_bind: getmsg for DL_BIND response failed (errno)dl_bind: unknown error
dl_bind: unknown error hexvaluedl_info: DL_INFO_REQ putmsg failed (errno)dl_info: getmsg for DL_INFO_ACK failed (errno)It is also possible that while CF is examining the kernel device tree, looking for eligible network interfaces, that a device or streams responds in an unexpected way. This may trigger additional message output in the system log, with no associated command error message. These messages may be considered as warnings, unless a desired network interface cannot be configured as a cluster interconnect. These messages are:
get_net_dev: cannot determine driver name of nodename deviceget_net_dev: cannot determine instance number of nodename deviceget_net_dev: device table overflow - ignoring /dev/drivernameNget_net_dev: dl_attach failed: /dev/drivernameNget_net_dev: dl_bind failed: /dev/drivernameNget_net_dev: dl_info failed: /dev/drivernameget_net_dev: failed to open device: /dev/drivername (errno)
get_net_dev: not an ethernet device: /dev/drivernameget_net_dev: not DL_STYLE2 device: /dev/drivernameicf_devices_init: cannot determine instance number of drivername deviceicf_devices_init: device table overflow - ignoring /dev/scin
icf_devices_init: di_init failed
icf_devices_init: di_prom_init failed
icf_devices_init: dl_bind failed: /dev/scin
icf_devices_init: failed to open device: /dev/scin (errno)icf_devices_init: no devices found
icf_devices_select: devname device not foundicf_devices_select: fstat of mc1x device failed: /devices/pseudo/icfn - devname
(errno)icf_devices_select: mc1_select_dev failed: /devices/pseudo/icfn - devname (errno)
icf_devices_select: open of mc1x device failed: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: calloc failed: devnameicf_devices_setup: failed to create mc1x dev: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: failed to open /dev/kstat (errno)icf_devices_setup: failed to open mc1x device: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: failed to stat mc1x device: /dev/mc1x (errno)icf_devices_setup: failed to stat mc1x device: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: I_LIST failed: devname(errno)icf_devices_setup:I_LIST 0 failed:devname (errno)
icf_devices_setup: I_PLINK failed: /devices/pseudo/icfn - devname (errno)
icf_devices_setup: I_POP failed: devname (errno)
icf_devices_setup: I_PUSH failed: devname (errno)
icf_devices_setup: mc1_set_device_id failed: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: mc1x_get_device_info failed: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: mc1x device already linked: /devices/pseudo/icfn - devname
(errno)icf_devices_setup: mc1x not a device
mc1_select_device: MC1_IOC_SEL_DEV ioctl failed (errno)mc1_set_device_id: MC1_IOC_SET_ID ioctl failed (errno)mc1x_get_device_info: MC1X_IOC_GET_INFO ioctl failed (errno)Content:
The CF shutdown routine has failed. This error message is generated when CF resource of PRIMECLUSTER layer service is active or a CF resource is allocated to the PRIMECLUSTER layer service.
Corrective action:
RMS, SIS, OPS, CIP, and so forth, need to be stopped before CF is unloaded. Please refer to the README file of each layered-product software on how to stop the respective software. An additional error message, for this case, will also be generated in the system log file:
OSDU_stop: failed to unload cf_drv
In the special case where the cfconfig command was called by a shutdown script that is rebooting the system, the following additional error messages are generated in the system log file:
OSDU_stop: runlevel now n: sent EVENT_NODE_LEAVING_CLUSTER (#xxxx)
cfconfig: cannot unload: #0423: generic: permission denied
The CF shutdown routine has failed. This error message usually indicates that an unprivileged user has attempted to stop CF. You must have a administrator authority to start, stop, and configure CF. An additional error message, for this case, will also be generated in the system log file:
OSDU_stop: failed to open /dev/cf (EACCES)
Content:
This message is generated only when a failure occurs to the CF driver or other kernel components.
Corrective action:
Contact field engineers. Additional error messages, for this case, may also be generated in the system-log file:
mc1x_get_device_info: MC1X_IOC_GET_INFO ioctl failed (errno)OSDU_stop: disable unload failed
OSDU_stop: enable unload failed
OSDU_stop: failed to open /dev/cf (errno)OSDU_stop: failed to open mc1x device: /devices/pseudo/icfn (errno)
OSDU_stop: failed to unlink mc1x device: /devices/pseudo/icfn (errno)
OSDU_stop: failed to unload cf_drv
OSDU_stop: failed to unload mc1 module
OSDU_stop: failed to unload mc1x driver
OSDU_stop: mc1x_get_device_info failed: /devices/pseudo/icfnContent:
This usually indicates that nodename is too long. The maximum length is 31 characters.
Corrective action:
Change the nodename to within 11 characters.
Content:
This indicates that nodename contains one or more non-printable characters.
Corrective action:
Use characters that do not contain any blanks and that can be printed.
Content:
This error message usually indicates that there is an existing CF configuration.
Corrective action:
To change the configuration of a node, you must first delete (cfconfig -d) any pre-existing configuration.
Also, you must have administrator authorities to start, stop, and configure CF. A rare cause of this error would be that the CF driver and/or other kernel components have somehow been damaged. If this does not resolve the problem, contact field engineers. Additional error messages may also be generated in the system log file:
OSDU_getconfig: corrupted config file
OSDU_getconfig: failed to open config file (errno)OSDU_getconfig: failed to stat config file (errno)OSDU_getconfig: malloc failed
OSDU_getconfig: read failed (errno)Content:
Too many devices have been specified on the command line. The current limit is set to 255.
Corrective action:
Change the number of devices specified by command lines within 255.
Content:
This error message indicates that the first argument "clustername" was accidentally been omitted when the cluster interconnect device was specified.
Corrective action:
Do not omit the first argument "clustername" when specifying a device for cluster interconnect using -s.
Content:
This error message indicates that the first argument, clustername, contains blank characters or those that cannot be printed.
Corrective action:
Specify a character string that does not contain blank characters or those that cannot be printed to the first argument, clustername.
Content:
This error message indicates that duplicate device names have been specified on the command line. This is usually a typographical error, and it is not permitted to submit a device name more than once.
Corrective action:
Specify devices names by avoiding double input.
Content:
This error message indicates that the specified device names are not CF-eligible devices. Only those devices displayed by cftool -d are CF-eligible devices.
Corrective action:
Specify a CF eligible device that is displayed by cftool -d to the argument.
Content:
Opening the CF device has failed.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message can occur if concurrent cfconfig -s or cfconfig -S commands are being run. Otherwise, this message is generated only when a failure occurs to the CF driver or other kernel components.
Corrective action:
Contact your field engineers. Additional error messages, for this case, may also be generated in the system log file:
OSDU_setconfig: config file exists
OSDU_setconfig: failed to create config file (errno)OSDU_setconfig: write failed (errno)Content:
This message indicates that the saved configuration cannot be read back. This may occur if concurrent cfconfig -s or cfconfig -S commands are being run, or if disk hardware errors are reported.
Otherwise, this message is generated only when a failure occurs to the CF driver or other kernel components.
Corrective action:
Contact your field engineers. Additional error messages, for this case, may also be generated in the system log file:
OSDU_getconfig: corrupted config file
OSDU_getconfig: failed to open config file (errno)OSDU_getconfig: failed to stat config file (errno)OSDU_getconfig: malloc failed
OSDU_getconfig: read failed (errno)Content:
This error message indicates that the device discovery portion of the CF startup routine has failed.
Corrective action:
See error messages associated with cfconfig -l above.
Content:
This error message indicates that required arguments to set CF over IP are not enough.
Corrective action:
Review the arguments.
Content:
This error message indicates that required arguments to set CF over IP are too many.
Corrective action:
Review the arguments.
Content:
This error message indicates that the argument specified to IP address is invalid.
Corrective action:
Review the arguments.
Content:
This message indicates that the CF configuration cannot be read. This may occur if concurrent cfconfig(1M) commands are being run, or if disk hardware errors are reported. Otherwise, this message is generated only when a failure occurs to the CF driver or other kernel components.
Corrective action:
Contact your field engineers. Additional error messages, for this case, may also be generated in the system log file:
OSDU_getconfig: corrupted config file
OSDU_getconfig: failed to open config file (errno)OSDU_getconfig: failed to stat config file (errno)OSDU_getconfig: malloc failed
OSDU_getconfig: read failed (errno)Content:
This message is generated only when a failure occurs to the CF driver or other kernel components.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This error message is generated if CF is still active (i.e., if CF resource(s) are active/allocated). The configuration node may not be deleted while it is an active cluster member.
Corrective action:
Stop the CF using cfconfig -u and then re-execute the command.
Content:
You must have administrator authorities to start, stop, and configure CF. This message is generated when a failure occurs the CF driver or other kernel components.
Corrective action:
Contact your field engineers. Additional error messages, for this case, may also be generated in the system log file:
OSDU_delconfig: failed to delete config file (errno)