How can I fix JIRA installation problem on EC2?










0















I have had a problem for a few days with EVERY EC2 INSTANCE that I create.



I set up the group security, the jira installation file, the database. Then I open the installation URL and a DB test connection is working but when I submit, it takes a few minutes loading then the whole server is down and the installation is aborted.



BTW: I'm new in AWS so I only changed and added ports in the security group.



Here are some screenshots:



  • Connection DB

  • Submit

  • Instance down

  • Inbound traffic

  • Outbound traffic









share|improve this question




























    0















    I have had a problem for a few days with EVERY EC2 INSTANCE that I create.



    I set up the group security, the jira installation file, the database. Then I open the installation URL and a DB test connection is working but when I submit, it takes a few minutes loading then the whole server is down and the installation is aborted.



    BTW: I'm new in AWS so I only changed and added ports in the security group.



    Here are some screenshots:



    • Connection DB

    • Submit

    • Instance down

    • Inbound traffic

    • Outbound traffic









    share|improve this question


























      0












      0








      0








      I have had a problem for a few days with EVERY EC2 INSTANCE that I create.



      I set up the group security, the jira installation file, the database. Then I open the installation URL and a DB test connection is working but when I submit, it takes a few minutes loading then the whole server is down and the installation is aborted.



      BTW: I'm new in AWS so I only changed and added ports in the security group.



      Here are some screenshots:



      • Connection DB

      • Submit

      • Instance down

      • Inbound traffic

      • Outbound traffic









      share|improve this question
















      I have had a problem for a few days with EVERY EC2 INSTANCE that I create.



      I set up the group security, the jira installation file, the database. Then I open the installation URL and a DB test connection is working but when I submit, it takes a few minutes loading then the whole server is down and the installation is aborted.



      BTW: I'm new in AWS so I only changed and added ports in the security group.



      Here are some screenshots:



      • Connection DB

      • Submit

      • Instance down

      • Inbound traffic

      • Outbound traffic






      linux postgresql amazon-web-services amazon-ec2 jira






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 11 '18 at 15:14









      Scott Dudley

      2,56011125




      2,56011125










      asked Nov 10 '18 at 17:57









      Ah MedAh Med

      63




      63






















          2 Answers
          2






          active

          oldest

          votes


















          0














          The most likely cause is you're out of RAM. Jira is quite high on requirements, so if you're trying to use an instance with, say, 1 Gb of RAM, it won't work, and the processes will get killed with OOM (out of memory) exception.



          Another approach would be to create an instance with ECS-optimized AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) and run Jira as a Docker container (https://community.atlassian.com/t5/Jira-articles/How-to-run-Jira-in-a-docker-container/ba-p/752697).






          share|improve this answer






























            0














            I’ve seen this occur using the Atlassian CloudFormation template. The issue is that the database setup takes so long that the load balancer pings eventually time out, so the load balancer decides that the node is down and removes it from load. You can confirm if this is the case by looking into the load balancer status on the AWS console.



            There are probably better ways to handle this, but I got around it by accessing the Jira node directly to perform the setup (ie. going around the node balancer and hitting port 8080 directly). You may need to setup a bastion host and forward connections over SSH to do this.






            share|improve this answer






















              Your Answer






              StackExchange.ifUsing("editor", function ()
              StackExchange.using("externalEditor", function ()
              StackExchange.using("snippets", function ()
              StackExchange.snippets.init();
              );
              );
              , "code-snippets");

              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "1"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53241854%2fhow-can-i-fix-jira-installation-problem-on-ec2%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              The most likely cause is you're out of RAM. Jira is quite high on requirements, so if you're trying to use an instance with, say, 1 Gb of RAM, it won't work, and the processes will get killed with OOM (out of memory) exception.



              Another approach would be to create an instance with ECS-optimized AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) and run Jira as a Docker container (https://community.atlassian.com/t5/Jira-articles/How-to-run-Jira-in-a-docker-container/ba-p/752697).






              share|improve this answer



























                0














                The most likely cause is you're out of RAM. Jira is quite high on requirements, so if you're trying to use an instance with, say, 1 Gb of RAM, it won't work, and the processes will get killed with OOM (out of memory) exception.



                Another approach would be to create an instance with ECS-optimized AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) and run Jira as a Docker container (https://community.atlassian.com/t5/Jira-articles/How-to-run-Jira-in-a-docker-container/ba-p/752697).






                share|improve this answer

























                  0












                  0








                  0







                  The most likely cause is you're out of RAM. Jira is quite high on requirements, so if you're trying to use an instance with, say, 1 Gb of RAM, it won't work, and the processes will get killed with OOM (out of memory) exception.



                  Another approach would be to create an instance with ECS-optimized AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) and run Jira as a Docker container (https://community.atlassian.com/t5/Jira-articles/How-to-run-Jira-in-a-docker-container/ba-p/752697).






                  share|improve this answer













                  The most likely cause is you're out of RAM. Jira is quite high on requirements, so if you're trying to use an instance with, say, 1 Gb of RAM, it won't work, and the processes will get killed with OOM (out of memory) exception.



                  Another approach would be to create an instance with ECS-optimized AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) and run Jira as a Docker container (https://community.atlassian.com/t5/Jira-articles/How-to-run-Jira-in-a-docker-container/ba-p/752697).







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 10 '18 at 18:43









                  Sergey KovalevSergey Kovalev

                  4,4491425




                  4,4491425























                      0














                      I’ve seen this occur using the Atlassian CloudFormation template. The issue is that the database setup takes so long that the load balancer pings eventually time out, so the load balancer decides that the node is down and removes it from load. You can confirm if this is the case by looking into the load balancer status on the AWS console.



                      There are probably better ways to handle this, but I got around it by accessing the Jira node directly to perform the setup (ie. going around the node balancer and hitting port 8080 directly). You may need to setup a bastion host and forward connections over SSH to do this.






                      share|improve this answer



























                        0














                        I’ve seen this occur using the Atlassian CloudFormation template. The issue is that the database setup takes so long that the load balancer pings eventually time out, so the load balancer decides that the node is down and removes it from load. You can confirm if this is the case by looking into the load balancer status on the AWS console.



                        There are probably better ways to handle this, but I got around it by accessing the Jira node directly to perform the setup (ie. going around the node balancer and hitting port 8080 directly). You may need to setup a bastion host and forward connections over SSH to do this.






                        share|improve this answer

























                          0












                          0








                          0







                          I’ve seen this occur using the Atlassian CloudFormation template. The issue is that the database setup takes so long that the load balancer pings eventually time out, so the load balancer decides that the node is down and removes it from load. You can confirm if this is the case by looking into the load balancer status on the AWS console.



                          There are probably better ways to handle this, but I got around it by accessing the Jira node directly to perform the setup (ie. going around the node balancer and hitting port 8080 directly). You may need to setup a bastion host and forward connections over SSH to do this.






                          share|improve this answer













                          I’ve seen this occur using the Atlassian CloudFormation template. The issue is that the database setup takes so long that the load balancer pings eventually time out, so the load balancer decides that the node is down and removes it from load. You can confirm if this is the case by looking into the load balancer status on the AWS console.



                          There are probably better ways to handle this, but I got around it by accessing the Jira node directly to perform the setup (ie. going around the node balancer and hitting port 8080 directly). You may need to setup a bastion host and forward connections over SSH to do this.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 11 '18 at 15:05









                          Scott DudleyScott Dudley

                          2,56011125




                          2,56011125



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53241854%2fhow-can-i-fix-jira-installation-problem-on-ec2%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                              Crossroads (UK TV series)

                              ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế