09-02-2014 04:50 AM
Hello Support Team,
I recently upgraded my appliance version from 2.6.0.1 to version 2.6.0.3. However, the upgrade did not work. Before the upgrade I copied the image SYMC_NBAPP_update-2.6.0.3-1.x86_64.rpm into the appliance /inst/patch/incoming directory. I was able to view the image using the CLISH "list downloded" command. However, the upgrade completed successfully, but when I tried the check the appliance new version after upgrade I got the same old version displayed: 2.6.0.1
When I run the command upgradestatus, I got the output below:
"appliance version 2.6.0.1 is not in upgrade state"
Please I need help what could be wrong.
NB: This is a new set of appliances, and they need to be upgraded before going into production.
Regards,
Felix
Solved! Go to Solution.
09-02-2014 01:57 PM
Hello Chashock,
This issue has by resolved by the enterprise_support_team. Below is the response from support following the logs I sent to them:
***************************************************************************************************
Hello Felix,
I found the following in the OID 99 logs. It appears to be running into a recently discovered issue that if an SMTP server is configured for notifications on the Appliance this may prompt a rollback at near completion of an upgrade.
<snip>
09/01/14 15:10:26.205 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39525 TID:140462249834240 File ID:99 [No context] [Info] [39520] COMMAND_BEGIN(2226): /opt/NBUAppliance/scripts/hwmon/callhome_setup.pl --smtp --showsettings
09/01/14 15:10:29.708 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39608 TID:140173192636160 File ID:99 [No context] [Info] [39520] COMMAND_END(2226): /opt/NBUAppliance/scripts/hwmon/callhome_setup.pl
09/01/14 15:10:30.164 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39622 TID:139799587321600 File ID:99 [No context] [Info] [39620] COMMAND_BEGIN(2230): -e
09/01/14 15:10:31.080 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39646 TID:139735837800192 File ID:99 [No context] [Info] [39620] COMMAND_END(2230): -e
09/01/14 15:10:31.760 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39693 TID:140612100261632 File ID:99 [No context] [Info] [3862] COMMAND_END(598): /opt/NBUAppliance/scripts/patch.pl
09/01/14 15:10:32.015 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39697 TID:139700948023040 File ID:99 [No context] [Info] [3744] COMMAND_END(590): /opt/NBUAppliance/scripts/patch_wrapper.pl
09/01/14 15:10:32.211 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39701 TID:140370871154432 File ID:99 [No context] [Info] [39699] COMMAND_BEGIN(2232): /opt/NBUAppliance/scripts/system_restore.pl --revertckpt PRE_UPGRADE
<end snip>
The solution is to remove the SMTP configuration, and re-run the upgrade.
To remove SMTP settings from CLISH:
Main_Menu > Settings > Alerts > Email SMTP Delete
****************************************************************************************************
I did remove SMTP configuration and re-run the patch upgrade, this time it completed successfully. I now have appliance version 2.6.0.3 and NetBackup 7.6.0.3 installed.
Thanks for your support,
Regards,
Felix
09-02-2014 05:03 AM
Hi Support Team,
Also find below outputs from some CLISH commands:
5230-01.Software> List Downloaded
Validating update 'SYMC_NBAPP_addon_nbclient_Solaris-7.6.0.3-SLES11.x86_64.rpm' ... failed
- [Error] Update SYMC_NBAPP_addon_nbclient_Solaris-7.6.0.3-SLES11.x86_64.rpm has an invalid name.
Software updates downloaded:
Patch_Name Size Release_Date NBU_Version
SYMC_NBAPP_update-2.6.0.3-1.x86_64.rpm 3.8G Wed Jul 09 2014 7.6.0.3
5230-01.Software> Share Close
Software update shares closed successfully.
09-02-2014 06:28 AM
You should open a support case on this issue. There are a number of things that could have gone wrong in the process, and you'll get the problem solved faster if you open a case than with going back and forth on this forum looking at the various logs that will need reviewed.
I'd have a DataCollect and possibly an nbsu pack ready to upload to support.
Alternatively, if they are brand new with no data on them, have you considered just re-imaging them to 2.6.0.3? That might be the fastest solution.
09-02-2014 08:38 AM
Hi Chashock,
Thanks for your prompt response, yes they are new appliances without data. As you know the nb5230 appliance is shipped with two USB sticks containing images for v2.5.4 and v2.6.0.1, how do I get a full image for v2.6.0.3
I have downloaded the update "SYMC_NBAPP_update-2.6.0.3-1.x86_64.rpm" and all the addons, but can I use these update images to re-image the appliance.
NB: I have also log a support call to Symantec, they are currently checking the logs from the upgrade
Thank you once again,
Felix
09-02-2014 11:47 AM
You can download the full ISO for 2.6.0.3 from FileConnect. Take a look at HOWTO98402 for full instructions.
09-02-2014 11:53 AM
Something just occurred to me. Have you declared a role for this appliance? If I recall correctly, you can't apply the upgrade patches until after a role is declared.
09-02-2014 12:59 PM
Hi Chashock,
The appliance role has been assigned already. The appliance is acting as a media server to an existing master server.
Thank you,
Felix
09-02-2014 01:57 PM
Hello Chashock,
This issue has by resolved by the enterprise_support_team. Below is the response from support following the logs I sent to them:
***************************************************************************************************
Hello Felix,
I found the following in the OID 99 logs. It appears to be running into a recently discovered issue that if an SMTP server is configured for notifications on the Appliance this may prompt a rollback at near completion of an upgrade.
<snip>
09/01/14 15:10:26.205 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39525 TID:140462249834240 File ID:99 [No context] [Info] [39520] COMMAND_BEGIN(2226): /opt/NBUAppliance/scripts/hwmon/callhome_setup.pl --smtp --showsettings
09/01/14 15:10:29.708 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39608 TID:140173192636160 File ID:99 [No context] [Info] [39520] COMMAND_END(2226): /opt/NBUAppliance/scripts/hwmon/callhome_setup.pl
09/01/14 15:10:30.164 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39622 TID:139799587321600 File ID:99 [No context] [Info] [39620] COMMAND_BEGIN(2230): -e
09/01/14 15:10:31.080 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39646 TID:139735837800192 File ID:99 [No context] [Info] [39620] COMMAND_END(2230): -e
09/01/14 15:10:31.760 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39693 TID:140612100261632 File ID:99 [No context] [Info] [3862] COMMAND_END(598): /opt/NBUAppliance/scripts/patch.pl
09/01/14 15:10:32.015 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39697 TID:139700948023040 File ID:99 [No context] [Info] [3744] COMMAND_END(590): /opt/NBUAppliance/scripts/patch_wrapper.pl
09/01/14 15:10:32.211 [Application] NBAPP 409 NBAPP_TRACE 99 PID:39701 TID:140370871154432 File ID:99 [No context] [Info] [39699] COMMAND_BEGIN(2232): /opt/NBUAppliance/scripts/system_restore.pl --revertckpt PRE_UPGRADE
<end snip>
The solution is to remove the SMTP configuration, and re-run the upgrade.
To remove SMTP settings from CLISH:
Main_Menu > Settings > Alerts > Email SMTP Delete
****************************************************************************************************
I did remove SMTP configuration and re-run the patch upgrade, this time it completed successfully. I now have appliance version 2.6.0.3 and NetBackup 7.6.0.3 installed.
Thanks for your support,
Regards,
Felix
09-02-2014 05:28 PM
Good to know that there was a fix. I had not yet seen this, so it's good to know as well!
09-03-2014 01:33 AM
Is this specific to a 2601 to 2603 upgrade, or specific to any upgrade to 2603 ? I have upgraded various appliances to 2602 with no issues (not to 2603 yet) and am wondering whether we should be removing the SMTP config prior to any upgrade to 2603 ?
AJ
09-03-2014 02:31 AM
Hi SYMAJ,
2.6.0.3 is a new update image, it is better you remove SMTP configuration prior to upgrading to 2.6.0.3 since we have now found a solution to a successful upgrade. However, if you wish to try upgrading without removing SMTP configuration. I am just worried you don't run into more serious issue as a result of the fail upgrade in production.
Felix
09-03-2014 04:49 AM
Is this a failure common to all upgrades to 2603, or was it just Felix having this issue ? I don't see any other reports of this so far, although 2603 is still very recent and maybe people not done this upgrade yet....
AJ
09-03-2014 06:22 AM
First time I'd seen this, so I don't think it is a universal issue.