[jira] [Commented] (OODT-716) Vagrant user on VM unable to start/stop oodt services

["Sheryl John (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034173#comment-14034173 ] 

Sheryl John commented on OODT-716:
----------------------------------

I edited the Vagrantfile with provisioning as non-privileged user (default is root).
{code} config.vm.provision :shell, :path => "vagrant/provision.sh", :privileged => false {code}
Built a new machine with 'vagrant up', and now I'm able to start/stop (./bin/oodt ) without sudo.

I think the environment variables were set for the SSH user with the above non-privileged option for vagrant provision.
See : http://superuser.com/questions/721813/vagrant-provision-script-echo-source-root-venvburrito-startup-sh-prof


> Vagrant user on VM unable to start/stop oodt services
> -----------------------------------------------------
>
>                 Key: OODT-716
>                 URL: https://issues.apache.org/jira/browse/OODT-716
>             Project: OODT
>          Issue Type: Test
>            Reporter: Sheryl John
>            Priority: Minor
>
> * Not able to stop/start oodt services as vagrant user, but able to do so via 'sudo'.
> * With 'sudo', tomcat -opsui service (catalina.sh) throws following:
> {code}
> vagrant@vagrant:/usr/local/oodt/tomcat$ sudo sh ./bin/catalina.sh start
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
> At least one of these environment variable is needed to run this program
> {code}
> To reproduce issue:
> Follow the README.txt from trunk/vagrant/radix/.
> Before the setup instructions, edit the vagrant/provision.sh. Add following line at the end of the "Setup new RADiX project" section
> {code} sudo chown -R vagrant:vagrant ${OODT_DEPLOYMENT_HOME} {code} 
> {code}
> > vagrant up (wait for 15-20 min)
> > vagrant ssh
> > cd $OODT_DEPLOYMENT_HOME
> > ./bin/oodt start
> vagrant@vagrant:/usr/local/oodt$ ./bin/oodt: 102: ./bin/oodt: cannot create /usr/local/oodt/logs/oodt.out: Permission denied
> ./bin/oodt: 101: ./bin/oodt: cannot create /usr/local/oodt/logs/oodt.out: Permission denied
> ./bin/oodt: 100: ./bin/oodt: cannot create /usr/local/oodt/logs/oodt.out: Permission denied
> ./bin/oodt: 99: ./bin/oodt: cannot create /usr/local/oodt/logs/oodt.out: Permission denied
> {code}
> Above error could be related to vagrant's provisioning as privileged user.



--
This message was sent by Atlassian JIRA
(v6.2#6252)