Start with a new clean gentoo 2004.2 system, emerge resin 3.0.8-r1, attempt to start resin via /etc/init.d/resin start: 1) immediately receive error "Can't create /var/log/resin/resin_out.log". This is because resin is being started as resin:resin uid/gid and attempting to write to a root owned directory /var/log/resin. Now, manually chown the log directory to resin:resin to complete the install and restart. 2) Still doesn't run because "Can't create /opt/resin/log/jvm.log". This is apparently a bug in the default resin configuration file...it should be referring to /opt/resin/logs/jvm.log where logs is a symlink to /var/log. ok, create another symlink (log -> /var/log/resin) and attempt to start a third time... 3) Nope..."Can't write /opt/resin/httpd.pid at /opt/resin/bin/wrapper.pl line 657". ouch. Look in /opt/resin...most files still aren't chowned to resin:resin resulting in the error. do a manual: chown -R resin:resin /opt/resin chown -R resin:resin /usr/share/resin chown -R resin:resin /etc/resin OK, now attempt to restart resin. It succeeds. Lets look through log files/etc to see how it is doing... Everything is mostly good except for: "java.lang.UnsatisfiedLinkError" no resin in java.library.path and Custom java settings via "JAVA_OPTS" in /etc/conf.d/resin do not appear to be in effect via looking at the commandline used to invoke each of the resin child processes (ps -aux or select one child, look at /proc/<PID>/cmdline). My guess is that both of the above are a result of /etc/conf.d/resin not being processed. It appears to be processed because many of the values are duplicated in wrapper.pl and httpd.sh in /opt/resin/bin..but I have yet to see a change in /etc/conf.d/resin be visible in any form.
i started with a clean 2004.2 system, emerged resin all premission where correct. 1) /var/log/resin is owned by resin:resin here 2) works fine and logs to /var/log/resin/ 3) also owned by resin:resin are you sure you started for a clean system? any errors when you merge? rm -rf /var/log/resin /etc/resin /opt/resin ; emerge resin
I'm guessing that at the very least, you emerged the 2.x version of resin.. I was testing the latest release of 3.0.8..since it appeared that your last patch applied created R1 and 2.x is getting old for new installs. (3.x is still masked? I know that I installed it because I explicitely specified the ebuild...if you just did emerge resin, that merged 2.x - or at least it did the other day). Can you try again with 3.0.8-r1? If you find no problems with it after emerging, I'll switch to another box which has never emerged resin before and try again..but I did wipe all the directories prior to emerging so I don't understand your results..
it was 3.0.8-r1 i'm on ~x86
worksforme
