VxUpdate install push fails for Solaris 10

Question

Has anyone noticed anything similar when trying to push an upgrade via VxUpdate?Client is running 8.1.1 and is a Solaris10 (Generic_150400-59 sun4u sparc) a container. The global zone is running NetBackup 8.2.23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Installing&nbsp;NetBackup&nbsp;Pre-Check&nbsp;as&nbsp;&lt;VRTSnbpck&gt;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;##&nbsp;Executing&nbsp;preinstall&nbsp;script.
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Thursday,&nbsp;January&nbsp;23,&nbsp;2020&nbsp;&nbsp;3:27:33&nbsp;PM&nbsp;EST:&nbsp;Installing&nbsp;package&nbsp;VRTSnbpck.
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Bad&nbsp;string
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Resolved&nbsp;machine&nbsp;role&nbsp;[CLIENT]&nbsp;from&nbsp;existing&nbsp;NetBackup&nbsp;configuration.
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Bad&nbsp;string
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Bad&nbsp;string
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Please&nbsp;review&nbsp;the&nbsp;VERITAS&nbsp;SOFTWARE&nbsp;LICENSE&nbsp;AGREEMENT&nbsp;located&nbsp;on
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;the&nbsp;installation&nbsp;media&nbsp;before&nbsp;proceeding.&nbsp;The&nbsp;agreement&nbsp;includes
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;details&nbsp;on&nbsp;the&nbsp;NetBackup&nbsp;Product&nbsp;Improvement&nbsp;Program.
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;For&nbsp;NetBackup&nbsp;installation&nbsp;and&nbsp;upgrade&nbsp;information&nbsp;specific&nbsp;to&nbsp;your
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;platform&nbsp;and&nbsp;to&nbsp;find&nbsp;out&nbsp;if&nbsp;your&nbsp;installed&nbsp;EEBs&nbsp;or&nbsp;hot&nbsp;fixes&nbsp;are
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;contained&nbsp;in&nbsp;this&nbsp;release,&nbsp;check&nbsp;the&nbsp;Installation&nbsp;and&nbsp;Upgrade&nbsp;checklists
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;and&nbsp;the&nbsp;Hot&nbsp;Fix&nbsp;and&nbsp;EEB&nbsp;Release&nbsp;Auditor,&nbsp;both&nbsp;available&nbsp;on&nbsp;the&nbsp;Veritas
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Services&nbsp;and&nbsp;Operations&nbsp;Readiness&nbsp;Tools&nbsp;(SORT)&nbsp;page:
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;https://sort.veritas.com/netbackup.
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;ERROR:&nbsp;&nbsp;&nbsp;Detected&nbsp;an&nbsp;attempt&nbsp;to&nbsp;install&nbsp;incorrect&nbsp;platform&nbsp;and/or
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;operating&nbsp;system&nbsp;and&nbsp;version&nbsp;client&nbsp;binaries&nbsp;on [FQDN].
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;ERROR:&nbsp;&nbsp;&nbsp;Detected&nbsp;an&nbsp;attempt&nbsp;to&nbsp;install&nbsp;incorrect&nbsp;platform&nbsp;and/or&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;operating&nbsp;system&nbsp;and&nbsp;version&nbsp;client&nbsp;binaries&nbsp;on [FQDN].
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;pkgadd:&nbsp;ERROR:&nbsp;preinstall&nbsp;script&nbsp;did&nbsp;not&nbsp;complete&nbsp;successfully
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;
23-Jan-2020&nbsp;3:27:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=46790)&nbsp;Installation&nbsp;of&nbsp;&lt;VRTSnbpck&gt;&nbsp;failed.The following appears in the VRTSnbpck install log fileERROR:   Detected an attempt to install incorrect platform and/or
         operating system and version client binaries on [FQDN&gt;].and packages installed on the container are:application VRTSnbcfg NetBackup Configurationapplication VRTSnbclt NetBackup Clientapplication VRTSnbjava NetBackup Java Consoleapplication VRTSnbjre NetBackup Java JREapplication VRTSnbpck NetBackup Pre-CheckPS: This issue has appeared on more than 1 container.

x2 · Answer

MarianneJust verified that those are whole root local zones.I will open a case with support and update as I get more information.&nbsp;

genericus · Answer

I never use VxUPdate for solaris since you can run the update_client from the master to update all the unix clients.
I may take up some space - make sure you have allocated at least4GB for /tmp.
If you have issues, it may leave it in an uncertain state, which will require a full uninstall, sometimes the solution is to reinstall on old version and upgrade it, lol.
If you run the update_client, it will build a file in /tmp, you can edit it so save out only the clients you want, then update only those few. I am only up to 8.1.2, but it has worked great so far.
&nbsp;

michal_mikulik1 · Answer

Hello,
review all NetBackup policies for this client if it has a correct OS/HW type configured in them.
Regards
Michal

x2 · Answer

Both the global zone and the container are setup as Solaris/Solaris10 in their backup policy and backed up only via a single backup policy.&nbsp;

marianne · Answer

X2&nbsp;
Is this a 'whole root&nbsp;local zone' or 'sparse root local zone'?&nbsp;
I think vxupdate will only work for&nbsp;whole root&nbsp;local zone.
This TN is quite old, but it explains different scenarios:&nbsp; &nbsp;https://www.veritas.com/content/support/en_US/article.100025009

Forum Discussion

VxUpdate install push fails for Solaris 10

Related Content

nbrepo for vxUpdate

VxUpdate bulk client upgrade on CLI from master

VxUpdate repository location 8.1.2

Netbackup client installation on Solaris 10

Solaris client installation issue