Follow the recommendations for succesfull upgrade.
Ex:- su admin from root and run
show apply
admin# show apply
Version Number : sp-x.x.x-x-x-lnx64
Status : Applied Start Time : xxxxxxxx
End Time : xxxxxxxxx
Version Number : sp-x.x.x-x-x-lnx64
Status : Applied Start Time : xxxxxxxx
End Time : xxxxxxxxx
If Status is “Apply-in-progress” , then don’t install any patch .
Download might fail due to many reasons to avoid the failure make sure below are configured before upgrading:
Apply might fail due to many reasons. After login to admin execute show apply
command to check why apply failed.
Ex :- Show apply:
Version Number : sp-x.x.x-x-x-lnx64
Status : Apply-failed
Start Time : xxxxxxx
End Time : xxxxxxx
Reason : Package file "xxx-x.x.x-x-lnx64.zip" not in expected format
In such scenario due to network issue sometimes downloaded package is corrupted.
su
– commandclearImproperPatch.sh
from here ./clearImproperPatch.sh <packagename>
./clearImproperPatch.sh sp-30.0.3-0-0-lnx64
su admin
and trigger the upgrade once more.Collect below information and share with collector support team .
su
– command/opt/LCM/log/install
and /opt/LCM/log/apply logs
Some time it observed that due to cache issue you will face this issue. Follow below steps to resolve it:
su
– commandservice adminshell restart
to restart adminshellDue to network issue some time downloading of package hangs. To overcome this issue follow below steps:
su
– commandvi /opt/LCM/log/install
ex :- 62 551M 62 342M 0 0 544k 0 0:17:18 0:10:44 0:06:34 0k
62 551M 62 342M 0 0 544k 0 0:17:18 0:10:45 0:06:33 0k
su
– commandEx:- #ps –aef | grep download
Kill -9 <PID> from above output
cd /opt/LCM/tmp/
rm –rf <Patch file
to delete the patchupdateDBScript.sh
form here./updateDBScript.sh
su
– commandEx:- #ps –aef | grep apply
Kill -9 <PID>
from above outputupdateDBScript.sh
from here and run as rootSoftware Updates UI page spins with Loading message on 2.8/2.8.0.1 after initiating upgrade from UI. The upgrade job triggered from CSPC version 2.8/2.8.01 might be triggered as casuser process. If the download fails for any reason in this scenario, which can be identified with below logs in /opt/LCM/logs/install
file and along with this sh download
command displays the status as downloading
.
“jeos-30.1.0-1-lnx64.zip ==========
[Fri Nov 16 09:30:36 EST 2018] Starting download operation
jeos-30.1.0-1-lnx64.zip ++++++++++++
~~~~~~~~
ASD-DOWNLOAD: Getting File details from the server
/opt/LCM/tmp/downloads/jeos-30.1.0-1-lnx64.zip~~~~~~~~~~~~~~~~~~
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
104 839 104 839 0 0 2064 0 --:--:-- --:--:-- --:--:-- 18644
RetVal:0
ASD-DOWNLOAD: Checksum error. Downloaded file is corrupted.
(5cbfed16c7e93db9a6c829cd7a825723, 6f7907d0fbaa6f860aa32a1642155d50)”
Database will not be updated with the failure status and Software Updates UI will end up in spinning with Loading message.
To resolve the spinning message issue, perform the following :
Please go through below Documents for more information & installation details for Collector
Revision | Publish Date | Comments |
---|---|---|
1.0 |
14-Mar-2019 |
Initial Release |