4 Replies Latest reply on Nov 2, 2010 4:50 AM by goldmann

    AMI without JBossESB

    ingedeut

      Hello Marek, 

       

      Finnally i have created an AMI for JBossESB. But the problem is when starting the image in a EC2 Machine i don't find JBoss ESB.  have you please any idea? 

        There is two public AMI (US East):

       

        -  ami-ecc63385 :  i386 

      -  ami-fcc43195:  x86_64  

       

      can you please check them?  

       

      -is there any required Packages for JBossesb?

       

      --Regards

       

      Younes

        • 1. Re: AMI without JBossESB
          goldmann

          I can confirm, that i386 AMI doesn't contains jbossesb package. This means the package wasn't installed. Most probably %pre or %post section for this RPM failed while the package was installed. Check your log.

           

          --Marek

          • 2. Re: AMI without JBossESB
            goldmann

            I cannot see in your previous post jbossesb package included in the packages list in .appl file. Why you haven't included it? This is the cause...

             

            --Marek

            • 3. Re: AMI without JBossESB
              ingedeut

              Thank you Marek,

               

              i have added the missed package to the appl file and have created the following AMI. Unfortunately can i not access to the started EC2 Instance. I think somthing is wrong in the rpm file. can you please check the following ami ami-24ae594d if it's running?

               

              thanks

               

              younes

              • 4. Re: AMI without JBossESB
                goldmann

                Add following packages to your appliance: dhclient and selinux-policy-targeted and rebuild it. Package dependency were broken after a package update in Fedora, we'll add these packages to default pacakge list in Fedora in next BG release.

                 

                --Marek