sailfin
  1. sailfin
  2. SAILFIN-1931

[REGRESSION] [inplace] domain1 failed to start

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • 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,931

      Description

      Could not start domain1 after "inplace upgrade" between v1 build 60g and v2
      build b28. Tried with scenarios using setup-cluster.xml without target
      uncompress-jars and see similar issue with domain1 startup

      Setup is on 1 machine

      History of commands used:
      515 java -Xmx256m -jar sailfin-installer-v1-b60g-sunos_x86.jar
      516 cp -r sailfin sailfin.b60g
      517 cd sailfin
      518 ant -f setup-cluster.xml
      519 la
      520 ks
      521 ls
      522 . ../setup.sh
      523 ant -f setup-cluster.xml
      524 ls
      525 ls
      526 cd ..
      527 ls
      528 cp /home/nga/sailfin-installer-v2-b28-sunos_x86.jar .
      529 java -Xmx256m -jar sailfin-installer-v2-b28-sunos_x86.jar
      530 cd sailfin
      531 ls
      532 ant -f setup-cluster.xml uncompress-jars
      533 ls
      534 bin/asadmin start-domain domain1

      bash-3.00# bin/asadmin start-domain domain1
      Starting Domain domain1, please wait.
      Default Log location is /export/home/sailfin/domains/domain1/logs/server.log.
      Redirecting output to /export/home/sailfin/domains/domain1/logs/server.log
      Timeout waiting for domain domain1 to go to starting state.
      CLI156 Could not start the domain domain1.
      CLI156 Could not start the domain domain1

        Activity

        Hide
        1xpert added a comment -

        Created an attachment (id=1083)
        domain1's log

        Show
        1xpert added a comment - Created an attachment (id=1083) domain1's log
        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. This is
        installer problem and I fixed the same.

        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. This is installer problem and I fixed the same. 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 -

        Verified bug is fixed using new instruction and support...
        Build used is sailfin 2.0 nightly build
        (sailfin-installer-v2-b30-nightly-25_aug_2009.jar)

        Show
        1xpert added a comment - Verified bug is fixed using new instruction and support... Build used is sailfin 2.0 nightly build (sailfin-installer-v2-b30-nightly-25_aug_2009.jar)

          People

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

            Dates

            • Created:
              Updated:
              Resolved: