HP XC System Software Installation Guide Version 3.2

Table 12-2 Software Upgrade Log Files (continued)
ContentsFile Name
Results of the YUM upgrade
/var/log/yum.log
Symbolic links to HP XC kernel-related RPMs on the
HP XC System Software Version 3.2 DVD
/var/log/upgrade/kernel/RPMS
Symbolic links to HP XC RPMs on the HP XC System
Software Version 3.2 DVD
/var/log/upgrade/RPMS
• If you see errors in the /var/log/postinstall.log or /var/log/yum_upgrade.log
files, fix the problem by manually installing the RPMs that failed to upgrade properly:
1. Mount the HP XC System Software DVD:
# mount /dev/cdrom /mnt/cdrom
2. Change to the following directory:
# cd /var/log/upgrade/RPMS
3. Install the RPM or RPMs that failed to upgrade properly:
# rpm -Uvh rpm_name
• An upgraded system contains the xc_prev_version attribute in the configuration and
management database. Use the following command to determine if this attribute exists:
# shownode config sysparams | grep version
cmdb_version: 1.26
xc_prev_version: V2.1
xc_version: V3.0
12.7.1 The upgradesys Utility Might Fail While Backing Up the Database
The upgradesys utility initiates the managedb backup command to back up the current
database. If a database table is corrupted, the mysqldump fails with the following error message:
Backing up database to
/opt/hptc/etc/sysconfig/upgrade/upgradesys.dbbackup-20061101164854.sql ...
mysqldump: Got error: 1016: Can't open file: 'CPUTotalsLog.MYI' (errno: 145)
when using LOCK TABLES
Could not perform backup:
Bad file descriptor at /opt/hptc/database/sbin/backup line 83,
<CONF> line 12.
Can't dump databases: Bad file descriptor at /opt/hptc/sbin/upgradesys
line 127, <STDIN> line 1.
If this failure occurs, run the following command to correct the database tables:
# myisamchk -r /var/lig/mysql/*.MYI
After the database tables are corrected, initiate the upgradesys utility again.
12.7.2 The hptc-ire-serverlog Service Might Not Start
The hptc-ire-serverlog service is responsible for logging node configuration (nconfig) and
imaging events to the /hptc_cluster/adm/logs/imaging.log file. Follow this procedure
to verify that the service is running. If it is not running, start the service.
1. Use the following command to verify that the hptc-ire-serverlog service is running
after the cluster_config [--migrate|--init] processing is complete:
# service hptc-ire-serverlog status
hptc-ire-serverlog is dead, but pid file exists
2. Determine if the /hptc_cluster/adm/logs/imaging.log file exists. If this file does
not exist, use the following command to create it. If this file does not exist, the startsys
utility fails.
178 Troubleshooting