When I accessed to the URL(http://<host>:8080/openrdf-sesame) after setting up owlim-cloud instance on ec2 and starting tomcat, an error message that is 'java.io.IOException: Unable to create logging directory /data_mount/owlim_data/openrdf-sesame/logs' was shown on browser. Maybe since the owner/permission of '/data_mount/owlim_data' is root/755, the process(owned by tomcat user) could not create directory. Then how can I change owner/permission of '/data_mount/owlim_data'? Since ec2-user can not be super user using 'sudo su -', I don not know how to fix this probrem. Do you have any suggestion?


asked 08 Jun '13, 22:56

schijimatsu's gravatar image

accept rate: 0%

Hi schijimatsu,

From the description of your problem I can see you are using OWLIM on the Amazon cloud. The issue seems to be that your EBS data volume is not fully configured. Please note the Prerequisites section of the user documentation and specifically what it says about the EBS data volume:


d. The filesystem on the EBS volume should be accessible (read/write) to the tomcat Linux user

What that means is that when you prepare your EBS data volume you should also configure its access permissions so that the all Linux users would be able to read/write to it.

That is a prerequisite for running OWLIM on AWS and due to security reasons you can not reconfigure the access rights of the volume directly from your OWLIM instance.

The easiest way of solving your problem would be to attach and mount your EBS volume to another instance (where you can login as root), configure its permissions and then delete the mounting point on the OWLIM instance (/data_mount/owlim_data). After that you can proceed as described in the documentation.

I hope that helps.


answered 14 Jun '13, 09:09

petark's gravatar image

accept rate: 0%

Thanks. I understood that it is written in the documentation. I will try to configure the access rights.

(14 Jun '13, 22:20) schijimatsu

we will be adding more validation checks and detailed error messages to the scripts, so that such problems are detected as early as possible.

Unfortunately, there's no easy way to automate all these configuration steps and some manual configuration will be required (this is the case with many AWS services)

(17 Jun '13, 06:28) Marin Dimitrov

Hello schijimatsu,

I think you have encountered this problem:


For which the solution is to change the ownership of /usr/share/tomcat6/.aduna/ to the tomcat user.

Not all default Tomcat installations have this problem, so in a worst case, you could try another EC2 machine image that includes Tomcat. However, is there really no way to log in as 'root' on this instance?


answered 10 Jun '13, 05:18

baz's gravatar image

baz ♦♦
accept rate: 36%

Thanks for answering. I will try your suggestion.

However, is there really no way to log in as 'root' on this instance?

Yes. I do not know why.

(10 Jun '13, 22:31) schijimatsu
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 08 Jun '13, 22:56

Seen: 4,662 times

Last updated: 01 Jul, 02:22

powered by BitNami OSQA