ViPR SRM 4.x: Online Update distributed new packages - Running Updates on Services prior to Core Update Brought VIPR SRM Down

           

   Article Number:     518638                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR SRM,ViPR SRM 4.1,ViPR SRM 4.1.1

 

Issue:

 

 

With the Online Update functionality configured in a ViPR SRM installation the latest available versions of the product will be staged on the SRM Frontend server and become available to update. However, if the core modules and kernel have not been updated prior to this then using the "yellow star" icon to Update to the Latest Version should not be utilized for the Services and SolutionPacks until this has been completed.   
   
    If the Services and/or the SolutionPacks are updated prior to the core/kernel update being performed there is a risk that the SRM installation may possibly stop discovering objects and/or collecting/displaying data. This can also affect the ability of the databases to run and store the data.
                                                           

 

 

Cause:

 

 

> Database ports were set incorrectly which did not allow database to start-up successfully.   
    > Mixed versions of software and services (between original version and newer version)
                                                           

 

 

Change:

 

 

   

      Full health-check on the ViPR SRM environment to compare versions, logs, etc.   

                                                             

 

 

Resolution:

 

 

   

      In this instance the 4 missing servers were being written to the apg3 database which was not starting due to two lock files on both the MySQL and mysqld services/agents that were dated at the time the issue first occurred. From the command line we used  kill -9 <PIDs> to kill the processes for the database and daemon. Once this was complete we then restarted the apg3 DB from command line and confirmed that it started and was listening on port 2300 for 0.0.0.0. We also checked the atf files for the apg3/tmp directory and there were a large number, which would take a while to work through the system.     
     
      With ViPR SRM back up and running the System Update should be completed after system health has been verified. This will bring the entire SRM infrastructure, core and kernel, update to the correct software version.