sailfin
  1. sailfin
  2. SAILFIN-1930

inplace upgrade throws BUILD FAILED, could not create-domain error

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: milestone 1
    • Component/s: Tools
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Sun

    • Issuezilla Id:
      1,930

      Description

      Inplace upgrade
      OS: suse linux

      Steps to reproduce:

      1)install sailfin v1 b60g

      2) execute ant -f setup-cluster.xml

      3)backup directory

      4)install sailfin v2 promoted build b28 in the same directory as sailfin v1

      5)execute ant -f setup-cluster.xml

      Maybe setup-cluster.xml should remove the target to create-domain to avoid error
      could not create domain, and build failed

      Error seen during extracting ant -f setup-cluster.xml

      remove.domain.xml:
      [echo] Deleting File ->
      /export/home/upgrade/sailfin/lib/install/templates/cluster/domain.xml

      create.domain:
      [exec] Domain domain1 already exists in
      /export/home/upgrade/sailfin/domains. Use a different domain name or the
      --domaindir option.
      [exec] CLI130 Could not create domain, domain1

      BUILD FAILED
      /export/home/upgrade/sailfin/setup-cluster.xml:171: The following error occurred
      while executing this line:
      /export/home/upgrade/sailfin/setup-cluster.xml:236: The following error occurred
      while executing this line:
      /export/home/upgrade/sailfin/setup-cluster.xml:690: exec returned: 1

        Activity

        Hide
        1xpert added a comment -

        same issue seen when executing ant -f setup.xml
        remove.domain.xml:
        [echo] Deleting File ->
        /export/home/upgrade/temp/sailfin/lib/install/templates/developer/domain.xml

        create.domain:
        [exec] Domain domain1 already exists in
        /export/home/upgrade/temp/sailfin/domains. Use a different domain name or the
        --domaindir option.
        [exec] CLI130 Could not create domain, domain1

        BUILD FAILED
        /export/home/upgrade/temp/sailfin/setup.xml:177: The following error occurred
        while executing this line:
        /export/home/upgrade/temp/sailfin/setup.xml:607: exec returned: 1

        Show
        1xpert added a comment - same issue seen when executing ant -f setup.xml remove.domain.xml: [echo] Deleting File -> /export/home/upgrade/temp/sailfin/lib/install/templates/developer/domain.xml create.domain: [exec] Domain domain1 already exists in /export/home/upgrade/temp/sailfin/domains. Use a different domain name or the --domaindir option. [exec] CLI130 Could not create domain, domain1 BUILD FAILED /export/home/upgrade/temp/sailfin/setup.xml:177: The following error occurred while executing this line: /export/home/upgrade/temp/sailfin/setup.xml:607: exec returned: 1
        Hide
        1xpert added a comment -

        Correction to previous comment: Maybe setup-cluster.xml should DETECT domain and
        if exists, it should not create-domain.

        Show
        1xpert added a comment - Correction to previous comment: Maybe setup-cluster.xml should DETECT domain and if exists, it should not create-domain.
        Hide
        naman_mehta added a comment -

        I added new support for in place upgrade in jar based installer. You can try
        same on today's nightly build. Follow below instructions to do upgrade. It is
        not going to create any domain so this create-domain problem has been resolved now.

        How to upgrade on existing SailFin?
        Consider user has existing setup of SailFin 1.0 under <ws>/sailfin directory.

        1. Download SailFin v2 jar file called <installer jar>.
        2. Copy this new jar file to <ws> directory.
        3. cd <ws>
        4. java -jar -Xmx256m <installer jar> -upgrade
        or
        java -jar -Xmx256m <installer jar> -console -upgrade
        Note: To do the upgrade user have to give -upgrade option otherwise it
        won't overwrite existing files under sailfin directory.
        5. cd <ws>/sailfin
        6. lib/ant/bin/ant -f setup.xml uncompress-jars
        This command uncompress all pack.gz jars to sailfin/lib folder. It won't
        create any new domain.
        7. Start the domain now and in-place upgrade would take place.

        Naman

        Show
        naman_mehta added a comment - I added new support for in place upgrade in jar based installer. You can try same on today's nightly build. Follow below instructions to do upgrade. It is not going to create any domain so this create-domain problem has been resolved now. How to upgrade on existing SailFin? Consider user has existing setup of SailFin 1.0 under <ws>/sailfin directory. 1. Download SailFin v2 jar file called <installer jar>. 2. Copy this new jar file to <ws> directory. 3. cd <ws> 4. java -jar -Xmx256m <installer jar> -upgrade or java -jar -Xmx256m <installer jar> -console -upgrade Note: To do the upgrade user have to give -upgrade option otherwise it won't overwrite existing files under sailfin directory. 5. cd <ws>/sailfin 6. lib/ant/bin/ant -f setup.xml uncompress-jars This command uncompress all pack.gz jars to sailfin/lib folder. It won't create any new domain. 7. Start the domain now and in-place upgrade would take place. Naman
        Hide
        1xpert added a comment -

        Verify bug is fixed using nightly build
        sailfin-installer-v2-b30-nightly-25_aug_2009.jar and new instruction from Naman.

        Show
        1xpert added a comment - Verify bug is fixed using nightly build sailfin-installer-v2-b30-nightly-25_aug_2009.jar and new instruction from Naman.

          People

          • Assignee:
            naman_mehta
            Reporter:
            1xpert
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: