You are viewing limited content. For full access, please sign in.



LfDcc stuck at 25% cpu (basically one core)

asked on April 24, 2015

On the Scheduler machine (we have 1 scheduler and 2 workers). the LfDcc process is stuck at using 25% cpu (a single core on a 4 core machine).  What is the best way to diagnose what is going on?

Also a related question that I could not find the answer to.  How do you resubmit a failed job?




0 0


replied on April 27, 2015 Show version history


I tend to see this problem when I don't have any image cleanup options selected within the Schedule OCR settings on the bottom right in the Workflow designer. I add the highlighted settings within the screen capture below so that I don't run into that issue. What I believe is that it may possibly be that the images are turned on their side or they are too large for DCC process. You can also edit your search to avoid large images such as maps. I'm not sure how to resubmit a failed job either.



You can also go into Task Scheduler  on the scheduler machine. Find the task that is scheduled for the DCC, it should have the workflow name, and then right click it and go to properties. It is defaulted to run for 3 days. You can change the amount of time that it runs. If it is a single repository that it is working on  then I would have it run for 6-8 hours.

If there are errors there should a tab under the event viewer under Applications and Services Logs->Laserfiche Distributed Process.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.