Search

Seems to be fixed after reboot.

Getting this while migrating from 6.3.6 to 6.3.7: 2019-06-09 16:28:06,453 [localhost-startStop-1] INFO com.openkm.util.FormUtils$LocalResolver- resolveEntity(publicId=-//OpenKM//DTD Property Groups 2.0//EN, systemId=http://www.openkm.com/dtd/property-groups-2.0.dtd) => /opt/openkm/tomcat/webapps/Ope...

Into the webapps should be OpenKM.war file what when starting is exploding the OpenKM folder. It is doing precisely that. When I'm starting OpenKM after having the webapps/OpenKM folder removed, it is created again. Just the application can apparently not work with it, for some reason. The older Op...

I have deleted work/Catalina and webapps/OpenKM, which have been replaced in restart. What I'm getting now is 2019-06-08 00:34:01,084 [main] INFO org.apache.coyote.ajp.AjpProtocol- Initializing ProtocolHandler ["ajp-bio-127.0.0.1-8009"] 2019-06-08 00:34:01,095 [main] INFO org.apache.catali...

This seems a bit outdated... I have moved up to 6.3.3 now and I'm still getting these errors. Apparently when there are "fancy" characters/symbols in the header lines. Here's another example: 2019-06-07 09:00:00,109 [Thread-125] INFO com.openkm.core.UserMailImporter- *** User mail importer...

The installation has now been moved from an ancient Debian machine to Devuan Ascii. After that, it has been upgraded to 6.3.2. So far, everything looks good. Just the Administration Dashboard still shows "Version: 6.3.0 (build: 8156)".

It's the tomcat version that came with 6.3.1. As soon as I have migrated, I will go through the update routine until I'm on the most recent version.

More precisely: I installed 6.3.0 and then upgraded to 6.3.1.

Very cool. The target machine is Devuan 2.0 Ascii.

I'm on Debian Linux, but an outdated version (Wheezy). The whole installation will soon move to a up-to-date machine.

Kicking the tempfiles now.
Cheers, Matthias

This means it is generally possible to simply move the whole installation with it's directory between machines, provided the path names, database settings and file/directory access rights remain the same.

On 6.3.1, I have found that over time about 80.000 okm*.tmp files have accumulated in tomcat/temp. They are using 20GB of storage altogether. I have randomly picked files and inspected them. Some of them contain PGP-keys, some are emails, and some (the bigger ones) are binary files. The date ranges ...

Good evening all, I am still running an aged 6.3.1 installation on a Debian machine. Rather than upgrading the installation, I want to move the whole repository to a new machine I have recently acquired, preferably to the most recent release (nothing has been installed on the new machine yet). Is th...

I realize this one sounds pretty stupid, but still. I am quite positive that some time ago I upgraded my installation from 6.3.0 to 6.3.1. The administration tab, however, displays this: OpenKM - Knowledge Management Version: 6.3.0 (build: 8156) © 2006-2014 OpenKM Is there another way to make sure w...

I'm still running 6.3.0 Community Edition and have missed several new releases. Can I migrate from 6.3.0 to 6.3.3 straight, or do I have to take each step, from 6.3.0 to 6.3.1 and so on? What would be the correct process? Haven't found this in the FAQ, maybe it's just me...
TIA
Matthias

Mail export fails as soon as the export process hits a mail with unexpected characters in the address line. I have the following in catalina.log: 2017-04-05 11:50:36,064 [http-bio-127.0.0.1-8080-exec-85] ERROR com.openkm.util.impexp.RepositoryExporter- Illegal address javax.mail.internet.AddressExce...