Forum Discussion
We traced this down to some of the files/folders in the collaborator content cache (<Collaborator root>/tomcat/collaborator-content-cache) being owned by root insted of the lower-priviledged user normally used to run the server.
Recursively resetting the ownership of this directory remedied the problem.
Hi,
I don't see the folder collaborator content cache in our setup. Are there any other places to look for this folder?
- bkambach6 years agoOccasional Contributor
My installation just uses the default location, but the Collaborator documentation has some details about alternate locations:
https://support.smartbear.com/collaborator/docs/server/admin-tasks/content-storage.html
"If you decide to use the non-default content cache location, you can change it by editing the XML file: <Collaborator server installation>/tomcat/conf/Catalina/localhost/ROOT.xml. Find the
Parameter
element with thecontent-cache
name attribute. Thevalue
attribute of this element should be the path to the content cache. Relative paths are interpreted relative to the installation directory."- alwaysonnet6 years agoOccasional Contributor
You are right. File specifies an alternative location for content-cache. I see there is lot of disk space available too (close to 8GB) and permissions look good too. all the CC users have read and execute permissions.
- alwaysonnet6 years agoOccasional Contributor
I have restarted the services and everything is back to normal.
Related Content
- 3 years agojim_prater
- 7 months agobleahy
Recent Discussions
- 7 days agorturner
- 17 days agomardito
Changing role settings
Solved18 days agoChrisF1- 20 days agoOGrimm