ConcourseConnect Support

Support
Corporate
PUBLIC PROFILE

Back to topics

Discuss Installation and Upgrade

The path could not be created or copied to: /opt/concursive/connect/fileLibrary/

You need to be logged in to post messages

This question is unanswered

The path could not be created or copied to: /opt/concursive/connect/fileLibrary/

8/3/2011 11:05 PM EDT

Hi,

When I configure the file library, during the web-base setup, it print the error "The path could not be created or copied to: /opt/concursive/connect/fileLibrary/". Even if I select another different path, for example, /home/chendy, it print the same error.
I think it should be the security setting problem in Tomcat. But can you tell me how to solve the problem?
Thank you very much.

deyan

2011 10:10:30 am java.util.prefs.filesystempreferences$2 run
warning: couldn't create user preferences directory. user preferences are unusable.
aug 4, 2011 10:10:30 am java.util.prefs.filesystempreferences$2 run
warning: java.io.ioexception: no such file or directory
aug 4, 2011 10:11:02 am java.util.prefs.filesystempreferences checklockfile0errorcode
warning: could not lock user prefs. unix error code 2.
aug 4, 2011 10:11:02 am java.util.prefs.filesystempreferences syncworld
warning: couldn't flush user prefs: java.util.prefs.backingstoreexception: couldn't get file lock.
aug 4, 2011 10:11:32 am java.util.prefs.filesystempreferences checklockfile0errorcode, there are errors in the wsrp4j-proxyportlet.2011-08-04.log file:
aug 4

(1 out of 1 person found this post useful.)

1. 11/7/2011 4:13 AM EST

Problem Identified (I think), and a solution is suggested, as follows:

http://www.allaboutbalance.com/articles/disableprefs/

This info needs to get to the developers ASAP for version 2.0.3. I'm evaluating this product for deployment, and needless to say: getting stuck on the install screen does not bode well for market adoption. The features list is impressive -- but all useless if I can't even install it because of this bug. In all fairness -- it is not concursive's fault, it is a java lib bug, but you should vette this workaround as soon as possible.

FYI: I tried everything to coax this thing into working. No matter WHAT YOU DO with file permission and ownership settings on any path in the filesystem, this bug is a show stopper because of the reasons mentioned in the link.

Good luck, and I look forward to a workaround-patched version soon to evaluate.

2. 11/17/2011 10:51 AM EST
Default user photo

By Matt Rajkowski

Concursive Corporation
Product Design

airplane-icon-100x100.png

We truly haven't seen this issue before, but no doubt there is some configuration that is causing a problem. Please list your operating system and specific version of java and tomcat.

The Java API tries to store a preference in the user's home directory. If the user that runs Tomcat does not have a home directory, then after a restart the user will be prompted to configure the application again. Choosing the same path reloads the existing configuration so make sure you restart Tomcat to verify if it really stuck.

If this occurs, then in the Tomcat startup script, you can add a variable called CATALINA_OPTS, or use an environment variable, with a directory that the tomcat user does have access to...

CATALINA_OPTS="-Djava.util.prefs.userRoot=/opt/concursive/connect/userPrefs -Djava.util.prefs.systemRoot=/opt/concursive/connect/systemPrefs"

2 results found