HP XC System Software Release Notes for Version 3.1

# ps -eaf | grep mysql
Three processes should be listed: grep, mysqld_safe, and mysqld. If you do not see
mysqld_safe and mysqld, proceed to step 4.
3. Use the process ID (PID) of /usr/libexec/mysqld (the number just after the process
owner name) to kill mysqld manually. If the mysqld process is not listed, but there is a
mysqld_safe process, use that PID instead.
# kill mysqld_PID
This process should kill both mysqld and mysqld_safe.
4. Restart the mysqld service:
# service mysqld restart
The command you were trying to invoke should now be able to connect to the database.
7.7 Consider Disabling Attribute Caching on Large-Scale Systems
On large-scale HP XC systems, NFS attribute caching can cause inconsistencies when large
numbers of client nodes are asked to access files that have been updated recently and the attribute
caching data on the client has not expired. Disabling attribute caching eliminates the problem
but may degrade performance for frequent file operations requiring file attribute data.
You can disable attribute caching using the noac mount option on all external NFS mounts.
7.8 Possible Problem with ext3 File Systems on SAN Storage
Issues have been reported when an ext3 file system fills up to the point where ENOSPC is returned
to write requests for a long period of time, and the file system is subsequently unmounted. A
forced check is initiated (fsck -fy) before the next mount. It appears that the fsck checks
might corrupt the file system inode information.
This problem has been seen only on fibre channel (SAN) storage; it has not been seen with directly
attached storage or NFS storage.
For more information about details and work arounds, consult Bugzilla number 175877 at the
following URL:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175877
7.9 Notes That Apply to Improved Availability
This section contains notes that apply when improved availability of services has been configured.
The HP XC System Software Installation Guide describes how to configure services for improved
availability.
7.9.1 Restart Serviceguard Quorum Server if Quorum Server Node is Re-imaged
You must restart the Serviceguard quorum server if the quorum server node is re-imaged while
improved availability is running. Issue the following command on the quorum server node to
restart the quorum server and update the /etc/inittab file:
# /opt/hptc/availability/serviceguard/startquorum
7.9.2 Benign Messages
When a node that is providing improved availability of services through Serviceguard is initially
configured and booted, a Serviceguard cmcld daemon is started. Part of the processing performed
by the cmcld daemon is to verify that the node is correctly configured for availability and to
determine whether or not the node should rejoin an already-active Serviceguard cluster.
The following benign error message are generated in the /var/log/nconfig.log output of
booting nodes that are configured for availability; you can safely ignore these messages:
7.7 Consider Disabling Attribute Caching on Large-Scale Systems 57