Page 1 of 1
6.2.2 Random Crash - No error in log
PostPosted:Sun Mar 10, 2013 4:59 am
by Alexires
Hi,
While I'm doing a massive repository import, OpenKM seems to crash... except it isn't a crash so much as it just stops. There doesn't appear to be any errors in the logs (catalina.log or RepositoryImporterxxxxx.log) to indicate why this is happening.
Any ideas?
Re: 6.2.2 Random Crash - No error in log
PostPosted:Sun Mar 10, 2013 9:31 am
by jllort
Which openkm version are you using. Without more information I suggest go to administration / crontab task and meanwhile you do import disable text extractor ( could be a problem with your JVM low resources of memory etc.. in your server and that make your tomcat fails and get an unespected hang).
Re: 6.2.2 Random Crash - No error in log
PostPosted:Mon Mar 11, 2013 1:43 pm
by Alexires
Running OKM 6.2.2 build 7815.
I've disabled the text extractor and I'm trying again. Let you know how I go.
Re: 6.2.2 Random Crash - No error in log
PostPosted:Tue Mar 12, 2013 5:59 pm
by pavila
Are you running on Linux or Windows?
Re: 6.2.2 Random Crash - No error in log
PostPosted:Wed Mar 13, 2013 8:37 am
by Alexires
Linux. Found out what the problem was: VPS admin was killing the task because it was using too much CPU/IO. Thanks for the help anyway; nothing to worry about.
Re: 6.2.2 Random Crash - No error in log
PostPosted:Thu Mar 14, 2013 9:50 pm
by jllort
It's normal OpenKM consumes a lot of cpu when is indexing files. That's normal and is not a bad thing, for example if you have uploaded a lot of documents ( massive imports ) the batch queue to index document will be great and will start every N minutes ( you can control with crontab task ) the indexing process. In pdf or ocr can take several seconds to complete a document indexing ( a lot of pages or images into pdf, and a similar problem with ocr ), these are high cpu cost. You can index with several cpu's at same time I suggest you take a look here to optimize
http://wiki.openkm.com/index.php/Applic ... extraction
Other thing you can do is change configuration parameters from day to night with crontab task to make less agresive from day at more at nigh