>On May 19, 2008, at 4:54 PM, Maurice Volaski wrote:
>>>On May 19, 2008, at 3:23 PM, Maurice Volaski wrote:
>>>>After extending the debugging, I immediately found the problem
>>>>[19:02:56.255] {main} Caused by: java.io.IOException: Cannot 
>>>>create directory: /usr/share/resin/admin
>>>>Once I changed ownership on /usr/share/resin to be owned by the 
>>>>resin user, the problem went away. My system is Gentoo Linux and 
>>>>the ebuild prepares the directories and sets their ownerships and 
>>>>permissions. So it seems the bug is here is Gentoo's default 
>>>>configuration, although it's not clear why resin tries to 
>>>>manipulate anything in /usr/share/resin given that it is started 
>>>>with -resin-home /usr/lib/resin. (I don't know why there even is 
>>>>a /usr/lib/resin; Gentoo sets it up that way.)
>>>Thanks. That's definitely a bug. I've filed that as 
>>>The startup isn't putting some of the directories in the right 
>>>places.  Instead of creating them in resin.root, it's putting them 
>>>in resin.home.  Since resin.home should be read-only, that's
>>I am confused some. Gentoo sets up /usr/lib/resin as resin.home and 
>>but also creates /usr/share/resin  where it puts resin's "lib" 
>>directory and sets up /usr/lib/resin/lib as a symlink to that. So I 
>>am not clear on which directory is supposed to be resin.root. I 
>>don't see any configuration that's explicitly assigning it. Resin 
>>is trying to create "admin" in /usr/share/resin, which has write 
>>privileges only for root, not in resin.home, which is 
>>/usr/lib/resin/. Resin.home is owned by and writable by resin under 
>I'm not familiar with the Gentoo configuration, so I'm not sure why 
>the parts of Resin are put in different places.  But as long as 
>Resin can read the jar files and the configuration file, it 
>shouldn't matter.
>In your configuration, where is resin.root?  i.e. where does the 
>content go?  That resin.root should be the only writable directory.

resin.root = /usr/share/resin.
resin.home = /usr/lib/resin.

I'm not sure how resin.root gets set or why these two are just not 
the same. Gentoo sets them up as follows:

lrwxrwxrwx  1 resin resin    10 2008-05-20 11:29 conf -> /etc/resin
drwxr-xr-x  4 resin resin  4096 2008-05-20 11:29 ext-webapp-lib
lrwxrwxrwx  1 resin resin    20 2008-05-20 11:29 lib -> /usr/share/resin/lib
drwxr-xr-x  2 resin resin  4096 2008-05-20 11:29 libexec64
lrwxrwxrwx  1 resin resin    14 2008-05-20 11:29 log -> /var/log/resin
lrwxrwxrwx  1 resin resin    14 2008-05-20 11:29 logs -> /var/log/resin
drwxr-xr-x  4 resin resin  4096 2008-05-20 11:29 php
drwxr-xr-x  4 resin resin  4096 2008-05-20 11:29 plugins

drwxr-xr-x   2 root root 4096 2008-05-20 11:29 lib
lrwxrwxrwx   1 root root   14 2008-05-20 11:29 log -> /var/log/resin
-rw-r--r--   1 root root 1213 2008-05-20 11:29 package.env
lrwxrwxrwx   1 root root   22 2008-05-20 11:32 webapps -> 

I don't understand this layout. Why do there have to be two 
directories? It seems redundant since /usr/lib/resin/lib points to 
the lib in /usr/share/resin. And why does there have to be the same 
log symlink in both?

Because /usr/share/resin is owned by root, Resin couldn't create the 
admin directory here and that's what caused it fail to launch 

(The symlink for webapps is setup manually by me since that's on another disk.)

If anything, it seems that the bug here is with Gentoo setting the 
wrong ownership on /usr/share/resin. Where should the admin directory 
go that somehow makes resin at fault here?

Maurice Volaski, [EMAIL PROTECTED]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

resin-interest mailing list

Reply via email to