UNSOLVED

RudolphVisagie

updated

13 years ago

0

1547

August 21st, 2013 01:00

Gen4S Rain installation fails

Hi,

I'm busy installing a factory delivered Gen4S Avamar RAIN server - titan rack the works.

Done all the pre-requisites like RAID and CRC checks etc.

During the installation, it fails at "Verifying System Is Properly Kickstarted and Ready for Install"

Since I didn't kick-start the nodes, why does it fail it here?

I'm installing 6.1.101-87.

Thank you

  • Lucky85

    173 Posts

    742

    0

    Posted August 21st, 2013 01:00

    Try to search more to the beginning, it has to observe somehow that your box should be AVE and not physical node…

  • rpervan

    266 Posts

    742

    0

    Posted August 21st, 2013 01:00

    hi rudolph,

    Please be so kind and tell us exactly the steps you performed in detail.

    Did you follow steps in installation guide ?

    Rej

  • 742

    0

    Posted August 21st, 2013 01:00

    I used the procedure from the Avamar Procedure Generator.

    Here is some more info from the logs:

    2013/08/21-10:24:37 [3239992]  INFO: upgrade_ks_25to27b.rb:43:do ---------- BEGIN UpgradeKickstart25To27b::do ----------

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2286:sys - - - - - - - BEGIN(output) - - - - - - -

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2300:sys SUSE Linux Enterprise Server 11 (x86_64)

    VERSION = 11

    PATCHLEVEL = 1

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2304:sys - - - - - - - END

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys " cat /etc/SuSE-release", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2286:sys - - - - - - - BEGIN(output) - - - - - - -

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2300:sys Linux IKHSAVAMAR01 2.6.32.12-0.7.1.4677.0.PTF-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2304:sys - - - - - - - END

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys " uname -a", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:1505:get_os_version address= remote= os=SLES version=11 update=1 arch=x86_64

    2013/08/21-10:24:37 [3239992]  INFO: UpgradeKickstart25To27b::do OS=SLES version=11 update=1 arch=x86_64

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2286:sys - - - - - - - BEGIN(output) - - - - - - -

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2300:sys SUSE Linux Enterprise Server 11 (x86_64)

    VERSION = 11

    PATCHLEVEL = 1

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2304:sys - - - - - - - END

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys " cat /etc/SuSE-release", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2286:sys - - - - - - - BEGIN(output) - - - - - - -

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2300:sys Linux IKHSAVAMAR01 2.6.32.12-0.7.1.4677.0.PTF-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2304:sys - - - - - - - END

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys " uname -a", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:1505:get_os_version address= remote= os=SLES version=11 update=1 arch=x86_64

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2278:sys no output seen from "find /usr/local/avamar/install -maxdepth 1 -name sles*v*"

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys "find /usr/local/avamar/install -maxdepth 1 -name sles*v*", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2278:sys no output seen from "find / -maxdepth 1 -name sles*v*"

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys "find / -maxdepth 1 -name sles*v*", exit status=0 (success)

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2278:sys no output seen from "find /tmp -maxdepth 1 -name sles*v*"

    2013/08/21-10:24:37 [3239992]  INFO: tools.rb:2309:sys "find /tmp -maxdepth 1 -name sles*v*", exit status=0 (success)

    2013/08/21-10:24:38 [3239992]  INFO: tools.rb:2278:sys no output seen from "rpm -qa | grep ave-script"

    2013/08/21-10:24:38 [3239992]  INFO: tools.rb:2312:sys "rpm -qa | grep ave-script", exit status=1

    2013/08/21-10:24:38 [3239992] ---------------------------------- ERROR ----------------------------------

    ERROR: UpgradeKickstart25To27b::quit  Verification of kickstart version failed operation failed

    --------------------------------------------------------------------------------------------------------

    2013/08/21-10:24:38 [3239992]  INFO: task.rb:1218:quit ---------- END UpgradeKickstart25To27b::quit ------------

    I hope this helps

  • 742

    0

    Posted August 21st, 2013 01:00

    Only extra info I could find says it fails at the command "rpm -qa |grep ave-script" which is weird since this is not AVE.

  • Lucky85

    173 Posts

    742

    0

    Posted August 21st, 2013 01:00

    There has to be error in log what is wrong…

    Regards

    Lukas

  • Lucky85

    173 Posts

    742

    0

    Posted August 21st, 2013 02:00

    Have you used same version AvamarBundle as installed package??

    Have you uploaded avamar avp package successfully?? Have you checked hash??

    Try to heck this log /usr/local/avamar/var/avi/server_log/avinstaller.log.0

    Lukas

  • 742

    0

    Posted August 21st, 2013 11:00

    Called in support on this one, turns out there was a file missing from the factory kick-start. Had to touch  /usr/local/avamar/install/sles11-SP1-64v41.5s.

    After this the install went through 100%.

    Thanks!

  • ionthegeek

    2 Intern

    2049 Posts

    742

    0

    Posted August 21st, 2013 12:00

    I would be extremely leery of placing this grid into production. If the kickstart version file was not present as you reported, we have no way to know know what else may have gone wrong during the kickstart. I would strongly recommend re-kicking this node or having it replaced with a factory fresh node to avoid future issues.

  • ionthegeek

    2 Intern

    2049 Posts

    742

    0

    Posted August 23rd, 2013 10:00

    I confirmed with the hardware team -- this node did not complete its kickstart and is not in a good state. Please get in touch with support and reference Escalation 6317.