This line was removed.
This word was removed. This word was added.
This line was added.
Comment: Updated the problem about access to /usr/share/tomcat6/.aduna/
Changes (6)View Page History
RAID-0 gives good performance, but is more likely to suffer problems due to disk failure. RAID-5 is a good balance between resilience/redundancy and cost. Using SSDs, we have (little more than anecdotal) evidence that RAID-0 is fast, RAID-1 is slower, and RAID-5 is slower with less than 4 disks and abut the same as RAID-0 with 4 or more disks.
h5. Why does it say "Unable to create logging directory" after deploying with Tomcat
h5. Why won't Sesame start in Tomcat?
If you deploy OWLIM/Sesame to Tomcat and you are unable to create an OWLIM repository using the workbench, then it might be due to a permissions problem on the logging directory for the openrdf-sesame server. To check this, point your browser directory at the Sesame server with a URL similar to the following:
This problem will manifest itself in many ways after deploying the Sesame/OWLIM war files to Tomcat's webapps directory. If you are unable to set the server URL in the Workbench then this is an indication that the problem has occurred. It will likely be due to a permissions problem on the logging directory for the openrdf-sesame server. To check this, point your browser directly at the Sesame server with a URL similar to the following:
bq. Invocation of init method failed; nested exception is java.io.IOException: Unable to create logging directory /usr/share/tomcat6/.aduna/openrdf-sesame/logs
then this indicates that Tomcat does not have write permission to its logging directory. To fix this, log in as root and do the following:
then this indicates that Tomcat does not have write permission to its data directory (where it stores configuration, logs and actual repository data). To fix this, log in as root to the server machine and do the following: