Appendix D. Error Messages
The following are commonly seen error messages:
Could Not Start CXFS Client Error Messages
The following error message indicates that the cxfs_client
service has failed the license checks:
Could not start the CXFS Client service on Local Computer.
Error 10038: An operation was attempted on something that is not a socket. |
You must install the license as appropriate. See the CXFS Administration Guide for SGI InfiniteStorage.
The following messages may be logged by CMS.
CMS excluded cells 0xXXX with incomplete connectivity |
Generated when CMS delivers a membership that excluded some
new cells that had not established connections with enough
cells yet to be admitted. 0xXXX is a bitmask
of excluded cells.
CMS calculation limited to last membership:configuration change incomplete on cells 0xXXX |
Generated when the leader is attempting to make a configuration
change current (that is, actually use the change on all nodes), but some
cells in the cluster have not yet received the configuration change staged
(uploaded and ready to be made current). 0xXXX
is a bitmask of cells that do not yet have the change in their configuration.
Changes make their way through the cluster asynchronously, so this situation
is expected. It can take a few attempts by the CMS leader before all nodes
have the change staged. As long as this situation resolves eventually,
there is no problem.
CMS calculation limited to last membership:recovery incomplete |
Generated when new members were disallowed due to recovery from
the last cell failure that is still being processed.
cxfs_client: op_failed ERROR : Mount failed for aixdisk0s0 |
A filesystem mount has failed on an AIX node and will be retried
cxfs_client:op_failed ERROR: Mount failed for concat0 |
A filesystem mount has failed on an Linux 32-bit, Mac OS X,
Solaris, or Windows node and will be retried.
Network Connectivity Messages
unable to join multicast group on interface
unable to create multicast socket
unable to allocate interface list
unable query interfaces
failed to configure any interfaces
unable to create multicast socket
unable to bind socket |
Check the network configuration of
the node, ensuring that the private network is working and the Windows
node can at least reach the metadata server by using the
ping command from a command shell.
You may see the following error message repeatedly on a node when
you stop services on another node until the shutdown completes:
Nov 4 15:35:12 ray : Nov 04 15:35:12 cxfs_client:
cis_cms_exclude_cell ERROR: exclude cellset ffffffffffffff00 failed: Device busy |
After the other node completes shutdown, the error will cease to
be sent. However, if the error message continues to appear even after
shutdown is complete, another problem may be present. In this case, contact
your SGI support person.
The following are common Windows CXFS messages.
cis_driver_init() failed: could not open handle to driver
cis_driver_init() failed: could not close handle to CXFS driver |
The
CXFS driver may not have successfully started. Check the system event
log for errors.
cis_generate_userid_map warning: could not open group file |
The
group file could not be found.
Even with passwd and group
warnings above, filesystem mounts should proceed; however, all users will
be given nobody credentials and will be unable to view
or modify files on the CXFS filesystems. For more information about these
files, see “Log Files on Solaris” in Chapter 8 and “Log Files and Cluster Status for Windows” in Chapter 9.
Also see the log files on the server-capable administration node; for
more information, see the CXFS Administration Guide for SGI InfiniteStorage.
cis_generate_userid_map warning: could not open passwd file |
The
passwd file could not be found.
could not get location of passwd/group files
could not retreving fencing configuration file name from registry
error retrieving passwd filename
error retrieving group filename
error retrieving fencing filename |
The registry entries
for the location of the
passwd,
group,
or
fencing.conf files may be missing, or the path provided
on the command line to the CXFS Client service is badly formed. Reset
these values by modifying the current installation as described in
“Modifying the CXFS Software for Windows” in Chapter 9.
could not open passwd file
could not open group file
fencing configuration file not found |
Check that the
passwd,
group and
fencing.conf
files are in the configured location and are accessible as described in
“Checking Permissions on the Password and Group Files for Windows
” in Chapter 9.
no valid users configured in passwd file |
No users in the
passwd file could be
matched to users on the Windows node. All users will be treated as user
nobody for the purpose of all access control checks.
no valid groups configured in group file |
No groups in the
group file could be
matched to groups on the Windows node. Attempts to display file permissions
will most likely fail with the message
Unknown Group Errors.
op_failed ERROR: Mount failed for concat0 |
A filesystem mount has failed and will be retried.
unable to create mount point
Configured drive letter may already be in use |
Check that
the configured drive letter is not already in use by a physical or mapped
drive.
Unix user is something other than a user on the NT domain/workgroup
Unix group is something other than a group on the NT domain/workgroup |
This warning indicates that a username or groupname is
not a valid user or group on the Windows node, which may be confusing
when examining file permissions.