Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2571

Add final apache restart to BioViz Connect playbook

        Details

        • Type: Task
        • Status: Closed (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
          None

          Description

          Situation: The BioViz Connect ansible playbook requires a final restart of apache in order to function correctly. We have tried to add the apache restart as part of the playbook without success. Unclear why this is occurring.

          Task: Implement a final apache restart as part of the BioViz Connect playbook.

            Attachments

              Issue Links

              relates to

              New Feature - A new feature of the product, which has yet to be developed. IGBF-2403 Add crt,redis,rds, mysql,migrate roles to BioViz Connect playbooks

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                cdias1 Chester Dias (Inactive) added a comment -

                [~aloraine]
                Please can you associate the below IP address with some test Bioviz domain?
                3.223.11.85

                and send me the domain name.

                Show
                cdias1 Chester Dias (Inactive) added a comment - [~aloraine] Please can you associate the below IP address with some test Bioviz domain? 3.223.11.85 and send me the domain name.
                Hide
                Permalink
                cdias1 Chester Dias (Inactive) added a comment -

                For some unknown reason, the handler was never executing. My understanding is that handlers don't get triggered on forced status changes.
                I have added a line that will force the handler that is notified to execute.
                Please Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/commits/d59819790e5662b3fead6884ec42315be9a1fa26

                Show
                cdias1 Chester Dias (Inactive) added a comment - For some unknown reason, the handler was never executing. My understanding is that handlers don't get triggered on forced status changes. I have added a line that will force the handler that is notified to execute. Please Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/commits/d59819790e5662b3fead6884ec42315be9a1fa26
                Hide
                Permalink
                cdias1 Chester Dias (Inactive) added a comment -

                PR: https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12/igbf-2571-added-a-change-to-force/diff

                Show
                cdias1 Chester Dias (Inactive) added a comment - PR: https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12/igbf-2571-added-a-change-to-force/diff
                Hide
                Permalink
                nfreese Nowlan Freese added a comment -

                Merged https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12

                Show
                nfreese Nowlan Freese added a comment - Merged https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12
                Hide
                Permalink
                nfreese Nowlan Freese added a comment -

                Tested running BioViz Connect playbook.

                Need to run playbook three times from control node - first for initial setup, then need to assign correct elastic ip or assign domain to ip, rerun playbook again for the syncing script to run, then run the playbook for the 3rd time to get (I think) redis settings to work correctly. After 3rd run of playbook everything worked correctly.

                Closing issue.

                Show
                nfreese Nowlan Freese added a comment - Tested running BioViz Connect playbook. Need to run playbook three times from control node - first for initial setup, then need to assign correct elastic ip or assign domain to ip, rerun playbook again for the syncing script to run, then run the playbook for the 3rd time to get (I think) redis settings to work correctly. After 3rd run of playbook everything worked correctly. Closing issue.

                  People

                  • Assignee:
                    cdias1 Chester Dias (Inactive)
                    Reporter:
                    nfreese Nowlan Freese
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: