Page 1 of 1
OpemKM 5.0.4 conf file
PostPosted:Thu Sep 01, 2011 7:34 pm
by ancoraopenkm
Hi Forum,
I have been using OpenKM for a couple of weeks now. Yesterday I got the following error OKM-012015(GetRootFolder):path not found and since then I am not able to get any of my data in OpenKM. Checked openkm.cfg file and it is empty. Could this have been caused due to this error and what was the cause ? How do I recover my previous configuration ?
Any help is highly appreciated.
Thanks
Amil
Re: OpemKM 5.0.4 conf file
PostPosted:Fri Sep 02, 2011 7:58 am
by pavila
If OpenKM.cfg file is empty, someone has delete its contents (your server has been hacked) or you have a hardware problem. When I say hardware problem, I mean a disk failure. In this case, restore a backup in a new computer.
Re: OpemKM 5.0.4 conf file
PostPosted:Fri Sep 02, 2011 8:01 am
by jllort
Which OS do you have ? do you have application shared to internet by port 8080 ? that could be other cause.
Re: OpemKM 5.0.4 conf file
PostPosted:Mon Sep 05, 2011 10:23 pm
by ancoraopenkm
Thanks for the reply.
I have noticed that OpenKM has updated itself automatically from version 5.0.4 to 5.1.5 without any user interaction.
Open KM has been installed on Cent Os 5.6 64 bit/MySQL as local DB and was configured to keep data on network disk. Yes, JBoss is on port 8080. Due to this auto update it has lost all of its local repository and configuration. Is there a way to recover the missing data?
How do configure the app so that it does not use port 8080 ?
TIA
Re: OpemKM 5.0.4 conf file
PostPosted:Tue Sep 06, 2011 9:06 pm
by jllort
Sorry ancoraopenkm but OpenKM not updates automatically without any human interaction basically becase there's no automatic OpenKM process for doing it, we would like to say we've got this kind of magic but we have not it.
Is for some reason you've lost repository then must use the backup to restore it ( lose repository means lose binary information ) binary information only can be restored from backup. I don't know what happened on your system, but it's not normal.
Hope you have not jboss 8080 port exposed to internet that has some security problems, we've got a page talking about how making jboss more secure
http://wiki.openkm.com/index.php/Securing_JBoss but I suggest if it's your case you configure jboss behind apache proxy.
Changing server.xml into server/default/deploy/jboss-web.deployer folder you can change port 8080 to 80