Hello Marcus, The solution you suggested absolutely worked. All the installations were successful but on an attempt to login at PGA url using admin_username and admin_password failed with an error "The Airavata Servers are currently down....", I attached screenshot below.
Any help would be appreciated. Thanks, Keerthi On Mon, Feb 18, 2019 at 5:43 PM Christie, Marcus Aaron <machr...@iu.edu> wrote: > Hi Keerthi, > > The "Stop daemons if running" task fails but that is expected since the > daemons haven't been installed yet. The "Copy distributions ..." task fails > because it looks like that build of Airavata failed? However, I think maybe > you are building the master branch of Airavata but the Helix distributions > aren't in the master branch. Make sure the git_branch is changed from > "master" to "develop" here in the standalone/group_vars/all/vars.yml [0] > file. > > [0] > https://github.com/apache/airavata/blob/develop/dev-tools/ansible/inventories/standalone/group_vars/all/vars.yml#L41 > > > On Feb 12, 2019, at 8:51 PM, Keerthi N <keerthi4...@gmail.com> wrote: > > Thanks, Marcus, Firewalld issue was resolved. But choosing to try centos > docker for Airavata installation has been a rough so far. Just on a side > note, I like to mention that I tried on Windows but ansible installation > isn't successful, then tried on Ubuttu (dualboot) with Virtualbox but > has vboxdrv kernel module missing issue. > > So with centos docker, here is another issue while executing > ansible-playbook -i inventories/standalone airavata.yml (screenshot is > attached): *Can't find Java Virtual Machine*. I tried multiple things > which I would like to list down for reference, some of them might not sound > sensible enough but I was just desperately trying if any of them works. > > 1. Maven installation steps included in common/tasks/main.yml because I > checked for mvn -version in docker and it's not recognized although yum > install maven package is present. And the error after trying this > is JAVA_HOME should point to a JDK not a JRE > 2. Explicitly set JAVA_HOME through ansible script, but still the same > error. Then I tried to output java -version which went blank although it's > been installed beforehand through ansible scripts. > 3. Included Java installation steps in the common/tasks/main.yml file > itself along with maven but still java -version didn't give any output msg > in ansible execution. > 3. In main airavata.yml file I changed "common" role to roles similar > to java, env-setup (i.e, no become,become_user) *This successfully > executed the ansible-playbook command*. But in the next step for *helix-setup > failed *at the task to stop daemons running failed error No such > daemon.sh file exists for all the files listed in with_items (the error is > attached as well) > > > Moreover, I'm surprised when I directly executed mvn clean install in > docker, the airavata Build is Successful even before step 2, the screenshot > of which I attached as well. I felt this is something to do with > become_user: {{user}} issue and tried to get rid of it, change it to root > but nothing worked. Also I'm wondering whether helix-setup step and > airavata build are related, so before trying anything further, I thought to > share and take help from you all. > > > Thanks, > Keerthi > > > > On Fri, Feb 8, 2019 at 5:02 PM Christie, Marcus Aaron <machr...@iu.edu> > wrote: > >> Sure. Just looks for the lines related to firewalld in the Ansible role. >> For example, for the env_setup role you would comment out these lines [0]. >> >> [0] >> https://github.com/apache/airavata/blob/05db6bcd44e70067e154243401c16b3a1f96ac2d/dev-tools/ansible/roles/env_setup/tasks/main.yml#L32-L59 >> >> On Feb 8, 2019, at 2:54 PM, Keerthi N <keerthi4...@gmail.com> wrote: >> >> Thank you Marcus, that's helpful. If you don't mind can you direct me to >> the exact file where I can make appropriate changes. >> >> Thanks, >> Keerthi >> >> On Fri, Feb 8, 2019 at 1:59 PM Christie, Marcus Aaron <machr...@iu.edu> >> wrote: >> >>> Hi Keerthi, >>> >>> I don't have experience trying to run Airavata in a CentOS 7 Docker >>> container. Honestly I hadn't thought of doing that, but it would be >>> interesting to see what it takes to get it working. I do have a couple >>> thoughts. >>> >>> First, we've had good success using VirtualBox to run CentOS 7 in a VM. >>> There are many tutorials out there, but I also wrote up some notes on >>> creating a CentOS 7 VM [0], especially with respect to configuring the >>> networking. So if you get stuck with running on a Docker container, there >>> is always the VirtualBox VM approach. >>> >>> Second, looks like the issue you are having is between firewalld and >>> Docker. A quick web search shows me that there may be some issues getting >>> those two to work together. That said, if there isn't a firewall running on >>> the container, perhaps you don't need to open ports in the firewall. You >>> can just comment out those parts of the Ansible scripts in that case. >>> >>> Sincerely, >>> >>> Marcus >>> >>> [0] >>> https://marcus.4christies.com/2019/01/how-to-create-a-virtualbox-vm-with-a-static-ip-and-internet-access/ >>> >>> On Feb 8, 2019, at 11:53 AM, Keerthi N <keerthi4...@gmail.com> wrote: >>> >>> Hello, >>> >>> I used centos 7 container for Airavata installation using guidelines >>> mentioned in the Airavata+Django installation document. I encountered an >>> error (attached below) at the Database installation step (*ansible-playbook >>> -i inventories/standalone database.yml)* >>> >>> The firewalld is not running in the centos 7 container even after >>> trying to enable/start firewalld and iptables. The error message for both >>> cases are attached to this email. Also I tried to restart the docker but >>> there is no difference in the errors. >>> >>> >>> If you have any suggestions to fix and move forward with the >>> installation process, please let me know. >>> >>> >>> Thanks, >>> Keerthi >>> >>> <ipaddr.png><current_status.png><firwalld.png><iptables.png> >>> >>> >>> >> <helix_error.png><mvn_error.png><build_success_on_docker.png> > > >
