Open Source Document Management System | OpenKM

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...

For a moment, by the way, I was thinking about whether davfs (as shipped with Debian) could be the culprit; but the problem appears also when I am trying to access the file through the webdav URL with a webbrowser. Maybe it's a problem with the webdav implementation on the server side.

I have changed the name to all-lowercase now. It makes no difference. This is written to catalina.log when I am trying to access (i. e. copy) the file: 2016-12-30 10:20:28,044 [http-bio-127.0.0.1-8080-exec-93] INFO com.bradmcevoy.http.HttpManager- GET :: http://127.0.0.1:8080/OpenKM/webdav/okm_root/...

Try stupid thing, rename .PDF file to .PDF The icon associated for this document in OpenKM is the PDF icon ? can you check in properties tab the mime-type value ? I have renamed the document in question from NeuesDokument11.pdf (extension "pdf" with small letters) to NeuesDokument11.PDF (extension ...

The directory is mounted on the server locally through davfs2: # cat /etc/mtab https://localhost/OpenKM/webdav/ /var/import/localhost fuse rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=16384 0 0 # # ls -l /var/import/localhost/ insgesamt 3 drwx------ 2 root root 0 Sep 26 16:37 l...

First, here is the result of the rectified database query. The query points to the correct file. Bildschirmfoto20.12.2016103224_1.png The next screenshot shows the file in question on the regular OKM desktop. Bildschirmfoto20.12.2016 1036051.png The third screenshot shows the directory through webda...