HP StorageWorks 9100 HP StorageWorks 9100 Extreme Data Storage System release - Page 13

Issue Description 25844 The exdsmgr command sometimes responds with: "Unable to contact database...The service may be transitioning. Please try again." This message can indicate that a server has failed. Within a few seconds the database should failover to a backup server and the exdsmgr command will work normally. However, if the problem persists, there is a problem with access to the database. Workaround: You can isolate the problem as follows: 1. Use the mx alert status command to determine whether there are any issues with the Matrix. The following relate to the operation of the database: • Issues with the exdsadmin virtual host • Issues with the varmxso device (that is, the /var/mxso utility filesystem) • Issues with the mysqld service Usually, you can determine the source of the problem and its resolution at this time. The resolution may involve the reboot of a server. 2. Before rebooting any servers, determine whether the system is otherwise operating normally. If the mx alert status command is not reporting problems with other virtual hosts or other filesystems, then the system can continue operation and the /var/mxso filesystem and the database are not needed for file I/O operations, NFS file serving, or HTTP serving. If these are working normally, you can postpone any action to correct the database access until a later time. 3. Run the exds_stdiag command to check the physical connectivity and state of storage blocks. The database is located on /var/mxso which is normally hosted by the first array. See Chapter 14 of ExDS9100 administration guide, section "The exds_stdiag Utility" for information on how to interpret the output from exds_stdiag. If necessary, shutdown all servers and power cycle the affected storage components. 4. Run the df -h command to see if any filesystems (including local filesystems such as /var) are full. If so, clear out logs and other large files. 5. If /var/mxso is mounted and not full, reboot the server that is currently serving the exdsadmin virtual host alias (this is usually the first server). 6. If the source of the problem is not immediately obvious from the mx alert status command and the above actions, shut down all servers and boot one server only. The database should become operational again and you can use the exdsmgr command to boot the remaining servers. 7. If the varmxso (/var/mxso utility filesystem) appears to be corrupt, you can switch to a backup filesystem. Instructions for doing this are described in Chapter 13 of the ExDS9100 administration guide, section "Recovering from corrupt or lost utility filesystem (/var/mxso)" 25932 Syscheck reports "Additional rpm." The exdsmgr syscheck command reports messages such as the following for every server except the first server: Workaround: These reports can be ignored. 25933 Email alerts do not contain fully qualified domain name. By default when the alert mechanism sends email, the source address does not contain a fully qualified domain name. Workaround: You can correct this by editing the /etc/mail/sendmail.mc file. You must do this on every server. HP StorageWorks 9100 Extreme Data Storage System release notes 13