Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS

HFdaemon process fails to load the CDE after rebooting and rebuilding the desktop process fails

Product
  • Brisque™ 4.0
  • Brisque 3.0
  • Brisque Serve 4.0
  • Timna™ 3.0

Platform

  
  • E30—Victory
  • 43P–140—Tiger1
  • 43P–150—Tiger2
  • F50—Wildcat (2 and 4 CPUs)
  • 44P–170—Hammerhead
  • 6F1—Condor (2,4 and 6 CPUs)

Operating system

  

IBM® AIX 4.2.1 or IBM AIX 4.3.3, Mac OS® X

Symptoms

  

Symptom 1:

The HFdaemon process produces core dumps at approximately 5 minute intervals. When you reboot the system, the HFdaemon fails to load the CDE.
The following output displays when the HFdaemon process produces a core dump:

C60BB505 0129150603 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129150003 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129145503 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129145003 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129144503 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129144003 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
C60BB505 0129143503 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED

When you examine the start.ScitexServers.log file after the HFdaemon process has started, the following output displays:

Opening the DHS Server < Ver 2.1 20.09.95 > ...
DHServer Registered in the Program Manager
Running the DHServer... (type ctl-c to exit)
Start HFdaemon...
It's already loaded. Its kmid is 080946fc.
101 1 /dataVolumes/ripro1.2.0
101 1 /dataVolumes/ripro1.2.1
101 1 /dataVolumes/ripro1.2.2
101 1 /dataVolumes/ripro1.3.0
101 1 /dataVolumes/ripro1.3.1
101 1 /dataVolumes/ripro1.3.2
104 0
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
stop run...
stop run...
stop run...
stop run...
stop run...
101 1 /dataVolumes/ripro1.2.0
101 1 /dataVolumes/ripro1.2.1
101 1 /dataVolumes/ripro1.2.2
101 1 /dataVolumes/ripro1.3.0
101 1 /dataVolumes/ripro1.3.1
101 1 /dataVolumes/ripro1.3.2
104 0
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
stop run...
stop run...
stop run...
stop run...
stop run...
101 1 /dataVolumes/ripro1.2.0
101 1 /dataVolumes/ripro1.2.1
101 1 /dataVolumes/ripro1.2.2
101 1 /dataVolumes/ripro1.3.0
101 1 /dataVolumes/ripro1.3.1
101 1 /dataVolumes/ripro1.3.2
104 0
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
HFaddDirThread_t::run
stop run...
stop run...
stop run...
stop run...
stop run...

Symptom 2:

Core dumps occur when the rebuilding-the-desktop process starts, which causes the rebuild process to fail.
The following output is displayed when the rebuilding the desktop process produces a core dump:

file '/dataVolumes/ripro1.3.0/50176/Rip/output/50176 NRL impo.job/
.Previewprf_RS_50176 NRL impo.assg': name too long, ignored file '/
dataVolumes/ripro1.3.0/Network Trash Folder/Trash Can #3/
50176 AFL impo.job/.Previewprf_ RS_50176 AFL impo.assg':
name too long, ignored open /dataVolumes/ripro1.3.0/Network Trash
Folder/TrashCan#3/50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/ 50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
50172.job/50172.job/ 50172.job/50172.job/50172.job/50172.job/
.rsrc/~~300001_63a224_7c8F
: File name too long
Segmentation fault(coredump)

Cause

  

A virus has infected the AIX volume. The virus creates a folder that propagates itself, which causes the HFdameon and rebuild processes to fail. It is likely that the virus was transmitted over the network from a PC.

Solution

  
  1. To isolate the folder that has propogated itself, at the AIX command line prompt, run the fsck command on the affected volume.
  2. Delete all occurences of the propagated folder.
  3. Log out of the system, and then log in to the system.
Technical contact(s)
  

Lev Weissman
Submitted by
  

Lev Weissman
Date submitted

19 Feb 2003

    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.