-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora fails to deploy on vagrant up #458
Comments
Just updated my ubuntu/xenial basebox to see if that does anything. After that, I'm investigating the service script for tomcat7 to see where the command is run from, as that may lead to where transaction.log gets written. |
Confirmed. It's failing. https://gist.github.com/DiegoPino/26cda84d454843a8350cde7a851cd108#file-catalina-log-L720 |
It sees to be related to tomcat deployment via apt-get |
I'm going to attempt the fix outlined in https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1232258
|
PR is up! #462 |
bah.... perms are getting set incorrectly further downstream... tested in isolation, (e.g. just the fcrepo.sh script), everything works fine. but full install shows this still fails. |
Fixed via 876d44b |
Blocks #448
Fedora fails to deploy when running a new vagrant up. Seems to be related to our tomcat setup, and where transaction.log gets written to. Somehow it's going somewhere the user doesn't have access to during the install process. See this gist for my catalina.out: https://gist.github.com/dannylamb/cea486a82d1467baf70d67bf40e8f9b9
The text was updated successfully, but these errors were encountered: