Cannot Boot Applications With Host Monitor Timeout Errors Due to Corrupt Config Files.

Unable to boot Applications software due to a Host monitor Timeout after 250 seconds See Long Description This was a running system. The tech decided to reboot the system, and then it would never come all the way back up again. Applications software would not come up. After a while, the message "Host monitor Timeout after 250 seconds" was displayed. By viewing the message log from a C-shell using the commands shown below, we found the errors shown below. These same two errors were logged on every failed applications software boot attempt. The two messages are reporting the process "ifcc". Knowing that "ifcc" stands for "Image File Creation and Control", we suspected that the image database was corrupt and would need recovery. We suspected the system was unable to mount the image database completely, and this could be the reason that Applications software would not boot. Looking at the disk partitions using the command "df -k", the /export/home1 image partition was seen to be present (it was 56% full) but perhaps it was corrupt. cd /usr/g/service/log [enter] more gesys* [enter] Fri Sep 1 11:31:19 2006 200002372 signa3 hostMonitor ssProcStart.c 927 The process ifcc took too long to start up. Fri Sep 1 11:32:04 2006 200002352 signa3 hostMonitor ssProcStop.c 812 A HOST_SHUTDOWN was initiated by the death of ifcc.