Open Source Document Management System | OpenKM

After a rough shutdown OpenKM would not come up again. It complained that it could not mount the repository.

Is there a method to correct the errors in the repository after an inevitable power outage? Or possibly a utility/method for extracting your data out of the dead repository.

I logged into the support portal but didnt see any documentation regarding repository issues.

The Messages on startup are,
Thanks.
-Lexangl

That's the reason why contrating some technical supporting is not a bad idea. For what you're saying your system has been down ( some power problem ) and system has been degradated. Normally OpenKM has no internal problems, the real problem comes when the mother board or disk damage, and I think it could be what it's happening in your system. In these case there's no way to recover information directly from hard disk or database if you've configured openkm there. You must starting a retore process from your backup. Hope you're doing backup well. Sometime mother board problems affects hard disk, and changing mother board solves it, sometimes mother board breaks the disk too, I don't know if you have lost chains in your disk or I/O errors. But if you're in some hardware problem, before restoring your backup ensure new hardware is OK.

UPS is not a bad idea, for 90€ you'll can buy one and in server is always a good idea.

jllort wrote:That's the reason why contrating some technical supporting is not a bad idea. For what you're saying your system has been down ( some power problem ) and system has been degradated. Normally OpenKM has no internal problems, the real problem comes when the mother board or disk damage, and I think it could be what it's happening in your system. In these case there's no way to recover information directly from hard disk or database if you've configured openkm there. You must starting a retore process from your backup. Hope you're doing backup well. Sometime mother board problems affects hard disk, and changing mother board solves it, sometimes mother board breaks the disk too, I don't know if you have lost chains in your disk or I/O errors. But if you're in some hardware problem, before restoring your backup ensure new hardware is OK.

UPS is not a bad idea, for 90€ you'll can buy one and in server is always a good idea.

Thanks for the response.

I have a RAID5 setup that verified when it came back up. I also tried restoring from the previous nights backup, and it gives the same error. No other data has seems to have been corrupted on the hard drive array.

Just to try your idea, I moved the OpenKM data to another physical server and tried restoring it there. I still get the same errors. Is it possible that with a bad shutdown process? or error during operation OpenKM might have corrupted the repository? I have seen this one other time during testing of OpenKM 3 on an Ubuntu 8 server. One time I did a shutdown on OpenKM and it would never startup again, complaining of a bad repository.

I am still testing it to see if we want to deploy OpenKM in our enterprise environment, and am just trying to make sure it is stable. During the actual deployment corporate wide I am sure we will contract professional services.

Have you tried to restoring backup before ?

In a bad shutdown you can make something really bad to repository, for example if some user is making a transaction and you jboss is suddently stoped can happen something bad to repository, it's really a very strange case, but can happens, and for what you're saying to me seems could be it. But is not a reason why backup is not restoring.

jllort wrote:Have you tried to restoring backup before ?

In a bad shutdown you can make something really bad to repository, for example if some user is making a transaction and you jboss is suddently stoped can happen something bad to repository, it's really a very strange case, but can happens, and for what you're saying to me seems could be it. But is not a reason why backup is not restoring.

I have restored backups before with success. Just a little be of history to explain why I am concerned about the repository.

The first time we setup a test for OpenKM 3 it worked great. We uploaded test documents and shutdown and restarted OpenKM a few times to test. After a few days, we shutdown OpenKM, then started it via run.sh, and it suddenly gave IO errors and aborted loading the repository. Everything we tried had no effect.

We eventually scraped the old install and started over. It worked for 3 weeks perfectly, with backups and test restores. Suddenly, on a routine shutdown/startup it did it again.

Our company really likes the product and I have a purchase order request for OpenKM Enterprise on my desk. However I am still concerned about the repository errors. This last error, even though it was a crash, is the same errors as the first two times, and even when I try to restore the most recent backup.

Again thanks for your replies. I am just trying to make due diligence for my company.

Have you changed default OpenKM configuration ? to store in database etc... ? This kind of errors are difficult to solve by forum, really I'll must connecting to your system to understand what has happened. And as I said to you it's not normall it can not restore backup.

For back up you must do it:
1- Always getting and older backup version ( not overwriting )
2- Stop jboss ( you make backups stopping jboss no ?
3- Make backup ( with rsync incremental it's best option )
4- Starting up server ( if sever not starts then here we've got the problem, and backup we've made is not good )

What has happened here ? althought OpenKM is still running, system has been degraded, we stop, make a backup of degraded system, and then when try starting openkm it not starts ( for it reason i says that must have two cycle older backup ). This type of error is really very very strange, and we've only seen in a systems where are I/O disk errors ( in comparation is something similar as oracle database with file system errors, continue running, but when is stopped can not turn to starting and you must make a restoring ).