HP StorageWorks Scalable File Share - Manual (Page 294)

Troubleshooting 9–70
When this happens, the SFS service prints a message similar to the following in the
/var/
log/messages
file:
sfsmount: Waiting for IB to be ready.
If this state persists for a long time, investigate the InfiniBand network. (You can log in and
run the
vstat
command to confirm the port state.)
• If some of the services are in the
recovering
state, the mount operation may be delayed for
any of the reasons described above (for the scenario where all file systems are in the
running
state). In addition, Lustre may reject requests because the
recovering
state requires all client
nodes to be actively connected before continuing. If any client node fails to connect (for
example, because it has been rebooted or remains down), Lustre must wait for up to 10 minutes
before timing out the recovery operation.
In such a situation, you will see that not only is the node that is currently being booted failing to
connect, but that other nodes (that were not rebooted) are also not connected. This is a normal
process in Lustre and you must be patient. Specifically, do not reboot any of the HP SFS servers;
if you do so, the 10-minute timeout period will restart.
9.43 Recovering after using the ifdown command
If you use the
ifdown
command on the site network or Gigabit Ethernet interconnect on the server that is
running the administration service (usually the administration server), the alias IP address on the network
stops working. This means that access to the LDAP database fails.
To restore the alias IP address functionality, run the
configure server
command on the server that is
running the administration service.
9.44 Password needed for ssh access
Normally, you do not need to supply a password to log in to an Object Storage Server from the
administration server. However, if an Object Storage Server is in the
not-configured
state, you must
supply a password when you log in to the server.
There are two main reasons why a server may be in the
not-configured
state when you attempt to log
in, as follows:
• You logged in too early, and the server is still in the process of being configured. Wait a few minutes
and then attempt to log in again.
• A failure is preventing the configuration process from completing. Use the
show server
server_name
command to determine the cause of the failure. When you have corrected the
problem, reboot the server.
9.45 The syscheck command reports that the Insight Manager Agents
are not running
The
syscheck
command may report a warning message similar to the following:
south3 Insight Manager Agents (hpasm) not running.
If this happens, you can correct the problem by logging in to the server and running the following
commands:
# service hpasm stop
# service hprsm stop
# service hprsm start
# service hpasm start
# service lsmon_scripts restart